Re: <no subject>
Re: <no subject>
- Subject: Re: <no subject>
- From: "Alastair J.Houghton" <email@hidden>
- Date: Tue, 5 Aug 2003 23:09:46 +0100
On Tuesday, August 5, 2003, at 08:37 pm, Alec Carlson wrote:
Llama,
... In any case, your app SHOULD
NOT INTERRUPT HER because she is not running your app, I am.
You are EXACTLY right. However, in order for my app to make that
decision,
it needs to determine that she (and not you) is currently using the
Mac and
therefore not interrupt her. That is exactly the API I'm looking for.
Without that information, you both look like the same user. If she
logs you
out and then logs herself in it's not a problem. However, if she
leaves you
logged in and fast switches to her account then I can't tell the
difference
between the 2 different users... Hence the gist of of question.
I haven't tried the Fast User Switching feature (because I don't have a
copy of Panther), but I imagine that it isn't possible for a GUI
application running on one user's desktop to affect the other desktop
at all. Which includes things like you popping-up dialog boxes, and
even making noises and the like. So the question is, why do you need
to know who it is has got the currently displayed desktop?
If both users are supposed to be running some obvious GUI application,
then you don't have a problem because the GUI application is only on
one desktop at a time... so, for example, say Fred and Jane are both
logged in, and say (for example) that you have written a chat program
involving a daemon and a GUI client (the normal model for this type of
thing). Fred and Jane are both running *their own separate copies* of
the GUI client, which identify them to the daemon. Fred sends Jane a
message using his copy of the GUI client, which passes it to the
daemon, which, in turn, passes it to Jane's GUI client. Jane's GUI
client pops a window to the front and tries to make a noise, but
because Fred has the visible desktop at the moment, he isn't
interrupted and the window is waiting for Jane when Fred has finished
and Jane returns to the computer.
How is your application different from this type of arrangement, and
why? Why do you think your application will bother the current user?
If you explain a bit more, then perhaps someone can suggest a suitable
solution to your problem.
Kind regards,
Alastair.
_______________________________________________
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.
| References: | |
| | ><no subject> (From: Alec Carlson <email@hidden>) |