> You have a point here, I'll make that change.
> I have actually changed the way shutdowns work slightly.
>
> ** Note to Linas: you should probably ignore all of
> ** my patches except for the last :)
>
> Instead of destroying resources, the ui_shutdown code just makes them
> invisible and causes the event loop to terminate. Then, when the
> application as a whole shuts down, a ui_destroy function is called
> which is responsible for destroying them. This makes stopping and
> restarting the ui more efficient and enables me to solve the problem
> I was having in this area on the Motif side.
Ok, I'm commenting on my own comments here :)
OTOH, the problem I was seeing was Motif's apparent inability
to create a second application after the first has been
destroyed. However, this may just be a lesstif bug, rather
than a fundamental limitation.
It might be better to really destroy the application when
you drop to the shell, and then rebuild it, since you might
be changing things while you're in the shell.
OTOH, guile is also changing things while the ui is running
so this is a problem we have to solve anyway.
I'd better go to bed now.
dave
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
