Re: Re: Disabling Exposé for some windows, some da y =3 F
Re: Re: Disabling Exposé for some windows, some da y =3 F
- Subject: Re: Re: Disabling Exposé for some windows, some da y =3 F
- From: "M. Uli Kusterer" <email@hidden>
- Date: Mon, 26 Jan 2004 18:02:35 +0100
At 9:25 Uhr -0600 26.01.2004, Glen Simmons wrote:
Personally, I don't think Apple should provide the API you are
requesting, and I hope a "hack or something to provide this
'feature' " can't be found. I would bet there would be quite a few
developers that would feel that their app is special and their
windows shouldn't be affected. Suddenly, Exposi isn't very useful
anymore because only half the windows move out of the way
Glen,
I agree with most of this part. I wouldn't really want it to be too
easy to get your window excluded from Expose. It could be limited to
windows in a particular layer (e.g. between the desktop icons and
desktop layer, and in some system-wide layer as well), for example.
I really don't see why it's a problem for your "preference pane to
display log files or pictures on the desktop" to be affected by
Exposi. I mean, Exposi is a temporary state, it's not intended to be
used continuously.
Here is where I disagree. Imagine you're implementing an application
(like he does) that shows animations on the desktop, or even useful
info. It should be possible to keep this window from being Expose-ed.
Same goes for disability applications. Imagine you're someone using
an on-screen keyboard. You accidentally hit F-something and suddenly
your keyboard is gone, and you can't get back without help from a
not-disabled person.
Similarly, I once worked on hacking together a simple Finder
replacement of my own. Every time I used Expose, my desktop would
slide out. There are definitely legitimate uses for windows that
aren't touched by Expose. But it shouldn't be too easy. It would have
to be at least as complicated as adding your own login items is
today, i.e. you write to Apple, they send you back a huge chunk of
source code and you have to add that to your app. Simply being able
to set a window attribute for doing that is inviting abuse.
Though I do believe that most of the users would probably much
rather throw away an app that refuses to Expose itself.
Or, if Apple really feels like inhibiting abuse, they could make it
an option that has to be explicitly turned on for each application,
just like Accessibility is. They could even bring up a dialog saying:
"This app wants to cripple your use of Expose. Do you really want
that?".
But there *has to be* some way of doing it.
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.