Customizable names for Count terminal (aka N) and Iteration terminal(aka i) in Loops

[X.]

Need I say more?

I do a lot of math formula transposition from my written notes to LabVIEW where matrices or vectors are involved.

I usually try to use different index names for different dimensions and most of the time, the size of vectors or matrices are different, so having three nested loops with all sizes called "N" and all indices called "i" doesn't help with legibility.

It would be fine (somewhat) if one could add labels to the count and iteration terminals, but we can't. And labels on wires are not as visible.

And since a picture is worth 1,000 words:

[Wart]

At a minimum I'd like to see the i terminal iterate automatically for nested for loops (i,j,k,...).

[fabric]

First, I like the idea in principle.... that's why I voted for it 🙂

However, I think having fully customisable names is probably unnecessary and could potentially be confusing. 

I quite like Wart's idea, but what would be really useful IMO is to update the iteration terminal name when auto-indexing a multi-dimensional array:

[Intaris]

Personally I like the freely configurable names.  Also worth considering is whether the name should be limited to a single letter or not.....

[X.]

In my use cases, I try to mirror my notes, and I could very well have used N_p for the number of elements and i' for the index, so I really meant FULL customizability (more than one symbol).

[mawodorfer]

This makes the code for other users not very readable if everybody uses different variable names for (N and i), don't you think?

[X.]

I am not asking for Chinese or Arabic character support, mind you...

[Intaris]

Well then how about allowing the formatting to only be displayed AFTER the "i" like

i\s(%Custom Formatting%)

OTOH, I think it's fairly clear that a square blue terminal is the iteration counter.  There are no other square blue terminals on the BD.

Shane.

[Manzolli]

Wire "Descriptions and Tip..." and "Label" are good enough for me. They work in all terminals like: Shift Registers, Feedback Nodes, Sequence Locals, etc.

[X.]

shift registers and loop terminals DON'T HAVE labels or Description and Tip. Besides, description and tip is only active when you hover over the object or have the help window open. Totally different.

I like wire labels, but you cannot move them ON TOP of the terminals, so you have two conflicting visual cues...

[Manzolli]

“shift registers and loop terminals DON'T HAVE labels or Description and Tip” The wire that comes out has.

“description and tip is only active when you hover over the object or have the help window open” Wires have labels, visible all the time.

The terminal and the wire that comes out of it have the same data.

I'm not saying your idea is bad, but for me is not necessary.