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


Click here to return to the '10.5: Be aware of a Software Update Command-Q issue' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: Be aware of a Software Update Command-Q issue
Authored by: rbsandkam on Mar 25, '08 01:12:43PM

I agree with the comments that this is not a bug.
When an ARD/screen sharing window is the main focus, the keyboard commands should go to that remote computer.

Having said that, I would simply ask for consistency.
Because if I command-shift-Q, then it does *not* invoke the log out command for the remote computer, it invokes it for your computer (at least it does with ARD).
If you are too quick to hit enter, then you will quickly find all of *your* applications quitting, including your ARD/screen sharing session.

So, why does command-Q go to the remote computer, while command-shift-Q does not?



[ Reply to This | # ]
10.5: Be aware of a Software Update Command-Q issue
Authored by: mm2270 on Mar 25, '08 02:53:57PM
I agree with you here, and have found myself in situations where I have accidentally logged out of my own account when trying to log out a remote systems account using ARD. But that isn't the issue here. Something like Software Update should never respond to the Command-Q action when it's in the middle of actually installing the update.

Take a look at good installers, and what you'll see is that buttons like "Cancel" become grayed out at a certain point in the install process, because the developer was smart enough to know that is the user hit cancel at that point, they would be left with incomplete software. Why should Software Update act any differently in this case?

For him, it was only Safari. What if it had been 10.5.3 that was interrupted in the middle of the install? You're saying OS X should just allow that to happen???

[ Reply to This | # ]