🚀 go-pugleaf

In article <1992Aug1.222645.591@prim> prim!dave@germany.eu.net (Dave Griffiths) writes:
>In article <l7fr1cINNse8@ai.cs.utexas.edu> yu@cs.utexas.edu (Yeong-Ho Yu) writes:
>>I tried to capture the postscript context of the previous application
>>by putting
>>
>>int caller = [NXApp activeApp]
>>
>>either in the action routine of the utility button or
>>appDidBecomeActive method of the utility application, but
>>the value seemed to have changed to that of the utility already.
>>(I wish they had a method called appWillBecomeActive.)
>>
>
>I agree. I also would like the context of the previous application for a
>similar reason. In my app I would like to have some buttons which you press
>when you are in some other app and which do something (eg post events) to
>the current app. The whole concept of a Service needs to be much broader.
>
>Anyone from NeXT care to comment? (I guess I already know the answer :-)

I was flamed by people at NeXT for tinkering with the activeApp in
Stylist.  Apparently there are some directives for the services file
documented _somewhere_ (I think it's in the 2.1 release notes...) for
controlling the activation of applications during a services run.

Also, NeXT doesn't seem to like it when developers use services for
more than the most simple of tasks... it's a shame since services are
so *powerful*!


andrew
<there's just so much good stuff in NeXTSTEP that it becomes hard to
'discover' the more obscure features (and when you do find it, it
could be broken... [see 2.1 NXDynamicServices()])>
-- 
andrew@cubetech.com
Andrew Loewenstern      | "Remember what the doormouse said...
Cube Technologies, Inc. |  Feed your head."  - Jefferson Airplane