Here are 4 different application windows with different actions for closing the windows. Sometimes it says ‘Close’, sometimes ‘OK’. All times there is a native OS close option.
Personally, I think less is more, and you can just get rid of them all together and just let the user use the native OS windowing [X] to close them. Reduce decision fatigue with fewer options to consider and a cleaner UI.
The presence of the window close button [X] depends on the underlying window manager. There is no guarantee that every window manager supports it. Also it is an extra burden to test the GUI compatibility with a large set of window managers.
On Android there is no window frame at all.
So, currently, I lean to NACK.
NACK, not all systems will have a WM that provides a native close button. Other systems can be configured not to have the native close button (i3, dwm, etc …). If we removed the ok/cancel buttons, those with the aforementioned systems would not have a way to close a window, except for a keyboard close window shortcut.
As for the point that sometimes there’s an Ok button and other times, there’s a Close button: This seems ok depending on the context the window is opened with. The receiving addresses and sending addresses windows are opened in the context of ‘performing an action’, so it makes sense that the exit button says close. The Command-line Options window is opened in the context of retrieving information, so, to me, it’s fine that the exit button says Ok. As in, Ok, I’ve found what I needed to find.
Labels
Design