I think this will be OK, since the amount of data loss would be very trivial. This would be a great thing to put in the realease notes under KNOWN BUGS. Also in order to stem somewhat a deluge of "Abiword can't find Times New Roman" complaints is there anyone who can update the FAQ on the website with the updated one that I posted that did not get commited into 0.90? Pretty please? (it will help much more on the website anyways, it's hard to get to the FAQ in the help if AbiWord won't load) Cheers, tim P.S. Sorry Mike, I didn't mean to send this to you personally. ---------Included Message---------- > Date: Wed, 25 Jul 2001 03:44:00 +0200 > From: "Mike Nordell" <[EMAIL PROTECTED]> > Reply-To: "Mike Nordell" <[EMAIL PROTECTED]> > To: "AbiWord-dev" <[EMAIL PROTECTED]> > Subject: update 964 > > It seems this is a win-only bug. > > I'm fairly sure I know how to fix it, but it obviously won't make it into > 0.9 I'm afraid. :-( > > This is a serious "bummer" since it is a data-loss bug that is so obvious > even M$ could see it. Actually, part of the problem in this bug _is_ M$. > > What happens is that we get WM_DESTROY to the Frame without getting > WM_CLOSE, in XAP_Win32Frame::_FrameWndProc that is. I'm quite sure we _do_ > get the WM_CLOSE, but it gets routed to somewhere else. I can't fix it > in -3.2 hours time, why this will have to make it into 0.9.1. > > This was something we didn't wish for... > > /Mike > > > ---------End of Included Message---------- Content-Type: application/octet-stream; name="" Content-Transfer-Encoding: BASE64 DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tMTMyNTQyNTE2NjE5MDkzOTA1MzkxOTA0 NzI1ODU4
