01-24-2018 11:17 AM - edited 01-24-2018 11:25 AM
I made an effort to force me to use autotool when it came out and never looked back. Yes, I did have a lot of muscle memory to switch tools (right hand on the mouse, left ring finger on the <tab> and left thumb on the <space>). Yes, the early iterations of autotool were a bit clunky but it has stabilized well within a few versions and has now been great for a long time.
The most annoying thing when using computers of others are the palettes. Mine are always "Icon Only/Category(Standard)/visible:all)". Since the number of columns in the default palettes is different, I always have a hard time finding anything because the row-column position of all items have changed. It's like the twilight zone! (I expect "Numeric" to be in the upper right corner, not second row on the left! 🐵
(Of course quickdrop has helped with this :))
01-24-2018 11:24 AM
@JÞB wrote:
On the other hand. Use Auto Tool and drop a free text label Oh You have to hit TAB Once not Twice to switch to the text tool. BECAUSE! at no point does the LabVIEW IDE think that commenting your code is the most appropriate thing to do!
@@!#!@#%@#^@$
I just double-click on my block diagram and start typing.
01-24-2018 11:31 AM
@crossrulz wrote:
I just double-click on my block diagram and start typing.
Yes, the only place I need the tool palette (SHIFT-RIGHT-CLICK) is when filling e.g. an enum. You won't ever get the text tool by just clicking on it 😄
On the front panel, there is this longstanding issue that you cannot double-click inside a tab to get a free label.
01-24-2018 11:34 AM
altenbach wrote:Yes, the only place I need the tool palette (SHIFT-RIGHT-CLICK) is when filling e.g. an enum. You won't ever get the text tool by just clicking on it 😄
You should be able to Ctrl+Click an enum to start editing the values in it.
I do use the tools palette for probing though. I find that typically I want to drop more than one probe and it's easier to just click everywhere with the probe tool instead of right-clicking each wire.
01-24-2018 11:45 AM
@Jacobson-ni wrote:
You should be able to Ctrl+Click an enum to start editing the values in it.
Yes, forgot about that. My enums are typically typedefs and I normally use right-click..edit items... anyway 😄
01-24-2018 12:21 PM
Oh great another auto-tool discussion...
For enums I do Shift+Enter to add after if I am setting it up for the first time. Then I'll use the Edit menu if I am making changes other than adding new items after.
I prefer auto-tool off but can change. One thing I really like is not having to be pixel perfect, or not having to select an object first (or deselect it) for the tool to be what I want. If my mouse is on the left and it is the pointer tool, I can move my mouse with my right hand, and change to the wiring tool by tabbing with my left. By the time my mouse is where it needs to be the tool I want is already selected. And now when I am wiring to something like a terminal, I don't need to be as accurate on the exact location of my click because the tool won't change to something else if I'm not at the right spot. This gets even more important with high DPI mice, and high resolution monitors.
Another fun thing is you can CTRL double click a subVI to open the block diagram. This works even when a VI is running, but only if auto-tool is off.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
01-24-2018 01:51 PM
I haven't had one of my comments get this much traction in a while! I'm just glad that I can choose between the two modes, that some NI person didn't make the command decision that auto-tool was the only way to go!
01-24-2018 01:53 PM
Hooovahh wrote:
Another fun thing is you can CTRL double click a subVI to open the block diagram. This works even when a VI is running, but only if auto-tool is off.
Just to clarify:
The Ctrl double-click works in edit mode either way. But with auto-tool on in run mode, CTRL puts the tool into Breakpoint mode. Thus the Ctrl double-click in run mode only works with the auto-tool turned off.
01-24-2018 01:55 PM
@LV_Pro wrote:
I haven't had one of my comments get this much traction in a while! I'm just glad that I can choose between the two modes, that some NI person didn't make the command decision that auto-tool was the only way to go!
*cough*NXG*cough*
01-24-2018 02:26 PM
@crossrulz wrote:
*cough*NXG*cough*
SpoilerUnless they changed their minds on that without me knowing
Every time I've brought it up, the response has been something to the effect of, NI will allow for auto-tool to be turned off in NXG if there is a large enough user base asking for it. Which is usually followed up with me, being told there is likely never going to be that large of a user base asking for it.
I will change...if I have to...I guess.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord