[openbeos] Re: inconsistency?

"Jonas Sundström" <jonas@xxxxxxxxxxx> wrote:
> Axel Dörfler wrote:
> > "Kevin Field" <kev@xxxxxxxxxxxxx> wrote:
> >>Maybe we should borrow something from 
> >>the Screen Saver kit?  If we had that don't-
> >>interfere flag, every app would have to 
> >>implement a system just like the functionality
> >>of a screen saver timeout.  It wouldn't 
> >>have the same time setting or criteria
> >>for (de)activation, but this way the behaviour
> >>would be standardized across all apps.
> > That kind of functionality should sit in the app_server,
> >  and be handled completely autonomously.
> There's always some mouse or keyboard activity
> right before, say, Tracker opens a file or application,
> or an application wants to open an URL in, eg, Net+,
> so any external "..." (so to speak) would always open 
> up behind. Probably a much greater annoyance
> and source of confusion. 
> 
> But, perhaps, an app_server -side  time-out -based
> heuristic (?) that works only for BTextViews. Whenever
> one is typing (or is within the timeout of typing).
> 
> On the other hand, in BeShare /priv user would open
> up the new window behind. Or, if you'd limit it to
> only windows from other applications, it would still 
> be annoying in some other case, like when running 
> a GUI application from Terminal.
> 
> Perhaps a cocktail of widget-aware heuristics, 
> and some API for finetuning these for each app.
> Don't know really. At the very least, it would be 
> nice not being interrupted while in a dropdown
> or other menu.

I would limit it to keyboard activity, and "return" and other 
functional keys would be ignored (ie. would mark an end of an input 
stream). Add a short timeout to that and you'd had what I initially 
meant to propose.
I would really like to see that implemented.

Bye,
   Axel.

Other related posts: