[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] wind_set(WF_TOPMOST) extension



søn, 16,.04.2006 kl. 14.33 +0200, skrev olivier.landemarre@utbm.fr:
> Quoting "olivier.landemarre@utbm.fr" <Olivier.Landemarre@utbm.fr>:
> 
> > Hello
> >
> > I just commint an extension to previous documentation
> >
> > wind_set(handle,WF_TOPMOST, parm1,...)
> > parm1:
> >         2 : for put window in topmost state (alway's over other classical
> > windows) but link to the focus of application, if application lost focus,
> > window
> > is close, when focus is restore window is open by aes. This is classical
> > toolbox
> > on other systems. For use just do a wind_create() then
> > wind_set(WF_TOPMOST,2,...), not do any wind_open() or wind_close() at the end
> > just do your wind_delete(), all is automatic.
> 
> Not do an wind_open() is not very GEM like, I try to correct this
> 
> Olivier
> 
> >
> > Now it need to know how this system call exist, actually I not like a lot to
> > add
> > this to appl_getinfo(), because this is not enough generic, I think we should
> > add a call in wind_set() or wind_get(), to know if a mode exist like
> >
> > wind_set(-2,WF_TOPMOST) return 1 if exist, 0 if not for example.

 What do you mean it is not generic? Why do you want to break the
standard way of using appl_getinfo() to get information about AES
capabilities?


 Best Regards,
Odd Skancke