Re: [Pyobjc-dev] NSAppEnableForeground

[Jack J. <Jac...@or...>]

I suggest everyone is *very* careful using  
CPSEnableForegroundOperation. It comes up time and again, and most  
recently there was a discussion on the Mac-Tk mailing list about it.  
Jim, the MacTk lead engineer, happens to work at Apple, and he asked  
the people responsible for CPSEnableForegroundOperation to make it an  
official API, but they were unwilling to do so, specifically because  
they want the freedom to change it at will. So you shuldn't be  
surpirsed if you use this in an application and then see the  
application breaking at the next minor MacOSX release:-(

On donderdag, feb 13, 2003, at 10:36 Europe/Amsterdam, Bob Ippolito  
wrote:
> Just to cover bases, CPSEnableForeground is exported by  
> CoreGraphics.framework, which is part of ApplicationServices (and used  
> by AppKit, which you can prove for yourself).
> % nm  
> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ 
> Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics | grep  
> CPSEnableForeground
> 938a54b8 T _CPSEnableForegroundOperation
>
> I will do so once I find the time (likely Saturday or Sunday).. but  
> you should note that the "number of other projects" that use  
> CPSEnableForegroundOperation are __all__ straight up copied from my  
> reverse engineering of the jar runtime, which I did somewhere between  
> dec 2001 and jan 2002... The first project that actually used the code  
> was pygame, as that was what I was working on at the time.   You can  
> tell that it's all derived from my original work by the fact that they  
> all use the same code:
> CPSEnableForegroundOperation(&PSN,0x03,0x3C,0x2C,0x1103);
--
- Jack Jansen        <Jac...@or...>         
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- Emma  
Goldman -