LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
Intaris

Diagram Constant Representation visualisation

Status: New

Inspired by Altenbach's Boolean constant design, I thought of the following....

 

When we have a SGL or a DBL constant on the block diagram, we have to right click, selece "representation" to find out exactly what type it is.  Why not have some indication as to the actual data type which could conveniently act as a menu for changing the data type.

 

BD Constant Data Type.PNG

 

The same thing goes for U8, I8, U16, I16 and so on.

 

Shane.

9 Comments
altenbach
Knight of NI

> When we have a SGL or a DBL constant on the block diagram, we have to right click, selece "representation" to find out exactly what type it is.

 

All you need to do is ctrl+h (context help) and hover over the constant. It'll tell you the representation (same for hovering over a wire). Still, I agree there should be some direct graphical cues, simply to be able to fully reproduce a VI from an image or printed representation. (This goes along the same lines as this idea)

J.Mamakos
Active Participant
@mechelecengr, perhaps a solid line to symbolise 8 bytes rather than a second row of four dots? Also, can you not have 'S' or 'U' instead of the 'X' to represent signed and unsigned?


Never say "Oops." Always say "Ah, interesting!"

jdeguire
Member

What about rather than showing dots for different data type sizes, the shade of color would change?  So maybe a U8 would be a light blue and a U64 would be a dark blue.  A float would be a slightly lighter orange, a double would be be the current shade of orange, and an extended float would be darker orange.  The advantage is that wires would follow this scheme as well, so it would be easier to trace wires of a certain type through the BD.

 

This still does not account for signed vs. unsigned, but maybe they should not be the same color anyway.  Maybe one could be purple or red or something.

RavensFan
Knight of NI
The different shades of orange and blue sound like a good idea.  The only problem is when you deal with wires, they are only a pixel or two thick, and it is kind of hard to discern different colors from such a narrow pixel area.  When you start factoring in thicker wires for 1-D arrays, and larger and larger spaced wires for 2-D, 3-D and larger arrays, discerning different colors of orange or blue would become even more impossible.
Matthew_Kelton
Active Participant
Don't forget that some of us are color blind and differing shades means nothing.  I already have enough trouble with wire colors (reals and booleans are probably the two biggest for me), so doing different shades will do me (and many others) no good.
cyro
Member

Maybe it helps when you customize your constants:

 

NumericConstants.png

X.
Trusted Enthusiast
Trusted Enthusiast

Neat, cyro. What is the trick?

tst
Knight of NI Knight of NI
Knight of NI

> Neat, cyro. What is the trick?

 

 

Right click the constant and select Display Format...

Then switch to the advanced editing mode and use whichever format string you wish.


___________________
Try to take over the world!
X.
Trusted Enthusiast
Trusted Enthusiast

Thanks. Now I see the limitations. I was hoping that could be a similar approach to this.