Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.7: Make Lion honor the com.apple.ScreenSharing DoNotSendSystemKeys default' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.7: Make Lion honor the com.apple.ScreenSharing DoNotSendSystemKeys default
Authored by: NovaScotian on Feb 23, '12 08:25:12AM

I've found that this behavior depends on where the cursor is. If in the shared screen, the command goes through to the server, if outside, it applies to the local Mac client.



[ Reply to This | # ]
10.7: Make Lion honor the com.apple.ScreenSharing DoNotSendSystemKeys default
Authored by: msadesign on Feb 24, '12 05:21:21AM

and isn't this how one expects the thing to work?



[ Reply to This | # ]
10.7: Make Lion honor the com.apple.ScreenSharing DoNotSendSystemKeys default
Authored by: NovaScotian on Feb 24, '12 07:00:28AM

Exactly.



[ Reply to This | # ]
10.7: Make Lion honor the com.apple.ScreenSharing DoNotSendSystemKeys default
Authored by: dilvish1984 on Feb 25, '12 09:07:21AM

Do you mean to say that it depends on whether Screen Sharing is the active (frontmost) app on your local machine? I can't imagine that they would set it up to respond to which window the mouse pointer is over (and indeed that isn't how it works on my machine) since there are actually two mouse pointers whenever you move it outside the screen sharing window (one local and one remote) and that would become terribly confusing (and therefore un-Apple-like).

As for the original hint, I have to say this seems like a bad idea to me, and a bit extreme just to get around a minor annoyance. Setting the defaults value was fairly safe, since some programmer had to anticipate its existence, or it wouldn't be coded into the app in the first place. Randomly killing a spawned process that the app may be relying on for more than you think is not something that a programmer should be expected to anticipate or accommodate. At the very least, this hint should have a very prominent "Use at your own risk" warning...



[ Reply to This | # ]