> okaydokey, I have a main menu form from which I would like to fire up
> other forms etc, the problem is I have created the other form in another
> file contained the cb.c main.c .h .c files.
> Is there anyway in which I can, upon clicking a button, pass control to
> this other file with its own fl_do_forms(); ?
> After the form has been quit it should just fall back to its calling form,
> I hope.
>
> I have done it this way to keep the code in logical manageable chunks.
If the other module indeed has its own main() function, then the only
way to do it is to do fork() and exec() system calls.
I'm not sure, however, that this is the right approach.
Do you want to freeze activity in the spawning form and commence
activity in the new form? Why not just fire up the new form, freeze
the old one with fl_freeze_form(), and then exit the callback in the
normal manner.
Having two event loops is, in general, a Bad Thing.
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/xforms-archive/