>PS: I'll put support for bidirectional communcation with the Xt
>application on the feature request list for the 2.0 release.
>
the aspect that made the communication difficult was that metacard will
watch for property changes on the window specified by the "-w" switch, but
it will only "post" property changes for metacard function/command calls to
its own window (which is used in the external.c demo). thus my hacked code
has to watch for property events on two windows. the first is the window
which is specified by the X/external Application through the "-w" command
option. the second is the metacard window itself. to get the metacard
window,
1. start up X in my app and pass the first window via the "-w" option
2. start metacard - - which will watch the "-w" specified window
3. get the windowid property from metacard (either by passing a global or
evalexpr)
4. set the external app to watch the metacard window also (using XSelectInput)
- - for external function/command calls.
thus, on the request list, it should be put that the "-w" option specifies
the place that all X-window properties are modified and watched for by
metacard.
-jim
*******************************************************************
* James M. Cardinal *
* Graduate Research Associate *
* Life-Cycle Design Lab & ERC/NSM, The Ohio-State University *
* Phone: (614) 292 - 2849 *
*******************************************************************