04-03-2019 12:53 PM
There is an ini option for use default run time menu that applies to new vis. I suspect someone might have changed that from default on a development machine and did not add the *.rtm files to the code repository. The exact behavior in that odd situation is not well defined. (You shouldn't do that!)
You can write a scripting vi to inspect and reset that property.
Posted by phone. Kudos for an example scripting vi.
04-03-2019 12:59 PM
I did a clean install of LV2018 and I'm still seeing the problem. How would I modify the ini?
04-03-2019 01:04 PM
That ini setting only effects new vis. If you have a vi created with the wrong setting you need to use scripting to reset it since it is not runtime writable.
04-03-2019 04:37 PM
I haven't used scripting before. But how would I create a vi with the wrong setting? Is there a good scripting resource you recommend?
10-26-2022 06:37 AM
Hi all
I don't see the problem was solved and cant find other information about this issue
I have the same one - all at a sudden - no any hotkeys with CTRL are working in Labview. Both in 2021 and 2012 versions, that are installed on this PC.
I can not Ctrl+C, Ctrl+V, Ctrl+A, Ctrl+B, CTRL-H.. Anything!
The most strange is - once I opened Options of Labview - I could use CTRL-H to show context help panel if some vi is opened. It also recognizes the combinations to change hotkeys. Once Options are closed - no hotkeys just beeeeeeep..
Even if no any VI is opened - in Search field one can't copy/paste the text - it types just a c v h and nothing else.
I tried many times to restart Labview, restart PC, already started to crash Windows registry.. Nothing helps. More ridiculously - this morning I started Labview, and it works! But the joy was too fast - again just beep in response to CTRL+C five minutes later.
And all of it is only Labview issue - all other programs work fully normal with Ctrl combinations
I am going mad... HELP!
10-26-2022 09:09 AM
Try deleting LabVIEW.ini. a new file will be created when LabVIEW is opened with default settings.
10-27-2022 09:10 AM
Thanks for suggestion, but it did not work. And as I told - it happened in two different versions of Labview, so ini file is definitely not the problem - two of them (2012 version was just for the test once the problem happened)
I completely reset all NI products. So full clean, partially with a registry also. After clean install the problem did not appear, but, again in 5 minutes it is again there.
Even more - now I have a problem that mouse operates only in one program. One can not switch to another program by hovering or clicking on it, taskbar also does not respond. One can only use keyboard for swap between programs. Once one kill Explorer, one can move to other programs and operate and almost everything seem to work Ok with mouse, but Labview still can use Ctrl+whatever.
I believe something on ground is corrupted - mouse driver, keyboard driver, and the way programs work with both..
UPD. You will not believe me. It is a mouse. Not driver, not some software lag/bag - just a mouse itself.. Once unpluged and PC restarted (laptop actually) - everything is Ok. I sit already several hours and no any issue appears as nothing would ever happen. And if I flash back - all problems started when I aimed to modify the VI (add on-flight-data-save), wanted better control than touchpad and connected the mouse.
Two days of wasted time for unistall/install.. Unbelievable.
10-27-2022 09:19 AM
I hate it when you convince yourself it is a SW problem and it turns out to be a HW problem. At least you figured it out!
10-27-2022 09:19 AM
Is this OS a garunteed genuine windows?
10-27-2022 09:32 AM
Yes, OS is fully genuine Win7. I have even run "sfc" - no issues with system files were detected.
2 Frozen - the problem did not appear immediately and in full color. And I even tried to unplug the mouse! But the problem with Labview still existed so I attached it back. But I did not restart laptop that time..
Only when a "second" problem with Explorer appeared, I started to assume it can be a mouse or its driver. First the problem appeared only with hotkeys and only in Labview.