BreakPoint

cancel
Showing results for 
Search instead for 
Did you mean: 

The look of string wires.

Inspired by this idea about boolean wires, I was wondering about why strings aren't pink solid (single-pixel wide for scalars) wires. Would seem clearer to me, especially in order to more easily tell the number of array dimensions.

 

 

I think that these "checkerboard patterned" string wires go all the way back to the B&W screens of the original Macintosh and nobody bothered to adapt them to color. 😄

 

This probably should be another idea unless I get shot down right here. Maybe I should get feedback from colorblind users first... 😮 Please comment.

 

 

Message 1 of 7
(9,434 Views)

Here is your feedback from a colorblind user: Too hard to distinguish from integers, at least in isolation. Side by side or crossing they might be distinguishable.

 

When LV went color, I resisted changing for one or two revisions (or maybe until it was no longer an option) because some of the color choices were more confusing than the nicely patterened B&W wires.

 

Lynn

Message 2 of 7
(9,401 Views)

Yes, these patterns go all the way back to prehistoric B&W LabVIEW. See e.g. page 4-59 of the LabVIEW 1.2 manual.

 

(It is actually a very impressive document and shows how mature and full-featured LabVIEW already was back in 1989. Good read!)

 

 

 

Back then, color was not an option and when color got introduced the special wire patterns remained for boolean and strings. Maybe it is good to have orthogonal visual clues (pattern & color) for major wire types as we do today. The problem is that there are only very limited pattern options given the narrow width. Personally, I probably would prefer solid wires distinguished only by color as suggested above but this might impact usability with certain vision problems. What if we had an option to show/hide enhanced wire patterns?

 

( EDIT: Thanks Lynn. I only saw your comment after I wrote this post)

 

 

Message 3 of 7
(9,399 Views)

Stupid question: why didn't NI just color the wires but leave the textures alone?

PaulG.

LabVIEW versions 5.0 - 2023

“All programmers are optimists”
― Frederick P. Brooks Jr.
0 Kudos
Message 4 of 7
(9,352 Views)

@PaulG. wrote:

Stupid question: why didn't NI just color the wires but leave the textures alone?


It looks like that is what happened, except for the cluster.  Not sure why that one got changed.


GCentral
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
0 Kudos
Message 5 of 7
(9,347 Views)

@altenbach wrote:

Yes, these patterns go all the way back to prehistoric B&W LabVIEW. See e.g. page 4-59 of the LabVIEW 1.2 manual.

 

(It is actually a very impressive document and shows how mature and full-featured LabVIEW already was back in 1989. Good read!)

 

 

 

Back then, color was not an option and when color got introduced the special wire patterns remained for boolean and strings. Maybe it is good to have orthogonal visual clues (pattern & color) for major wire types as we do today. The problem is that there are only very limited pattern options given the narrow width. Personally, I probably would prefer solid wires distinguished only by color as suggested above but this might impact usability with certain vision problems. What if we had an option to show/hide enhanced wire patterns?

 

( EDIT: Thanks Lynn. I only saw your comment after I wrote this post)

 

 


Wow, all those broken wires!Smiley Surprised

Spoiler
No I never liked the red x's when they were introduced

"Should be" isn't "Is" -Jay
0 Kudos
Message 6 of 7
(9,207 Views)
So, what was the look of a broken wire? Did they exist back then?
0 Kudos
Message 7 of 7
(9,194 Views)