[Contents] [Index] [Help] [Browse <] [Browse >]
Custom Handlers for Listers
--------------------------------- -- -  -
A custom handler is "attached" to a lister by calling
 lister set  handler  for that lister, giving the name of your
message port. Whenever something interesting happens to your lister, the
handler will be sent an ARexx message.

The handler can be implemented either as a rexx program or as a C program
(in which case it must interpret the rexx message itself).

Unlike Opus 4, messages sent to handlers do not cause Directory Opus 5 to
"hang" until they are replied (although you should try to reply to any
messages as soon as possible).

Note that custom handlers for listers are specific only to the cache that
is visible in the lister at the time the handler name is set. The same
handler port may be used set for multiple caches, and indeed for multiple
listers. 

Note also that message port names are case-sensitive. Be careful that
ARexx doesn't uppercase them. 

The rexx message identifies the type of event, the lister the event
happened to, and other pertinent data.

 List of events 


Converted on 04 Nov 1998 with RexxDoesAmigaGuide2HTML 2.2 by Michael Ranner.