When wiring from inside a for loop to outside it, and the user lands the data on a singular data node (not an array or cluster), automatically set the tunnel mode to Last Value to prevent unnecessary code cleanup.
You will have to define what you mean exactly by "singular data node". I guess you mean "any input terminal which data type is not an array".
Seems like a fair idea at first, but what about:
- Functions with polymorphic inputs?
- Polymorphic VIs?
- Malleable VIs?
- Variant inputs?
- XNode inputs?
They can all support both array and non-array inputs despite having a scalar input by default. So, the auto-selection would be incapable of choosing. I think I would prefer the editor to act always the same rather than it taking false guesses.
But maybe you could give your most common use case where that would be useful?
Seems reasonable the IDE could try wiring Indexing first, and fallback to Last Value if there's a broken wire. Surely more edge cases, but that's the case with any feature. Even outright excluding the special cases (VIMs, Variants, etc.) would be an improvement to the developer experience.
