save bug

[Derek Atkins]

Herman <Herman at AerospaceSoftware.com> writes:

> On Friday 19 September 2003 11:03 am, Derek Atkins wrote:
> 
>    Yea, but it currently doesn't work right, and I think part of the
>    problem is that if you have unsaved work there isn't a good way to pop
>    up a dialog saying "wait" because you've already destroyed the main
>    window.
> 
>    The real fix will be moving to an embedded-SQL backend so we DONT have
>    to force-save the work (and we wouldn't need log-replaying, either).
> 
> 
> Hmm, can't you fix this just by changing the order of the actions?
> 
> If you get a close window command, don't just go and blow it away immediately, 
> fist check a few things.

It depends on what the window manager does.  You don't necessarily
get a close-window event -- sometimes it's a destroy operation which
destroys the connection to the X server before you can do anything else.

-derek
-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available