10-14-2019 12:18 AM
Hello All,
I need to open subVi in VI with F- button on keybord.
This subVi will be some settings, so it should be opened on F- command.
Can someone advise how to do this?
Thank you.
Solved! Go to Solution.
10-14-2019 01:31 AM
Hi milan,
are you talking about the <F> key on your keyboard? Or are you talking about any of those F1-F12 "function" keys?
Options:
- for function keys you can set a key navigation for a button on your frontpanel to toggle. Then use an event structure or a simple case structure when the button is toggled…
- for any (other) key you can use an event structure to catch all key press events in the front panel: just check if the <F> key is pressed, then call your subVI…
10-14-2019 03:15 AM
Thanks Gerd, that works.
But now I have problem to open subVI… Button react, but VI is not opened.
10-14-2019 03:27 AM
Hi milan,
@milan87 wrote:
Thanks Gerd, that works.
But now I have problem to open subVI… Button react, but VI is not opened.
So there is a problem in your VIs. Did you try to debug your VIs?
Do you get any error on the RunVI method? Is the subVI started? Did you set the VI properties of the subVI to show its frontpanel when called?
General advice:
We cannot debug images with LabVIEW. When you have problems with your VI(s) then you should attach them!
10-15-2019 02:30 AM
Hello again,
i manage to open VI by clicking on button, but in development environment. Problem is when I create .exe, then VI cannot open that ''config'' VI from main VI.
I changed path for VI, to find application reference, but still unable to open...
In attachment there are all subVIs...
If someone could advise, how to solve this?
''Config'' VI is used to read and write data in ''config1.ini''...
10-15-2019 05:26 AM
@milan87 wrote:
Hello again,
i manage to open VI by clicking on button, but in development environment. Problem is when I create .exe, then VI cannot open that ''config'' VI from main VI.
When you compile into an .exe the compiler doesn't know that you're referencing that file, and you need to include it in the "always include" section. Also, the path changes, so that path constant needs to be handled. A better alternative is to use a VI ref constant to that file and use the name or path property. That way the compiler know you need it in the .exe and the path is automatically corrected.
/Y
10-18-2019 03:42 AM
Hello All,
one more question regarding this topic...
Button works normaly by pressing F5 on keyboard.
Next, I would like to hide that button, but to keep command on F5.
When I hide button, I cannot call it by pressing F5.
Can antone sugest solution for this?
Thank you.
10-18-2019 05:08 AM