View Cluster Constant as Icon

[chris.b]

Clusters are powerful and necessary, but they can easily clutter up otherwise immaculate code.  Why not have a "View As Icon" option (a la Express VIs) for cluster constants?

Right-click menu change...

There have been similar suggestions, but I think we need a clean, simple solution.

[JackDunaway]

Don't get me wrong - I'm thrilled that this idea has passed and is In Beta with the small icon! Light-years ahead of the cluster-saurus-constants attacking our BD's.

Being able to put the typedef's icon to use would just be a natural extension for our group since we are fairly disciplined at creating custom, meaningful icons.

[Wonger]

I still need to decide out how we can differentiate an iconified typedef cluster from an FPTerminal of that same typedef... otherwise you wouldn't be able to tell if it was a constant or a control. Any more suggestions on that issue?

[Wonger]

Right now, for the typedef'd cluster control we are adding a little cluster icon to the bottom of the typedef's icon. For constants I could change that icon up a bit (similar to how the generic cluster icon shown above looks) and add that to the typedef's icon... I'm not sure if the difference is too subtle though.

[chris.b]

Many power users (the same one's with huge clusters) turn off "Place front panel terminals as icons" (with the same reasoning as this idea: free up diagram space).

For these users, the typedef icon for constants would not be confusing at all.  Maybe this swings the balance a little...

Just a thought 🙂

[Wonger]

That's a good point, but even if most power users wouldn't notice it, I still do need to differentiate between the two in some way. I'm working on a prototype right now, I'll post up images when it's done and you guys can tell me what you think.

[Wonger]

Here's what my prototype looks like.  I ended up making the outer rect a little less thick to differentiate from the Control FPTerm, and also changed the glyph at the bottom a bit (you can still disable this bottom glyph the same as with the FPTerm). The space between the inner and outer rects is a bit smaller than the indicator, the same as with the regular cluster constant.

Thoughts? 

Message Edited by Wonger on 02-25-2010 03:39 PM

[JackDunaway]

Wonger, brilliant job. So, if I start with my icon (1) and add your border (2), I would get (3)? I really like this.

Consider the smaller icon (4) with the transparent top/bottom. Would I get (5) or (6)?

One more comment: I notice the Typedef Iconified indicates the arrow output direction, but the Non-typedef Iconified does not show the output arrow. What if you took the output indicator off of the Typedef Iconified to match no arrow on the non-typedef, and to give greater difference between the constant and the Control/Indicator?

***EDIT: chris.b, good point. Removing the output arrow on the the cluster constant is even one more step toward differentiating***

Message Edited by JackDunaway on 02-25-2010 04:08 PM

[Wonger]

Modified it a bit, added rect around the type glyph.

Removing the arrow is a good idea, I had also been considering it. Not sure about the rectangular icon, I will check and get back to you on that.

Message Edited by Wonger on 02-25-2010 04:20 PM

[Wonger]

The rect is formed based on the image size, and since the image is still the regular icon size I believe you would get 6. I don't think we really have a good way to check for transparency and reduce your image size based on transparent space. I don't think FPTerms or Indicators currently do this (please correct me if I'm wrong, I haven't messed with the icon editor that much) and it would work in the same way.

Technically you would not have the black border that surrounds your icon either, that is overwritten by the type color border just like the FPTerm and Indicator currently do.  I can change this however if you would like to retain the outer border of your icon.

[JackDunaway]

I like th rect around the type glyph - it cleans up the disarray of the "cluster elements." Here are the updates with the bound around the elements, and no arrows:

Having the bounds squeeze in as the icon becomes smaller is a perk. Necessary? No, but I think it looks nicer. If it's going to be ridiculous to implement, I can certainly live without it, but if it's virtually a freebie in your implementation, go for it!