Yet another New NeXTanswer: services activation

Thread View: comp.sys.next.programmer

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Kate Smith Wed, 14 Oct 1992 00:09

#1463

Author: Kate Smith
Date: Wed, 14 Oct 1992 00:09

31 lines
1721 bytes

Q:  My app provides a Service, but I want it to behave a little  
differently than usual.  Specifically, I don't want the app requesting the  
Service to deactivate, and I don't want my app to become the active app  
when it receives the data.  This way, users can send data to this service  
without being thrown out of whatever app they're in.  Is this possible?

A:  Yes!  Service providers can dictate whether or not they're activated  
when providing a Service, as well as whether or not the requesting app  
deactivates, through the following two options in the Services message  
description:

	Activate Provider: <YES or NO>
	Deactivate Requestor: <YES or NO>
  
Specifying NO in the Activate Provider field instructs the Services  
machinery to launch the Service provider (if not already launched) but not  
make it the active application.  Specifying NO in the Deactivate Requestor  
field instructs the Services machinery not to deactivate the application  
requesting the Service.  

Omitting one of these two fields is equivalent to specifying YES.

N.B.  Be careful how you use this feature.  Technically, you can have any  
combination of provider and requester activation but it would violate user  
interface guidelines.  It really only makes sense to set these both to  
either YES or NO, but not a combination of the two.

QAxx

Valid for 2.0
Valid for 3.0

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads