From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Re-opening because LabVIEW NXG has been discontinued.
The smaller footprint of the Local Variables in 2010 has increased usability of the IDE and readability of the LabVIEW language. Another node that could benefit from a smaller footprint is the User Event Ref Constant.
Below is some conceptual artwork on what a smaller footprint might look like. Feel free to post more concepts!
Don't forget Queues and Notifiers too. I'm sure there are more, but those are these three I use most.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions Unofficial Forum Rules and Guidelines "Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Jack fell a step short I think in his illustration. With constants that small they could be stacked vertically, thus saving real estate both horizontally and vertically.
I initially stacked them vertically in the mock-up, but there is a 1px overlap between the edges (just like Control References and Local Variables). For the sake of the illustration, I did not want obscure any part of the ref constant so it could be subjected to a more complete visual scrutiny.
Hence, the horizontal staggering.
But yeah, if it's implemented, I too would stack them vertically.
@crossrulz wrote: Don't forget Queues and Notifiers too.
Of course, this is was an oversight on my behalf to forget Queues and Notifiers. I was fixated on the User Event constants since I use them to "turn on" and "turn off" dynamic event registrations, while Queues and Notifiers don't share a related purpose for dropping NULL refs (not yet, anyway).
So, psuedo_kudos for picking up slack in the Idea.
It's great that NI implements many of the ideas that have been suggested here, but I think it would be even better if they generated some general guidelines based on those ideas and applied them to the whole GUI of LabVIEW. That way we might have seen things like this idea implemented in LV2010 as well - not just the ones that were already suggested.
Re-opening because LabVIEW NXG has been discontinued.