Article View: comp.sys.next.programmer
Article #1468How to prevent other apps from becoming active ?
From: Izumi Ohzawa
Date: Wed, 14 Oct 1992 09:27
Date: Wed, 14 Oct 1992 09:27
48 lines
2306 bytes
2306 bytes
Keywords: Music, sound, DSP, real-time Reply-To: izumi@pinoko.berkeley.edu Distribution: world Music, sound recording/playback, and other DSP apps that do real-time work often need to get as much processing power as possible. As an option to my real-time app, I would like to add a capability to disable GUI of all other applications (including Workspace/Dock), so they don't get activated inadvertently during a heavy real-time activity. Could anyone point me to an example code that does this or relevant section of the doc? Also, how do I lock down windows and panels of my app so that they can't be moved during real-time activity? Dragging a large window around is very bad for real-time processing. I still need mouse-dragged and other mouse events in views within a window which is locked down. Again, any examples? I incorporated "fixed policy" and maximum priority code by David A. Jaffe (available as file fixedpolicy.tar.Z from ccrma-ftp.stanford.edu), but dragging windows still causes bad things to my app. Users shouldn't be dragging windows and scrolling large regions at a critical moment, but our kind of apps should be able to prevent these unwanted activities which result in a disaster. Thanks, --- Izumi Ohzawa USMail: University of California, 360 Minor Hall, Berkeley, CA 94720 Telephone: (510) 642-6440 Fax: (510) 642-6341 Internet: izumi@pinoko.berkeley.edu (NeXT Mail OK) gging a large window around is very bad for real-time processing. I still need mouse-dragged and other mouse events in views within a window which is locked down. Again, any examples? I incorporated "fixed policy" and maximum priority code by David A. Jaffe (available as file fixedpolicy.tar.Z from ccrma-ftp.stanford.edu), but dragging windows still causes bad things to my app. Users shouldn't be dragging windows and scrolling large regions at a
Technical Details
Message-ID:
<1bgp6nINNr6k@agate.berkeley.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!olivea!spool.mu.edu!agate!agate!usenetShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!spool.mu.edu!agate!agate!usenet From: izumi@pinoko.berkeley.edu (Izumi Ohzawa) Newsgroups: comp.sys.next.programmer Subject: How to prevent other apps from becoming active ? Message-ID: <1bgp6nINNr6k@agate.berkeley.edu> Date: 14 Oct 92 09:27:51 GMT Organization: University of California, Berkeley Lines: 48 NNTP-Posting-Host: moomin.berkeley.edu