Check marks on custom run-time menus

Is there a simple way to add a check mark for currently selected item on custom run-time menus?
The only method I have found is to fire off of the "Shortcut Menu Activation?" event, grab the menu reference, and basically recreate the shortcut menu with the proper check marks based on boolean values. This method just seems ... cumbersome for something that should (in theory) be fairly common. I can't help but think there is a better solution.
Thanks!
Solved!
Go to Solution.

Hi Bown,
you can assign custom menus with the menu editor to your controls/VIs. They will be saved as rtm file.
Using the known tag names of such custom menus you can set the checkmark for your tags without rebuilding the menu on activation each time…
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Similar Messages

Custom run-time menus within dynamically called sub-VIs?

How do you use custom run-time menus within sub-VIs that have been dynamically called? I'm using Labview 6.02.

Since you say within subVIs, I am assuming that you have the subVIs open their front panels when called. Each subVI must have the RTM defined when the subVI is created. You can use the same RTM for each one (use the open function in the menu editor).
If necessary, you can dynamically add and remove menu items using the Application Control->Menu functions. I have some subVIs that add items to the main RTM when they are loaded and remove the items when they finish.
Rob

Creating customized run-time menus

I am trying to create a customized run-time menu when I right click on a tree control. I can disable the existing run-time/pop-up menu but would like the ability to use a different customized menu.
I can simulate a run-time menu by using creating a VI that functions in a manner similar to the menu but would prefer the ability to create and process and customized run-time/pop-up/floating menu.
The menu is always of a fixed size with all items enabled. I do not need the ability to modify this menu within the application.

There is an LTR article by David Ritter called "Contextual Pop-Up Menu Programming" that shows a method similar to yours. It is well worth a look.
-Jim

Preserving run time menus

The problem is that applications do not preserve custom run time menus applied to graphs or controls once the executable is run on another machine, or an installation is built and installed on another machine. I have tried advice from this board about saving .rtm to alternate llb's, to the same destination/support, opening from within development vi and saving to the same path as development vi.
Surely the concept that you want to define a custom menu for a control and have your customer see this one when he installs is not a foreign concept within Labview. How can this be done?

Here's how the two workarounds would play out in this situation:
In the first workaround, you'd have to open the run-time menu editor for each control individually and choose to save the run-time menu to the control instead of the file. I don't think this is a very risky procedure, but it would be tedious. One thing to keep in mind is that in order to get the prompt to save the menu to the control or to a file, you'll need to make some small change to the menu. For instance, you could press the add button to add a temporary item and then the delete button to delete it. Then when you close the menu you'll see the option to save the menu to a control. I suppose this step is the only real risk in the process
In the second workaround, you'd have to create 3 or 4 new event structure cases, one for each of the different run-time menus you want to display. Then you'd have to register each separate event for all the controls that correspond to that particular menu. This seems a little more risky, because the new code might induce bugs into your system, or you might forget to register the event for a control, or register the wrong event for a control.
Jarrod S.
National Instruments

Custom Run-Time Menu Not Found in User.lib

Our Instrument Run-Time Menus are getting lost.
This is because we have some computers that are 32 bit and the code is located at
C:\Program Files\National Instruments\LabVIEW 2011\user.lib\InstrumentDrivers
Other computers are 64 bit and the code is located at
C:\Program Files (x86)\National Instruments\LabVIEW 2011\user.lib\InstrumentDrivers
The directories are thus slightly different because of how Windows treats the location of 32bit LabVIEW running on a 64 bit machine.
Does anybody have an easy work around?

I'm confused by "lost". Do you mean when you build the path to your custom menu within your vi or are running some executable? Is this code you have written? If so, then maybe a simple check when initializing the paths might work.
If it is as simple as just having to decide between those two directories, then I would just check to see if the win64 bit directory exist, using "file directory info" vi. If it doesn't' exist you should get an error, then check to see if the other path exists, it should hopefully, and use that.
Not sure if this is what you need.

Custom Run-Time Menu error when named "FileMenu.rtm"

Discovered an interesting "feature" (error?) in LabVIEW 2009 when using custom run-time file menus.
If you create a custom run-time menu (.rtm) and name it "FileMenu.rtm" the menu will not function correctly in executable format.
In my LabVIEW Project, any VIs which called this custom file menu worked correctly in the project, but when I built an executable, the VIs defaulted to the default file menu. This was not due to a corrupted .rtm file or the file not being included in the executable. Instead after extensive debugging I determined that the name "FileMenu.rtm" is somehow reserved in LabVIEW and any executables that are built have the custom run-time menu overwritten by the default. The tricky part of this error is that it goes unnoticed while the code is still in development and only presents itself after being built into an executable.
Simply changing the name of the file fixed the executable run-time menu.

Chris,
Thanks for trying it out. It seems that my forum post may have been a bit rushed.
I tried to duplicate the problem in a new project from scratch and similarly was unable to reproduce it. I will try more soon, and in doing so perhaps reveal the true underlying problem. I would post the original code but it is proprietary.
I was running LabVIEW 2009 and Windows XP when the problem first presented itself. I updated to LabVIEW 2009 SP1 as part of my debugging and the problem still presented itself.
V/R,
~David

Problems with executing customized Run-Time menu from a sub-vi imported from the main vi.

I am having trouble executing Run-Time menu from the sub-vi.
Currently my main vi program, which is the first thing that I open up to acquire data from different sources (i.e. dll’s, scanners etc.) opens up a number of sub-vi’s.
I have created several sub-vi’s, which are opened from the main vi’s customized Run-Time menu that I have created (i.e. dsp file). I am using the open panel.vi to open other sub-vi’s. I don’t have any problems opening any number of sub-vi’s through the main vi’s menu.
I would also like to have the option to open other sub-vi’s from any sub-vi’s menu. I succeeded in exporting the Run-Time m
enu from the main vi to the sub-vi using the property node properties however nothing happens (I hear a beeping sound) when I click on the sub-vi’s menu. I don’t know what I am doing wrong. I would really appreciate it if someone can attach a sample code using Run-Time menus on sub-vi’s imported from the main vi.
Thanks
Nish

I don't actually have any VIs like this. It might be easier to take the menu and just add it to the VI during development. Then it will always be there. It might be easier than doing this with Property Nodes.
J.R. Allen

Custom Run Time Menu (.rtm) for a tree control doesn't appear in LV executable

Hello,
I am using a custom run time menu (.rtm) for a tree control in LV. When I right click on the control the run time menu appears in the LV development environment. However the run-time menu does not appear when run the executable installed by the installer I created. I tried including the .rtm file with the installer, but it did not fix the problem.
Please let me know if any ideas.
Thanks,
Russell

This is a known issue and has been reported to our R&D engineers for further investigation (CAR# 3T2E57V2). The workaround is to embed the run-time menu in the control instead of the separate .rtm file. To do this, make a minor change in the shortcut menu (for instance, add a dummy item then delete it), so that the shortcut menu editor will ask you to save the new menu. When it prompts you, choose to save it with the control instead of to file.

Break execution after custom run-time error handler callback

I am using Teststand 2010 SP1 and have written a custom runtime error handler based on the ErrorHandlerExample example that ships with TestStand. It has been implemented as a StationPostStepRuntimeError callback in my Station Callbacks folder. I have modified the example as follows:
(1) Added code to turn off the UUT transmitter if it was on.
(2) Added a call to an executable that sends an email to the currently logged in user.
(3) Calls the standard TestStand run-time error dialog using the Engine DisplayRunTimeErrorDialog method.
(4) Processes the user's selection, then turns on the UUT transmitter for any option other then Abort.
The callback also checks the status of the Break and "Don't Show again for this execution" options selected by the user. If the user selects Break then the only option I can find is to call the API Execution.Break() method which breaks the execution right there in my callback. The user then has to single step there way out of the callback. Is there a way of instructing TestStand to complete the callback execution and break immediately after completing the callback (i.e.at the step following the error)? I've zipped up and attached my modified sequence.
Alternatively, is there a better way of doing this?
Regards,
David
Solved!
Go to Solution.
Attachments:
StationCallbacks.7z ‏13 KB

Didn't have a chance to try it yet but maybe StepOut is your solution?
From the TS Help:
StepOut Method
Syntax
Execution.StepOut
Purpose
Resumes the execution from a suspended state and then suspends the execution again after execution of the current sequence completes.
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Checking dynamic query at run time

i need to check whether the query is valid or not at run time. The query will be formed based on the column name, table name, and where clause. this query is purely a select statement. if column name and table names are diff then system should display an error msg. i have more than 10 tables and the table name will be selected from LOV. i should be allowed to enter the condition for where clause also ar run time and this condition column should also be validated.

Hi,
I think you only want to see if your select statement has compilation error or not because when you use dynamic statement it doesnt show the compilation erro if the statement has it or not. What you can do is add an item say "stmt" in your control block. change the property to multi record so that you can see multiple lines in that item and make the lenght say 2000. Now assign your statement into "stmt" for example
:control_block.stmt := 'select ' || col1
                    || ','
                    || col2
                    || ','
                    || col3
                    || ' FROM '
                    || table
                    || ' where ' || conditionput this statement on any button on when-button-pressed trigger. When you will press the button on run time you will see the statement. Run that statement on sql*plus or toad and check if there is any problem in the statement.
Hope this helps
Ghulam

Make Custom (Run-Time Error Dialog Box)

I would like to Customize the Run-Time Error Dialog Box
bcos I want to use H/Wbuttons (need to Init the H/W) & not mouse to navigate thr the box
is the Dialog box available in Labview also

Hello aparab,
You won't be able to edit the dialog in LabVIEW for sure. Not sure if NI provide CVI / C++ source for that.
You can have your own dialog by handling the run-time error using SequenceFilePostStepRuntimeError callback. Look at this example:
http://zone.ni.com/reference/en-XX/help/370052M-01/tsexamples/infotopics/callbacks_sequencefileposts...
The example ships with TestStand as mentioned in the above link. You just have to use the information which will be in Parameters.Step container for error details and to customise your dialog.
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

Run-time menus and save with control

I created a custom shortcut menu (on an XY graph) and saved it by selecting "save with control". This worked fine while I was running LabVIEW but did not work in the executable version that I created. The label of my XY graph was something like "X/Y GRAPH". I guessed that LabVIEW was trying to save my shortcut menu by using the string "X/Y GRAPH" and that the "/" was causing the problem. I changed the label to "XY GRAPH" and everything now works fine. Does this count as a bug? Do widget labels need to use legal filename characters if I am going to create custom shortcut menus?

Hi Oyester,
I have reproduced your situation and this does not count as a bug--the slash counts as a special character and the filenames have to be alphanumeric. I hope that answers your question.
Ipshita C.
National Instruments
Applications Engineer

Shortcut run-time menus and ActiveX

I'm working on a Labview video player with four instances of VLC embedded in it, as ActiveX controls. After some help from the forum, it runs very well, but I would like to implement custom right-click menu's for the ActiveX windows. Currently, nothing happens when the user right-clicks on the ActiveX control. I've tried enabling the shortcut menu, editing the menu, etc, and nothing worked. I've tried overlaying another transparent control over top of the ActiveX window, but the ActiveX control seems to want to be on top no matter what I do. Any ideas?
Running LV 8.6.1f

i tried the same with windows media player since i dont have VLC.. Did you use the shortcut menu activation property? see the attched vi
Regards
Guru (CLA)
Attachments:
1.vi ‏10 KB

Custom run time error message into C# UI

Hi,
I'm trying to get the error message for the last step into my C# UI (using TestStand3.5).
I've tryed the GetRunTimeErrorMessage in the UIMsg_Trace message event, but it doesn't work.
Probably I should use the PostStepRunTimeError callback instead? Is there a sample code available in C# using it?

I'm getting the error code and the message, se below, but I also want to get the location info as in the standard TS error popup.
The boolean Occurred parameter seems to be false even if I get an error. Is it reset to false or something?
int frameID = 0;
errorCode = axExecutionViewMgrs[index].Thread.GetSequenceContext(0, out frameID).AsPropertyObject().GetValNumber("Parameters.ErrorLoad.Code", 0);
details = axExecutionViewMgrs[index].Thread.GetSequenceContext(0, out frameID).AsPropertyObject().GetValString("Parameters.ErrorLoad.Msg", 0);
location = axExecutionViewMgrs[index].Thread.GetSequenceContext(0, out frameID).AsPropertyObject().GetValBoolean("Parameters.ErrorLoad.Occurred", 0);

Application's run-time shortcut menus don't work on local drive.

The run-time menus in my application don't work, unless I run the application from the location where it is built. This project has an application build specification, and an installer build specification. The installer specification, copies the app to the local drive. But the run-time shortcut menus do not work when the app runs. Nothing happens when I right click on the control. However if I run the same app from the network drive, where the application build spec builds it, it runs fine. When I have the application build spec build the app directly to the local drive, it works fine. The exe, ini and aliase files are identical. Why does this app run differently depending on which drive it's on? How can I fix it so the run-time shortcut menus work on the target machine? Any ideas?

Hello, I believe that when you create a custom run-time menu it gets saved to a file. My guess is that you are not including this file as part of the build specification for the application. The file likely exists in the build directory but does not on the target directory which is why it no longer works. If that does not fix the problem, let me know and I will see if I can figure something else out.
Regards,
Burt S

Check marks on custom run-time menus

Similar Messages

Maybe you are looking for