• 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
Shielding Windows/Observations About Force Quit
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Shielding Windows/Observations About Force Quit


  • Subject: Shielding Windows/Observations About Force Quit
  • From: Buzz Andersen <email@hidden>
  • Date: Fri, 20 Sep 2002 09:43:42 -0600

Hey all,
It appears that when an application has a shielding window, OS X treats it differently as far as "Force Quit" is concerned:

1. When the user performs the "Force Quit" key combination, instead of popping up the normal dialog, it simply forces the application to quit.

2. It also appears to me that "Force Quit" initially sends a SIGINT to the application. I can, of course, ignore this using signal(). But, after a short delay, when the application is still running, it sends a SIGKILL, which, of course, I can't ignore.

My question is, is this: I want to make a screen locking app that uses a shielding window, but for security reasons, I don't want people to be able to simply use the force quit key combination to defeat it. Does anyone know of a way around this, given the fact that I can't ignore SIGKILL. Is there a way to lock the keyboard, or intercept the key combination (I kind of doubt the latter)? It seems like I might have been able to use InputSprockets in OS 9, but that isn't an option anymore, evidently.

If anyone has any novel ideas or could point me in the right direction, I would be most grateful!

--
Buzz Andersen
email: email@hidden
web: http://www.scifihifi.com
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Shielding Windows/Observations About Force Quit
      • From: Andreas Mayer <email@hidden>
  • Prev by Date: Re: [Q] NSThreads and UI
  • Next by Date: Re: UFS can't handle creation date
  • Previous by thread: Re: How do I remove all formatting (setUsesRuler:NO does not work) from an NSTextView?
  • Next by thread: Re: Shielding Windows/Observations About Force Quit
  • Index(es):
    • Date
    • Thread