LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why is LabVIEW 2015 Silver Error Out cluster bigger than Error In cluster?

Default sizes

 

Error.PNG

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 1 of 7
(3,108 Views)

Feedback from developers probably showed that we care more about the source of the output error when we're looking at the FP of a subVI.

 

I know that if I see an error come in to a subVI, I only care about the subVI it came from and go over there. When I see an error coming out of a subVI, I look at the source more closely to see where I need to go on the block diagram to probe/breakpoint/etc.

Cheers


--------,       Unofficial Forum Rules and Guidelines                                           ,--------

          '---   >The shortest distance between two nodes is a straight wire>   ---'


0 Kudos
Message 2 of 7
(3,104 Views)

Maybe... But it sure makes for a sloppy looking sub-vi

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 3 of 7
(3,093 Views)

Your controls have different font structure... are you sure they are both the default controls from the palette?

 

Edit: Hooovahh's response below also points to you having created the cluster on the right from somewhere else.

Cheers


--------,       Unofficial Forum Rules and Guidelines                                           ,--------

          '---   >The shortest distance between two nodes is a straight wire>   ---'


0 Kudos
Message 4 of 7
(3,078 Views)

@RTSLVU wrote:

Maybe... But it sure makes for a sloppy looking sub-vi


Yeah so does using the silver error cluster.  Smiley Tongue

 

<rant>

 

So I can't stand when the silver error cluster is used.  Silver controls in general take up more space on the FP than they should with lots of bubbly modern looking decorations.  This is fine if you have something the user sees.  I mean if they want to see bubbly UI's then that's what I make them.  But I see zero purpose in using those controls at all, in code that isn't seen by the user.  Heck I see little reason to even have a front panel for subVIs that are API calls, but that's a different discussions.

 

I also noticed the change in terminal names (Error In, Error Out), and while I agree with the standard, the default on a fresh install of LabVIEW is modern style controls, which use the "error in (no error)" and "error out", so to be consistent this is what I use.

 

If you agree with this type of thinking you may enjoy this tool which will modernize controls in a VI.

 

</rant>

 

...that being said I just dropped Error In and Error Out from the silver palette on my 2015 and they are the same size.  Larger than the modern, but In and Out are the same size.

0 Kudos
Message 5 of 7
(3,077 Views)

@Hooovahh wrote:

...that being said I just dropped Error In and Error Out from the silver palette on my 2015 and they are the same size.  Larger than the modern, but In and Out are the same size.


 

Oh you are right, that just makes it worse because if I right click on a sub-vi error out terminal and select create indicator the error out cluster is larger than the error in created the same way.

 

But dropping them from the pallet they are the same size.

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 6 of 7
(3,060 Views)

RTSLVU wrote:

 

Oh you are right, that just makes it worse because if I right click on a sub-vi error out terminal and select create indicator the error out cluster is larger than the error in created the same way.


I just tried this and I don't get this behavior.  In 2015 I made a new blank VI, then changed the VI Properties >> Editor Options >> Silver Style.  Then dropped a Close File primative, right click create control, right click create indicator, and the two silver controls are the same size.

0 Kudos
Message 7 of 7
(3,038 Views)