LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How Intuitive Are My Icons?

Can you figure out what these should do just by looking?

 

Conversion Icons 0.png

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 1 of 8
(2,017 Views)

UTF to 8, 16, or 32 bit integers, either little endian or big endian.   (How does endianism apply to an 8 bit)?

 

Convert to ASCII string,

Convert to Unicode.

 

The pink on pink is a little hard on the eyes.

 

How'd I do?

0 Kudos
Message 2 of 8
(2,008 Views)

@RavensFan wrote:

UTF to 8, 16, or 32 bit integers, either little endian or big endian.   (How does endianism apply to an 8 bit)?


That was my first thought, but UTF by itself doesn't mean much (unless UTF-8 is implied). So it could also be interpreted as some string (probably ASCII) to UTF-8, UTF-16 LE, UTF-16 BE. Based on the colour, the output type might be a variant.

 

Not too sure what UNi does. The red text makes me think it isn't a straight conversion. Perhaps it tests if the input is a valid unicode string?

 

In any case it's pretty obvious they are some unicode conversion/processing functions.




Certified LabVIEW Architect
Unless otherwise stated, all code snippets and examples provided
by me are "as is", and are free to use and modify without attribution.
0 Kudos
Message 3 of 8
(1,953 Views)
  1. Yes, endianness doesn't mean anything for UTF-8 (although it is conceiveable for the multi-byte sequences). That was just a mindless blunder when I was slapping the graphics together.
  2. They are all conversions
  3. Like the built-ins, the inputs are polymorphic (mostly); the icon just shows what it converts to, not what it converts from. So "UTF - 16LE" is what it converts to.  The hyphen and my color choice created confusion there. I'm aiming for a consistent color scheme for this project. The main color being red (well, closer to cerise).  I wanted my functions to all have a matching background color, so I chose pale red. On these conversions, I wanted the text colors to indicate the output type;  but with magenta on pale red, the "BE" and "LE" were very hard to distinguish, so I made them darker.

 

Ravens Fan: You did well, in the sense that you found deficiencies in my initial icons (which is what I was looking for).

 

Here's my 2nd whack (though I'm not sure I like the white background):

Conversion Icons 2.png

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 4 of 8
(1,897 Views)

Hi Paul,

 

how do you go beyond the 32 pixel limit (height, width) of VI icons?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 5 of 8
(1,889 Views)

@GerdW wrote:

Hi Paul,

 

how do you go beyond the 32 pixel limit (height, width) of VI icons?


Those are going to be XNodes, which don't have a limit on icon size; so I don't have to try to squeeze things.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 6 of 8
(1,884 Views)

I think I will go with this style:

 

Conversion Icon 3.png

"If you weren't supposed to push it, it wouldn't be a button."
Message 7 of 8
(1,852 Views)

@paul_cardinale wrote:

I think I will go with this style:

 

Conversion Icon 3.png


Yeah that's better, the '-' immidiately bring the mind to to/from.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 8 of 8
(1,830 Views)