BreakPoint

cancel
Showing results for 
Search instead for 
Did you mean: 

Silver Controls


@PaulG. wrote:

@Steve Chandler wrote:
I guess that makes sense. I never thought of it since all my subVIs use classic controls. I have only used the silver controls on the GUI of one project.

I'm stuck on the silver controls. They are my defaults. Best cosmetic improvement LV has had in a long time.


 

I agree. There are a few cases where I still use system over silver; if I want the app to feel more congruent with other applications that may be based on visual c++, .net etc. I'm also not a huge fan of the numeric controls I feel the frame is a bit profound. But for things like graphs, charts, etc I love them.
0 Kudos
Message 11 of 12
(4,412 Views)

I use them! but, for the opportunity to diagnose the "archialogical context" that the VI was last updated in.  "Error In" and "Error Out" are much better lable formats (IMO) but, the silver Error clusters do have two distinct drawbacks:

  1. TestStand does not recognize "Error Out" as the same control as "error out" so, if you use TestStand you need to modifiy the vi lib to type def the Error Out cluster and disconnect from type def on each vi or vit.  Alternatly, for every step in TestStand you need to manually set Error Out to Step.Result.Error
  2. VI analyzer will fail the test "Cluster not sized to fit" on all Error clusters.  This is an annoyance as well.

 

Hopefully NI will fix those someday

 

I do like the silver look.


"Should be" isn't "Is" -Jay
Message 12 of 12
(4,405 Views)