01-12-2023 08:58 AM
@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.
01-12-2023 09:47 AM - edited 01-12-2023 09:52 AM
@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...
01-12-2023 11:27 AM
I tested it, even tested with modal and other settings, Ctrl+. worked with no menu or toolbar visible.
01-12-2023 11:30 AM
@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.
01-12-2023 03:59 PM
I did not test an exe, I thought we were talking about dev stuff. It doesn't work in an exe
01-13-2023 05:54 AM
@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.
01-13-2023 09:29 AM
@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:
@Peterboshra wrote:
("note I shouldn't remove this button")
But you really should.