Rich Edit Box in MFC Operator Interface

Hi
I'm trying to add a MFC Rich Edit box into my OI. However each time I add in the box, my OI cannot be loaded. FYI I can compile my OI code without any error.
I'm writting my codes based on the simple MFC OI from the NI OI sample. What I did is just add the rich edit box from the MFC control into the OI dialog box and my OI.exe cannot load the OI anymore.
I'm using TS3.5 and VC6
Thanks

Hi caviars,
I believe this is related to how you are using the Rich Edit box. See here and here.
Test Engineer - CTA

Similar Messages

How to save contents of two different rich edit box into single rtf file in windows 8.1 app

Developer, I have requirement to save registration data into rtf file.. These can only be done by if I put rich edit box to fill the data.. Now if I am going to write the code for saving the data of different rich edit box into one particular file, it
only saves the data of last rich edit box.. So plzz suggest that how can I save the contents of different rich edit box together into one rtf file.

Ok Nishant, just did some quick research, since rtf file is unlike txt file, we cannot simply directly write some content to the rtf.
You can try to find some third party code that can help you insert text into rtf file or you would like to load the content from rtf out to the richeditbox and merge them to one richeditbox and then save back to the file.
You could like to see how to read/save rtf file sample from:
RichEditBox class
--James
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to align the text vertical in the edit box in mfc?

Hi,
I had an edit box of which height is increased than the default.Now the problem here is when I am entering text into the edit box the text is not present at the centre of the edit box, It is still aligned at the top.
After increasing the height of the edit box the text and cursor are aligned at the top as shown in the below figure.
But Actually how I want is the text and the cursor position needs to be aligned centre as shown in the below figure.
Note: "EDITTEXT IDC_EDIT_BOX,10,73,156,14,ES_AUTOHSCROLL"
Can anyone please help me how can I make the text and the position of the cursor to be aligned vertically i.e, to the centre of the control.
SivaV

If vertical alignment is not possible, then use an edit box without borders, having the default height, and place it inside a static control having
SS_WHITERECT style. (In MFC Dialog Editor, set the Type and Colour properties). Both of controls will be children of dialog. Use a proper tab order. Check if the style
WS_CLIPSIBLINGS is needed too.

Why are my LabView Dialog Boxes no longer modal when using the Example LabVIEW Operator Interfaces?

Hello,
I have a step in my sequence that pops up a modal LabVIEW dialog box. My LabVIEW vi uses the TestStand - Start Modal Dialog.vi and TestStand - Stop Modal Dialog.vi as described in the example and it works as advertised when I'm using the TestStand Development environment however when I use the sample Operator Interfaces distributed with TestStand the Dialog boxes lose focus. I have the VI Properties->Window Appearance set to Dialog and have followed all of the instructions I could find for making a dialog modal. I've also reviewed all the documentation I could get my hands on including previous posts on this board and didn't see anything obvious.
Does anyone have any suggestions as to what I may be missing? Has anyone else experienced this problem and come up with the solution?
I am using LabVIEW 8.0 along with TestStand 3.5.
Thanks,
RG

Hi RG,
Running the example modal dialog in the teststand3.5 examples folder and using labVIEW8.0, I notice that when the Dialog is displayed its not active, but it is modal to the OI. Clicking on the Dialog panel makes it active. If you try to click on the OI panel behind, you can not. Is this what you are seeing?
I am using the Full labVIEW IO as supplied with TestStand and the example VI in the modal dialog folder is as supplied.
The LabVIEW Adapter is still configured to use the active labVIEW developement environment.
If I run the same example, only this time using LabVIEW7.1, the Dialog panel is active.
There is a patch to take it to labVIEW8.01, at this moment in time I am not sure what the update fixes.
There does seem to be a problem with TestStand3.5 (engine) and LabVIEW 8.0.
Regards
Ray Farmer
Regards
Ray Farmer

Unable to include Operator Interface in TestStand deployment

Hello. I have created a test system using TestStand 3.5.
There is only one sequence file, and this sequence calls several VIs
that I have created in LabVIEW 8.0. I would like to distribute
this test system to a target computer, which will then run the default
Operator Interface. No bells and whistles, just plain and
simple. However, I'm running into problems.
First, I created a Workspace file in TestStand. I then added a
Project to it. In the Project, I added all necessary files for my
project (the sequence file as well as all of the custom VIs).
Then I proceeded to follow the TestStand reference manual in order to
deploy my system.
For reference, text in italics is the reference guide and text in bold is my comments.
Deploying the TestStand Engine
1. Launch the TestStand Deployment Utility by selecting Tools»Deploy
TestStand System from within the sequence editor.
I did this, and set up my build how I wanted it.
2. On the System Source tab, enable the Deploy Files in TestStand User
Directories option.
This option collects files from the <TestStand>\...\User
directories, so that any customizations that you have made to process
models, step types, language strings, and so on, will be distributed to
the target computer.
I did this, and copied my Operator Interfaces\NI folder to Operator
Interfaces\User. This would assure (I hope) that I would have the
default operator interfaces included in my project.
3. On the Installer Options tab, enable the Install TestStand Engine
option.
Done.
4. On the Installer Options tab, click Engine Options to launch the
TestStand Engine Options dialog box, which you use to select the
TestStand components that should be present in the installer.
Done. Everything is checked.
In the TestStand Engine Options dialog box, expand Operator
Interfaces»Full-Featured in the tree view.
a. Click the X next to LabWindows/CVI to include the
Full-Featured LabWindows/CVI Operator Interface in the engine
installation. The X should become a green checkmark.
b. Click OK to accept the new settings and close the dialog box.
This is where things go wrong. There is NO Operator Interfaces box in my tree view. It simply doesn't exist.
I've tried several different builds using different strategies.
I've done builds with the CVI operator interface in the User directory,
and I've also tried copying over the files manually. On the
target computer, I've always gotten either an error message (Could not
open the TestStand Engine), or else TestStand opens in evaluation
mode. In both cases, my custom VIs and sequence files are nowhere
to be seen. Can anyone shed some light on this? It's
driving me a bit crazy!
Thanks very much,
Brett Gildersleeve

Hi Brett,
Whenever you deploy your TestStand application to target machines, you will always needs a license. The licenses for distributing TestStand are different than for distributing LabVIEW and LabWindows/CVI code modules.
LabVIEW does not require you to purchase any run-time licenses for a deployment system. You can even run LabVIEW VIs in VI format (not executables) from TestStand without using the development environment and without an additional license.
In order to run LabWindows/CVI code modules, you will need the LabWindows/CVI Run-Time engine which is also available free of charge.
Regarding TestStand, you will need a license for each machine that runs a TestStand sequence. TestStand has three types of licenses which are the TestStand Development System License, the TestStand Debug Deployment Environment License, and the TestStand Base Deployment Engine License.
TestStand Development System License
The TestStand Development System License is required for any test sequence development and/or editing of existing TestStand sequence files that you perform within the TestStand Sequence Editor or programmatically using the TestStand API.
TestStand Debug Deployment Environment License
The TestStand Debug Deployment Environment License gives you maximum flexibility for deploying TestStand and LabVIEW, LabWindows/CVI, and Measurement Studio-based systems. This license allows you to install the development versions of TestStand, LabVIEW, LabWindows/CVI, and Measurement Studio, along with any corresponding add-on toolkits, so that you can debug your test application on your deployed test station. This license does not include the ability to perform any development tasks within the TestStand Sequence Editor or programmatically using the TestStand API.
The TestStand Debug Deployment Environment License has debugging capabilities including settings breakpoints, monitoring variable values, and stepping into test code directly from the TestStand sequence.
(Note: This license does not provide the software but rather gives you the right to install a previously purchased piece of software on the target machine.)
TestStand Base Deployment Engine License
The TestStand Base Deployment Engine License is the minimum license required for all deployed TestStand-based applications. This license allows you to deploy the TestStand Engine, a TestStand Operator Interface, and TestStand sequence files to the single test station for which the license is applicable.
The TestStand Base Deployment Engine License provides simple sequence debugging capabilities, including setting breakpoints and single stepping through test sequences in your Operator Interface. You cannot save sequences and open the sequence editor.
I hope this clears things up.
Best Regards,
Jonathan N.
National Instruments

Including Limits, Measurements in Simple Operator Interface UI

Dear Experts,
I am in the process of modifying OPerator Interface such at that it must also display Low Limit,High Limits,Measured Value, Units. I am sure that it is possible only through expressions. I want this Limit columns value to be updated during runtime i.e., it must display the same value as we use to enter using Edit limits for Numeric test, Measured value should be the value in Step.Result.Numeric or Step.Result.NumericArrya.
I could just manage to create a parameters in each Sequence & Subsequence Parameters.Limits.Low, Parameters.Limits.High,,Parameters.Limits.Unit & just hard code the values in these. But for Parameters.Measurements i could get values in runtime using RunState.Sequence.Parameters.Measurement. I know this is not more efficient way. This might work only for Action, Numeric Limit.
For reference i have attached Simple OI Top Level.vi(where i have made some modifications) all other supporting files you can find in TestExec.llb. I hope i have explained my problem. If anyone find any confusions in understanding please let me know.
If someone tried this before please share your knowldege. Expecting your greatest support.
regards,
Bharat
Attachments:
Simple OI - Top-Level VI.vi ‏177 KB

Hello Bharat,
Adam is out of town right now. It looks like the error you are getting is occurring because you do not have the TestStand 3.0 UI controls installed for LabVIEW. You can check this by making sure that you have a TestStand subpalette in both your Control Palette and Function Palette. If you do not, you can go to "Start >> Settings >> Control Panel >> Add/Remove Program". Find the entry "National Instruments Software" and click "change". Find "TestStand 3.0" in the list of NI software installed on your computer. Click on "modify". This will launch the installer. Follow the steps and make sure to enable support for LabVIEW 7.0 (there is a step with a tree of features that you choose to install).
I took the liberty of saving the latest VI that was posted to my computer. I opened it with LabVIEW 7.0. This was verified by going to the "About" LabVIEW Dialog box that displays the version. I was running on the TestStand 3.0 engine. Besides the fact that you can only have one engine active on a computer at a time, I added a message popup to my TestStand 3.0 Front End Callback so that it would display when an instance of the engine is created. I did save the VI again and am not attaching it to this post. It should certainly work with LabVIEW 7.0 and TestStand 3.0 if everything is installed correctly.
Thank you for contacting National Instruments. Take care and good luck!
Regards,
Aaron B.
National Instruments
Attachments:
Simple OI - Top-Level VI.vi ‏177 KB

Rich Text Box Issue - Expand to show all Text

Hi everyone
I'm having a pretty frustrating issue with the rich text box when viewing a line item (not when editing the item, but viewing the item)
I want my rich text box to expand with the text, which I have changed in the options on InfoPath with the "Expand to show all text" scrolling option. However, in IE, the table row will expand, but the actual rich text box will not and I'll have
a scroll bar there and you cant see all of the text at one time. If I look in Chrome, then it works the way I want and I can see all of the lines of text that were entered into the rich text box.
The only solution for IE to work correctly is to change the Display settings to "Enable enhanced rich text content...". But the big issue with that is now you can no longer highlight the text (the highlight disappears right after highlighting it),
and the users will need to copy text from the text box, so it renders the "enhanced" rich text box useless for us
It's kind of a lose-lose situation that I'd love to find the solution for

I guess a better solution would be how can you highlight text from an enhanced rich text box, because changing these to "rich text box" gets rid of font colors in the pre-existing data.
The original problem was that they couldn't highlight text unless they went into edit mode

I am trying to use the T. S. operator interface I need to add pass fail and error

Hello:
I am using Labview 6.1 and Test Stand 2.0
I have made some modification to a copy of the T.S. Labview operator interface. How do I get the pass/fail or error from test stand to be pass to LabView so I can tell the operator that the unit pass or fail the test. I do not want to use the Test UUTs. I want this to be very low operator response.
Message Edited by Toro on 02-28-2006 01:52 PM

Not sure if this is available in the earlier versions of TestStand, but I think so.
You could post a UI Message, from your execution entry point in the process model, to your User Interface indicating the pass/fail/error status when a test run is complete. You will need to handle the UI Message in your Operator Interface. See TestStand II Customisation course notes for handling UI Messages.
The data passed in the UI Message can be anything you like, the UI Message handler in the User Interface will have to process the message and update the display as required.
Hope this helps
Steve
Message Edited by SercoSteve on 03-01-2006 10:02 AM
There are 10 types of people in the world that understand binary, those that do and those that don't.

Sequence file path programmed in operator interface

Hello,
I do not want to load the sequence file with the button OPEN_FILE etc.. for example how it is done in th Simple Operator Interface. I want to programm the path and the sequence file name in the Operator Interface. How can I do this that the correct file will be loaded
regards
samuel

I try to explain what you have to do without an example, because it is realy simple, and so we have no version dependency ;-)
I used the "simple operator interface" installed with TestStand (..\National Instruments\TestStand 3.x\Operator\Interfaces\NI\Simple\LabVIEW\TestExec.llb\Simple OI - Top-Level.vi). I added the method mentioned above in front of the Event-Structure (See attached picture) and added a path-constant, to define which Sequence should be loaded automatically.
Try this out. It works fine on my machine (LabVIEW 8.2.1, TestStand 3.5, but should be independent of Versions as long as you have TestStand 3 and LabVIEW 7 at least).
Hope this helps!
André
Message Edited by Andre_Saller on 04-25-2007 11:34 AM
Attachments:
Autoload.jpg ‏167 KB

Step_description unknown variable error in built operator interface

I'm getting the following error when I execute a seq. from a built LabVIEW operator interface:
Error evaluating expression
Unknown variable or property name 'STEP_DESCRIPTION'.
Error accessing item 'STEP_DESCRIPTION'.
Some searching is leading me to an issue with the localization languages files? Not sure what exactly.
Message Edited by Michael Aivaliotis on 11-06-2007 01:09 PM
Michael Aivaliotis
VI Shots LLC
Attachments:
1.png ‏10 KB

Here is a guess: try right clicking on the step list and select a different step list configuration. If the problem goes away, then your current step list configuration has a column specified by expression and there is a problem with the expression.
Message Edited by James Grey on 11-06-2007 03:14 PM

Programatically Loading Several Sequences Using LV Simple Operator Interface

I am playing around with the supplied LV(2009) Simple Operator Interface for running TestStand (4.2) and hoping that someone can point me in the right direction.  I know this may be too generic for a concise solution, but hopefully I can get some suggestions on the best approach for this. Here is a short description of what I am trying to accomplish.
I am testing 2 unique UUTs on a single test fixture that is controlled by a PCI-7831R DAQ. Each UUT will have a unique serial number and report generated. Therefore, I am using 2 unique sequence files created using TestStand. Basically, I want to be able to read in a barcode on the test fixture and have the operator interface load the 2 unique sequence files based on information contained in the barcode. The operator will then hit a button to start the sequence file executions.  I want the first sequence file to run and test the first UUT. Once the first sequence file is finished, I want the second sequence file to load and run on the second UUT.
I can use the simple operator interface to load both sequence files. I then have to select the combo box to select which one I want to run. This works fine, however, I am trying to automate this so that the operator doesn't have to open the files and continually use the combo box to select sequence files.
Any ideas or suggestions would be greatly appreciated.

I have figured out a solution (for my initial application at least) of programmatically loading the sequence files. When the operator interface first starts, there is a prompt where the user will scan a barcode that is loaded on the front of the fixture. For all of our product lines, we will have a unique format for the fixture barcode. Included in this barcode is a product specific software ID number. I create a folder with the same software ID number and store the sequence files there. I then parse the barcode and open all *.seq files in that folder. I have this working correctly now.
Once the sequence files are opened, the user must scan each UUT ID barcode before installing them on the fixture. The intent is to have both UUTs installed on the fixture at the same time so they can be tested serially.  If, however, they do not scan one of the UUTs, it will not be tested. Basically this is due to the fact that they may want to run only a single board. Once all of the UUT barcode scanning has been completed, I have another button that will execute the sequence files using the 'Single Pass' execution entry point. I agree that the 'Single Pass' and 'Test UUTs' points should be hidden from the user. Once the execute test(s) button is pressed, it will check each UUT barcode to make sure that it is valid. If both UUT's have valid barcodes, it will run the first UUT and then the second using the 2 sequence files that were previously loaded, otherwise, it will run only one or the other. The UUT(s) will then be removed and the process starts over again from the UUT ID barcode scanning. They will not have to scan the fixture barcode again since the correct sequence files have already been loaded.
Currently I have the UUT/Sequence File associations hard-coded in the UI. I will need to put my thinking cap on so that as we increase the product lines (several are already in the pipeline) we can use the same UI without any modifications. Scalability is King!

User manager in operator interface

How can I add/edit list of users in TestStand Operator Interface?

Hi hss,
In your teststand examples is a useful example called CreateDeleteUsers.seq
It demonstration creating and deleting of user by running a sequence and using the TS API calls.
To simply add the capababilty you require to your OI, all you need to do is add it to the tools menu.
See attached bmp showing CreateDeleteUsers.seq linked in the Tools Menu. Also note that its only available in the Operate Interface.
Beware, this example is only a demonstration and requires additional error checking such as checking for duplicate entries.
Hope this help
Ray Farmer
Regards
Ray Farmer
Attachments:
Customize_Tool_Menu256.bmp ‏321 KB

Add limits and results columns to Operator Interface

Hi,
I am using TS 4.0.1 and CVI 2009. I want to modify the CVI Operator Interface to display columns with the test result and the high and low limits. I tried to modify the properties of the SequenceView control on the operator interface by adding columns, but the changes are not seen when I run theOI.
How can this be done?
Thanks
John

John,
the display of the requested information depends on the "binding" of the control. The SequenceView control can be connected as SequenceView (ConnectSequenceView of the Sequence File View Manager) or as ExecutionView (ConnectExecutionView of the Execution View Manager). The later connection displays the result during execution like this:
But it will only display during execution, not during edit time! (Result is always a runtime property because why should a test sequence return any results during edit time??)
Limits are displayed in the description of the NI steptypes like seen here:
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

How can I view TestStands Operator Interface front panel, from a VI, while a test is taking place.

I need to view the sequences and steps that are displayed during a test session while running TestStand. Except I would like to view this in a LabVIEW front panel

JD,
I'm not sure if you're asking to be able to view the actual code module's front panel (ie. VI front panel) while it's executing, or if you just want to see the steps and overall sequence in a VI front panel. If the latter is true then you can use the simple LabVIEW operator interface that ships with TestStand, as Dennis mentioned in his answer. This would indeed be a great place to start if you want to add any further functionality to the operator interface. If the former is true and you want to see the actual VI front panels of the steps as they execute, you can check that box "Show VI Front Panel" from the "Specify Module" window in TestStand.

Remove step icons from CVI Operator Interface to improve execution performance

The CVI Operator Interface updates the icons for each step (lower right) when tracing is enabled. Can these be stopped but the steps still visable and would this improve execution performance.

Hi Dave,
I take it you are using the old style Teststand Operator Interface.
The only way would be to modify the code in the exedisp.c, in UpdateOnStepChange() function. Just comment out the SetCtrlBitmap() function there are two calls in this function.
As to whether it is going to make a noticable different in performance, well that depends on the spec of the controller (PC), graphics card etc. you are using. But you probably wouldn't notice any diference.
Before you make any changes, copy the sub-folders from the NI folder to the User folder and work from the User folder.
Regards
Ray FarmerMessage Edited by Ray Farmer on 05-07-2005 06:29 PM
Regards
Ray Farmer

Rich Edit Box in MFC Operator Interface

Similar Messages

Maybe you are looking for