07-13-2020 10:09 AM
I checked this KB already.
Attaching trimmed VI (saved in 2017).
Could find where is the mistake or is it a bug?
Solved! Go to Solution.
07-13-2020 10:25 AM - edited 07-13-2020 10:26 AM
07-13-2020 10:29 AM
My bad about password protection, it was not intended.
Attached is the code with password removed.
At my end <Ctrl + .> is not working at all.
I also opened 'on screen keyboard' and tried that just to be sure that its not because of keyboard settings, but no luck.
07-13-2020 11:35 AM
Unfortunately CTRL+. works just fine to stop that VI for me so I can't reproduce your issue. Go into your options and confirm that the shortcut hasn't been messed with.
Saying "Thanks that fixed it" or "Thanks that answers my question" and not giving a Kudo or Marked Solution, is like telling your waiter they did a great job and not leaving a tip. Please, tip your waiters.
07-13-2020 03:04 PM - edited 07-13-2020 03:12 PM
Thank you Andrew.
I just realized that its because of 'runtime menu' (.rtm file).
Actually this VI has an associated runtime menu and when I shared the VI, I never included the RTM file.
On my end, if I remove the custom runtime menu then I'm also able to use <Ctrl + .>
07-22-2020 01:11 PM
Anybody knows about this, why the <Ctrl + .> shortcut doesn't abort a running VI with a custom runtime menu?
07-22-2020 01:29 PM
Same deal I would say... go to Edit -> Run-Time Menu... and make sure this is there:
Saying "Thanks that fixed it" or "Thanks that answers my question" and not giving a Kudo or Marked Solution, is like telling your waiter they did a great job and not leaving a tip. Please, tip your waiters.
07-22-2020 01:40 PM
@scofield wrote:
Anybody knows about this, why the <Ctrl + .> shortcut doesn't abort a running VI with a custom runtime menu?
Since typing in <CTRL + .> is a shortcut to the Operate>>Stop command in the menu, I think it would make sense that removing it from the menu would disable <CTRL + .>. That way, you can choose to prevent users from exiting the VI through that keyboard shortcut. Otherwise, the user would always have a way to interrupt the VI.
As @FireFist-RedHawk says, if you want that option available, you can include it in your custom menu.
-joeorbob