LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Ctrl + . (period) doesn't seem to be working (and aborting my VI).

Solved!
Go to solution

I checked this KB already.

Attaching trimmed VI (saved in 2017).

 

Could find where is the mistake or is it a bug?

0 Kudos
Message 1 of 8
(2,258 Views)

Hi scofield,

 

why do you need to password-protect your VI?

Do you think this helps in debugging your VI?

 

Your VI just contains an event structure, waiting for a panel close event.

And it stops when I press <Ctrl + .> !

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 8
(2,249 Views)

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.

0 Kudos
Message 3 of 8
(2,244 Views)

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.

FireFist-Redhawk_0-1594658121536.png

 

Redhawk
Test Engineer at Moog Inc.

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.

Message 4 of 8
(2,210 Views)

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 + .>

0 Kudos
Message 5 of 8
(2,173 Views)

Anybody knows about this, why the <Ctrl + .> shortcut doesn't abort a running VI with a custom runtime menu?

0 Kudos
Message 6 of 8
(2,094 Views)
Solution
Accepted by topic author scofield

Same deal I would say... go to Edit -> Run-Time Menu... and make sure this is there:

FireFist-Redhawk_0-1595442531791.png

 

Redhawk
Test Engineer at Moog Inc.

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.

Message 7 of 8
(2,088 Views)

@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

0 Kudos
Message 8 of 8
(2,082 Views)