Re: [Alephmodular-devel] Kiosk mode

[Br'fin <br...@ma...>]

On Saturday, March 15, 2003, at 10:25  PM, Mark Levin wrote:

>
> On Saturday, March 15, 2003, at 03:02  PM, Br'fin wrote:
>
>> Hmm, what 'system' should be responsible for Kiosk mode?
>>
>> Kiosk mode being a mode (typically used while fullscreen is active) 
>> where the ability to switch processes is disabled. For instance, on 
>> MacOS X 10.2 this would entail disabling Cmd-Tab to switch process 
>> and Cmd-` to switch windows.
>>
>> On one hand it's only kicked in during fullscreen mode, on the other 
>> it affects system behaviour without being directl tied to display 
>> mode. Hsm
>>
>> -Jeremy Parsons
>
> OS X automatically disabled command-tab when a display capture is 
> performed (using CoreGraphics), so this would be a "free" side effect 
> of AM's classes supporting fullscreen mode. I can only assume that 
> Aleph One currently doesn't do this "properly", so cmd-tab is still 
> active.
>
> --Mark
>

Actually, I'm trying to find a reference to that effect. I've heard it 
before but I haven't seen it documented. When I actually went looking 
for disabling cmd-tab I found this tech note:
TN2062 - Guide to Creating Kiosks on Mac OS
http://developer.apple.com/technotes/tn2002/tn2062.html

And while good and useful, the SystemUIMode API only seems to apply to 
10.2. So at some point I'll try and see about mastering weaking-linking 
and OSX.

And other notes, like Omni's paper on porting games to OSX (typically 
with Cocoa) seemed to indicate no such ability at all to disable 
Cmd-Tab.

AO appears to use a neat little set of DisplayManager related classes, 
but still uses screen_window and backdrop window for the actual display 
of things.

AM at best seemed to luck out and have existing classic code still 
capable of doing depth switches, but which drops the ball on resolution 
switches. But itself still has the screen_window and backdrop_window. 
(Though in my current branch few things directly know about 
screen_window anymore)

-Jeremy Parsons