topic Re: Silver Controls in BreakPoint

Silver Controls

SteveChandler — Wed, 20 Jun 2012 16:48:47 GMT

I have to ask, why is there a silver error cluster? Do people really put them on user interfaces?

Re: Silver Controls

Ben — Wed, 20 Jun 2012 19:43:05 GMT

For the absolute minimum cost projects that have absolutely no frills, yes I will show a hidden Error Cluster if an error is detected.

An unbundle by name boolean to Visable property node is my "poor man's" event handling.

If feel it a notch better than ingoring the error and having the operator try to decide if the stop or continue.

Ben

Re: Silver Controls

PaulG. — Wed, 20 Jun 2012 20:18:07 GMT

Why *NOT* make a silver error cluster? Just because "no one" sees them? Speak for yourself.If I worked with FPs all day (as I usually do) and all the controls *except* the error clusters were in one style that would drive me absolutely insane. A trait I got from my cats. ("It's different! It's different! It's BAD! NO LIKE!!")

Re: Silver Controls

P@Anand — Thu, 21 Jun 2012 03:41:06 GMT

@PaulG. wrote:

Why *NOT* make a silver error cluster? Just because "no one" sees them? Speak for yourself.If I worked with FPs all day (as I usually do) and all the controls *except* the error clusters were in one style that would drive me absolutely insane. A trait I got from my cats. ("It's different! It's different! It's BAD! NO LIKE!!")

I Agree with PaulG. It will look unconfortable when you design everything in one style and one in different style even if we are not going to present that to the End user. Error cluster will be an Odd man out 🙂

Re: Silver Controls

SteveChandler — Thu, 21 Jun 2012 13:00:53 GMT

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.

Re: Silver Controls

PaulG. — Thu, 21 Jun 2012 14:27:39 GMT

@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.

Re: Silver Controls

crossrulz — Thu, 21 Jun 2012 15:21:10 GMT

@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 use the "Modern" controls for my subVIs. Any new programs I've done recently use the Silver for GUI. For some reason, I just don't like the Silver in my subVIs. I think they are just too busy for subVIs.

Re: Silver Controls

SteveChandler — Thu, 21 Jun 2012 15:43:27 GMT

That's what I meant - modern not classic.

Re: Silver Controls

crossrulz — Thu, 21 Jun 2012 22:07:04 GMT

@Steve Chandler wrote:

That's what I meant - modern not classic.

You could say that modern is the new classic

Re: Silver Controls

Rodéric — Fri, 22 Jun 2012 14:11:49 GMT

I guess some people use them... The noobs... or people who don't care that much about use interface (let's say for an internal tester)

Re: Silver Controls

GregFreeman — Sat, 23 Jun 2012 14:31:51 GMT

@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.

Re: Silver Controls

JÞB — Sat, 23 Jun 2012 19:40:08 GMT

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:

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
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.