Customizable context menu

[cy...]

hello forum

thanks NI for the new features in LabVIEW 2019, so far I am liking most of the things you have done; except for that 1 item, context menu change

Why change the context menu (on right-clicking wires)?

2010-2018 1..3: clean up wire, create wire branch, delete wire branch (7.1...7.3: create constant, create control, create indicator)

2019 1..3: create constant, create control, create indicator (4..6: clean up wire, create wire branch, delete wire branch)

surely NI have reasons, but can try implementing a customizable context menu as a feature instead? I used to be able to write or edit my codes with muscle memory, but now I spend more time undoing things... 

maybe the next patch? 

[crossrulz]

NI has clear evidence that the Create Constant/Control/Indicator are the most commonly used items.  So it really was done for a reason.  Give it some time and you will surely get accustomed (or so I am told, I have not gotten to install 2019 yet).  But for those who refuse to conform, you can add this to your LabVIEW.ini file: PopupMenus.ElevateCreation=FALSE

As far as customizable context menu, you already can: LabVIEW Shortcut Menu Plug-Ins

[joerg.hampel]

You might wanna watch Darren's NIWeek presentation and hear from the horse's mouth why that changed: bit.ly/labviewspeed 

[AristosQueue (NI)]

@Crossrulz : Alas, the right-click menus can be customized EXCEPT for the prioritization of the three Create items. Those are applied AFTER all the plug-ins have already run. This is the one part of the context menus you cannot programmatically adjust.

@Cy : As mentioned above, there is a config token to turn this off if you do not like it. But I encourage you to take a couple weeks to use it... it's been a major time savings for nearly all G users that we've observed. Those three menu items are used all the time, and getting them elevated and into a fixed location really improves speed. Muscle memory is a key thing for us to think about between versions, and we do not change it lightly (I do a hefty amount of G programming myself).

Because of the existence of the config token, I'm going to recommend NI decline this idea. We will continue to monitor customer response to this change in LV 2019, but thus far the reception has been largely positive, making us confident that this is the right decision going forward.

[Darren]

Declined for reasons listed in AristosQueue's reply

[cy...]

wow that escalated quickly

I have not proposed to reversed the option, but to make the option to be customizable. rather than discussing/exploring on the idea, it was declined from day 1. Kudos given... 

let's look at the probable reason why a person will right click on the wire, is it to perform wire operations (cleanup, create or delete branch) or to create constants (that doesn't connect) or controls (that would break the wire)? I would say it make more sense in right clicking input terminals to create constant/controls and output terminals(/wire) for indicators. 

[cy...]

Kudos disabled 

[cy...]

@AQ: can you tell me where can I find this token?

[cy...]

pardon me for the earlier comment, the token worked just fine  

@crossrulz @AQ: thanks for the workaround

[TomOrr0W]

So far I have found myself trying to modify the visible items of terminals/constants and/or clean up wires more often than using the create options (maybe if I used Quick Drop more, the priorities would be different), but I am willing to give it a couple years to see if I adjust.

This reminds me of JKI's annoying decision to put State Machine-related items at the top of right-click menus in their latest version of the State Machine Toolkit.  It annoys me, but not enough to create a JKI forum account and complain to them.

[cy...]

well... I have ancient codes (for some old hardware) to maintain on top of writing new ones, so I have no choice but to use a decade's version worth of LabVIEW. not having the option/workaround would be a setback for me, especially when switching between pre-2019 and 2019 versions.