Better tooltips for shift registers

[SteenSchmidt]

Hi.

I'll propose a more informative set of tooltips for shift registers. Especially when you drag out shift registers to access older values as well, I always have a difficult time remembering which is the most current value, and which is the oldest (is it the one on top, or is it the one at the bottom...).

Currently all shift registers have the same tooltip, namely "Shift Register". I suggest to change that into an indexed iterator variable name:

Cheers,

Steen

[fabric]

---

@SteenSchmidt wrote:

... I always have a difficult time remembering which is the most current value, and which is the oldest (is it the one on top, or is it the one at the bottom...)...

---

Seriously?!! I expected more from a man of your calibre! 

Spoiler

Anyway - I dare not vote for this in case it diverts precious resources away from the R&D team's main focus... (I believe they may be close to a working prototype!)

[SteenSchmidt]

Seriously, I didn't know I am of a certain calibre? There is stuff that I just have to try out in the IDE, when I use it rarely enough (my insecurity lies only with the up/down direction of stacked registers, not which value is in non-stacked registers ).

Anyways, I even suggest a step further to help LabVIEW beginners (and myself of course ).

I don't think not voting for ideas makes much difference for R&D when they prioritize their work. But I could be mistaken. This is probably not the most expensive idea resource-wise to implement at any rate...

/Steen

[fabric]

Well... It's just that I normally find your ideas and contributions to be very "juicy" and valuable, and yet this idea seems a little trivial! 

Of course I agree that "not voting" is ridiculous unless you have a good reason... In this case I agree that your idea may help first time users (and you! ), but IMO lots of tip strips just add visual noise. They always seem to be there when you don't want them and not there when you do!

In this case I think a far better solution would be to remove the tip strip altogether and update the context help when rolling over a shift register. If I was a new user, that is where I would look to understand a "strange" block diagram element. Currently you only get context help for the For Loop as a whole...

[SteenSchmidt]

Agreed about tip strips vs. context help. Several very good ideas float around in this idea exchange regarding beefing up the context help, so if some of that was implemented it would invalidate ideas like this one in an instant. Toggleable tip strips for select UI controls at runtime, and then context help for the IDE at edit time basically...

I don't know what happened with my memory and stacked shift registers. That info may have been written in a cluster of bad neurons or something . I can't disagree that it seems rather trivial compared to so much else we're dealing with on a day to day basis.

Cheers,

Steen

[crossrulz]

I like this idea simply because sometimes I'm too lazy to count.

[X.]

I have only one word to amend this idea: label.