> My project requires that I move a form (or simulate this motion)
> from one display to another.
>
> How shall I do this?
>
> Should I set my DISPLAY environment variable and then call
> fl_initialize() a second time, then hide the one form and show
> the other?
I don't think this will work. You certainly can't call
fl_initialize() more than once in an application. I don't believe
that even calling fl_finish() will reset the library to a pristine,
preinitialization step.
> Must I fork off a child (early on), set the DISPLAY environment
> variable, call fl_initialize(), and create the second form, maintaining
> communication with the parent using a pipe?
This is probably the most straightforward of your choices.
> What support does the Forms Library have for an application that
> uses multiple displays?
There is none at this time. I know there are some internal provisions
for maintaining multiple displays but they aren't implemented fully in
the version that's currently released.
> What am I missing?
Nothing other than reading some of the fine print in the discussion of
the fl_get_display() macro, wherein it says indirectly that multiple
connections are not supported in this current release.
spl
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
XForms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/