LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

how can i be notified when abort execuation button is called


@DerrickB wrote:

FYI Ctrl+. is always available whether toolbar/menu is displayed or not.


I don't believe this is true for compiled executables... I certainly hope the OP is not expecting end users to run programs from the DEV environment. 

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 11 of 17
(801 Views)

@DerrickB wrote:

FYI Ctrl+. is always available whether toolbar/menu is displayed or not


If you hide just the abort, (and optionally the entire menu), CTRL+. is not available.

 

The VI can still be aborted, if it's used as a SubVI and it's caller is aborted, or with the abort method (if the Vi is top level).

 

Especially when designing a reuse library, you can't impose requirements like "don't abort your code" on users. The library should simply behave...

0 Kudos
Message 12 of 17
(788 Views)

I tested it, even tested with modal and other settings, Ctrl+. worked with no menu or toolbar visible.

0 Kudos
Message 13 of 17
(769 Views)

@DerrickB wrote:

I tested it, even tested with modal and other settings, Ctrl+. worked with no menu or toolbar visible.


How about when it's an executable instead of running in the DEV environment. 

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 14 of 17
(766 Views)

I did not test an exe, I thought we were talking about dev stuff. It doesn't work in an exe

0 Kudos
Message 15 of 17
(748 Views)

@DerrickB wrote:

I tested it, even tested with modal and other settings, Ctrl+. worked with no menu or toolbar visible.


Yes, you have to explicitly hide the abort.

wiebeCARYA_0-1673610873869.png

 

0 Kudos
Message 16 of 17
(713 Views)

@DerrickB wrote:

I tested it, even tested with modal and other settings, Ctrl+. worked with no menu or toolbar visible.


I just did as well. At least in 22Q3 dev environment:

 

  • Deselecting "Show toolbar when running" does not disable the keyboard shortcut.
  • Deselecting "Show Abort button" does disable the keyboard shortcut.
  • The default "Top-level application window" preset deselects both of those options, which (as you might expect) does disable the keyboard shortcut.

 

@Peterboshra wrote:

("note I shouldn't remove this button")

 


But you really should.

Message 17 of 17
(692 Views)