Hide close button of the front panel windows

[P@Anand]

When I was developing an option I thought it would be good if we have an option of hiding the close button instead of simply hiding. Since even when we hide the close button the tip strip is still available. I am proposing this idea after searching the forum.

Option for hiding the Close, Minimize and Maximize buttons.

Once this option is enabled the other option releated to the windows will get disabled.

So the window finally looks like this.

It would be good if it gets appreciated.

[parthabe]

I'm wondering why this idea has not got enough support  from the LV community?!

In my experience, LV is the only language that still shows the Window Close button (X) in a disabled state, even after we deselect that option in the VI Properties. So, this makes the UIs ugly. Getting this rid off totally would avoid situations where we cannot convince the customer that asks "If you are not going to allow me close the UI, then why do you give that button in first place?"

Going by the same argument, then the Resize & Minimize buttons also should only be disabled, and not made invisible.

[crossrulz]

My argument is that we should not even be able to disable the Close.  What program out there forces you to close the window with a Stop button?  I don't know of any.  They all shutdown via closing the window with that X.  So our programs should use it since that is the first thing our users go for when trying to shut down the program.

Ok, my argument might not quite fit with industrial situations.  But those (that I have seen) do not even have a title bar on the window (which will remove the X).

[parthabe]

"What program out there forces you to close the window with a Stop button?  I don't know of any.  They all shutdown via closing the window with that X."

Then there wont be any need for the Panel Close? filter event! 

[crossrulz]

Which is the proper way to shut down your main GUIs.

[X.]

Don't touch the X, or else.

[parthabe]

The Windows Close (X) must be made invisible when we deselect the option "Allow user to close window", like the other two options beneath it. Today, this is a bug in LV.

Why would someone deselect this option but still get to see it in disabled state, and not invisiblle?! 

[X.]

disabling-or-hiding-the-minimize-maximize-or-close-button-of-a-window

[AristosQueue (NI)]

> Why would someone deselect this option but still get to see it in disabled state, and not invisiblle?

It's presence is part of the visual chrome that helps users identify the edges of windows when working with many windows open, so even if you disable it, you often aid your users more by leaving it visible.

I asked our UX team. They tell me that:

The Microsoft recommendations for visual design say:

Regarding hiding:
All primary and secondary windows with a standard window frame should have a close button on the title bar. Clicking Close has the effect of the Cancel or Close button in the window.

Where hiding the close button is appropriate is when you are hiding the entire window frame/chrome. Guidelines give the example of immersive application, games, and kiosks. There is a separate section of the guidelines covering when to disable the [x]. It's pretty limited.

[parthabe]

> It's presence is part of the visual chrome that helps users identify the edges of windows when working with many windows open,

I dont agree to this point! The users would still be able to easily identify (without any difficulty) the edges of the window they are working on easily from the example screenshot Anand had posted. I've seen many Industrial Automation IDEs & SCADA applications designed using C++/C# that do not show any of the 3 Windows standard buttons (Min, Max, Close)

Another ugly feature in LabVIEW is, when you have both Close & Minimize enabled to be visible, Maxmize button (which is in the mniddle of the three) also becomes visible in the disabled state, which again gives makes the end user question us "Why do you even show it to me, when you are not allowing me to Maximize or Restore (if maximized) the window?". Moreover, It spois the aesthetic appeal of the UI rather than adding any visual appeal to it.

Coming to the Microsoft guidelines... "a standard window frame should have a close button on the title bar." Anyway it is a "should have" and not a "must have", which means it is a recommendation, NOT compulsory.

[AristosQueue (NI)]

> I dont agree to this point! 

Do you have usability testing evidence to submit to counter Microsoft's researched findings? The MS usability guidelines are generally well checked by actual user observation, not just finger-in-the-wind ideas.