Re: [Pyobjc-dev] NSAppEnableForeground

[Bob I. <bo...@re...>]

On Thursday, Feb 13, 2003, at 16:14 America/New_York, Jack Jansen wrote:

>
> On donderdag, feb 13, 2003, at 21:28 Europe/Amsterdam, Ronald Oussoren  
> wrote:
>
>>
>> On Thursday, Feb 13, 2003, at 14:32 Europe/Amsterdam, Jack Jansen  
>> wrote:
>>
>>> 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:-(
>>
>> Is that list archived anywhere? Considering this information I'm  
>> starting to worry even more about the possible long term effects of  
>> adding this.
>
> It's the tcl-mac list at sourceforge. Look at Jim's postings of  
> 13-Nov-2002:
> https://sourceforge.net/mailarchive/ 
> forum.php?forum_id=3853&max_rows=25&style=flat&viewmonth=200211&viewday 
> =12
>
> In reality it's a bit different than I remembered it, though:
> - the responsible people didn't specifically want to change it, they  
> wanted to be able to decide whether to open it up later.
> - The good news is that they seem to think that this whole business of  
> having to run in a .app bundle may really be a bug...

I could rewrite the patch again to try and find the symbol dynamically  
and do nothing if it can't find it.. but anyways, I just made a diff  
that doesn't require libFoundation.a, I also changed setup.py to  
override "-flat_namespace -undefined suppress" with "-bundle_loader %s"  
% (resolve_to_actual_file(sys.executable),).. which would catch the  
symbol-doesn't-exist bug really quickly, and solves some other issues  
with python modules and namespaces..  I also added a FLAT_NAMESPACE  
flag to the top of setup.py, so if someone were to try and backport to  
10.1 they could just turn it on and the -bundle_loader replacement  
wouldn't happen anymore.

-bob