Re: [MiNT] XaAES, TosWin2 closed and wrong active window

[Eero Tamminen <oak@helsinkinet.fi>]

Hi,

On tiistai 12 helmikuu 2013, Helmut Karlowski wrote:
> Vincent Rivière, 11.02.2013 22:59:06:
> > On 11/02/2013 22:53, Helmut Karlowski wrote:
> >> You need one window open if you want the app to stay focused.
> > 
> > This is annoying, but acceptable.
> 
> Actually I don't understand your problem:
> 
> 1. You want toswin to untop when it's last window is closed.
> 
> 2. You want toswin to not untop when it's last window is closed, but it
> is a dialog.
> 
> What do you want to do with the still topped toswin after you closed the
> dialog?

Although 2) is a less common case, I think it's actually a valid use-case,
regardless of a program.

One may want to set/change some options before opening a window which
contents those options concern.  Good programs allow changing those
options also while the content is already shown, but user might for
some reason want to do that before opening the window.


This is even worse with programs that show (potentially windowed) dialogs
at startup, which need to be OKed before they open any windows.  Clicking
through a startup dialog shouldn't untop the program...

I think this is important enough use-case that unless it can be solved,
1) should be discarded.


Next questions are:

* Would it be possible to identify a windowed dialog somehow already?

* If not, would be possible to device a way for GEM library to set some
  flag which tells window contents to be a dialog?


	- Eero