Not showing the close box may be a historic artifact from trying to match the behavior on exising X window managers at that time.
A quick test here shows that metacity, at least, is showing the X for modal windows. So I see no problem with turning on the close box for all windows on Win32. Especially if that is how most applications are working there. On 05/20/2011 04:27 AM, Nikita Egorov wrote: >> It's not as clear cut as that - you need to make it explicit to the user >> what state will be returned, and in many cases the dialog will be >> offering a choice where it is not obvious which is the default; so what >> value do you get for "cancel"? >> >> Now, as programmers, the "right" answer may be obvious to us, but >> experience tells us that for the end-users there will inevitably be >> cases where our "obviously right" choice is not the expected value... > > Yes, I agree with you but all your explanations are destroyed by > existence of Esc key-- > >> So, better to make it so that there is an explicit button, then the user >> has to pick a value... > > Yes, it's right way but there is one more moment - I can't remember > any title bar (in native Win32 program) which hasn't the close button. > In some cases when behaviour is ambiguously (Yes/No dialog) the button > is deactivated and Esc doesn't work too. But windows have the same > appearance always. > >> You should probably file that as an RFE, and we can look at it as an >> option - though we'll need to support it across all platforms so a win32 >> only patch is unlikely to be acceptable. If you have "equivalent" >> patches for OSX and X11 that'll be better (though I doubt X11 is >> consistent in this anyway, given the differences between the different >> WM's in use...) > > I see difficulties in implementation of the feature and I'll remain > for a while with adding the WS_SYSMENU in my programs when I need it. > _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
