• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cancel Sleep
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cancel Sleep


  • Subject: Re: Cancel Sleep
  • From: Matt Burnett <email@hidden>
  • Date: Thu, 31 Jan 2008 15:51:24 -0600

RE a):
OS X behaves like this for shutdown, why not sleep? OS shutdowns are delayed or canceled all the time by user applications. What if I have a unsaved document open in TextEdit and choose shutdown, if i take no further action the shutdown will be canceled because i never interacted with the save dialog in TextEdit. If i click the cancel button in the save dialog, the shutdown is canceled too.


As i said previously, it would be obvious to the user. The sleep LED wouldn't pulse, user opens laptop and sees a dialog similar to canceled shutdown dialog.

RE b):
What do you mean by "Making the system work "well enough" in this context is much harder..."? The system was working fine before the lid is closed, with a external monitor the system still works fine with the screen closed. I dont see any reason why the system cant continue to run with the main screen disabled, i've ran other macs headless. I dont see why the system couldnt operate just fine being carried around under my arm. Could you please give a example.


RE c):
I told my system to shutdown, TextEdit canceled the shutdown. Why should sleep be different?


On Jan 31, 2008, at 2:28 PM, Michael Smith wrote:
You don't appear to get it.

Yes, in *some* situations the system could defy the user's explicit instruction to go to sleep and go on with whatever it was doing.

However:

a) This behaviour won't be consistent, and it won't be obvious to the average user why it's not consistent.

b) Making the system work "well enough" in this context is much harder than you can possibly imagine. You can't think of "the system" as a monolithic entity; there are dozens of components who each have dependencies, and you'd have to have some way of matching the possibly degraded state of the system to the components depended on for the current set of operations and asserting that they were going to remain operational...

c) The user has told the system to sleep.  It should sleep.

= Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Cancel Sleep
      • From: Marc Epard <email@hidden>
  • Prev by Date: Re: Cancel Sleep
  • Next by Date: Re: Cancel Sleep
  • Previous by thread: Re: Cancel Sleep
  • Next by thread: Re: Cancel Sleep
  • Index(es):
    • Date
    • Thread