On 9-Oct-05, at 17:40 , Shaun Wexler wrote:
In mission-critical operations such as performing Show Control at a live event, an accidentally-closed laptop lid could potentially halt an entire performance, and more importantly, it might even harm people's lives, ie when triggering pyrotechnics, machine control, animatronics, etc. Sometimes, kernel hacks are justified... ;)
This is where I will repeat that what ever assumptions you make, should be done in such a way that the user can over-ride the settings. Maybe what you can do is do your assumption based tests on first launch, and then present the user with a dialogue allowing them to fine-tune these settings. From what I can see, the following tests could be used, you can find the necessary API access: - presence of battery - computer name - presence of clamshell test - I notice that if you look in the system profiler under "Power" the is actually a entry indicating whether the clamshell is open or closed.
The danger of operating with the lid closed is that of a fried screen or some other aspect of the computer being fried. For the most part PowerBooks and iBooks just aren't designed to work with a closed lid. If you do find a solution to keep the computer running with the lid closed, then I would recommend adding some audible signal (voice or beep), to force the user to open the computer and possible even provide them with a warning dialog so they are aware of what happened. You don't want to be responsible for having to replace a customer's computer.
André
|