Almost created this very Idea, but glad I didn't because you did a better job describing in one picture than all the paragraphs brewing my head! Kudos to this "old gem" that hopefully more will discover.
You
can also read this
post for my explanation of why this isn't a native part of LabVIEW
already. I'm not opposed to it being added... there's just history for
why it didn't get created originally.
I read through the conversation on lavag - too bad about your usability testing. Whoever says "it's too confusing since the palette would be dynamically rearranged (alphabetized)", I don't buy into that. Did you try the dynamic palette building based on the order it appears under the class? If the user wants the list alphabetized, such will be the palette. If the user wants the newest items at the end, such will be the palette.
Not including this feature simply because the palette may get rearranged as items are added/removed from the class? This is a significant loss over a minor detail. I really like the palletes view vs. simply a text listing (I appreciate an easily-recognizable icon). Having palettes built dynamically based on class contents would be an excellent UI addition.
Several users on lavag mentioned "Why not run the proposal by us (the community) for usability testing?" Would it be worth revisiting your proposals in the context of the Idea Exchange?
The real problem here is that such a natural, intuitive feature is missing. I commonly right-click on different sorts of wires to access the appropriate palette, and I continually make the mistake of right-clicking on class wires expecting to pull up the class library palette.
Message Edited by JackDunaway on 05-03-2010 11:32 AM
