The code as it stands now is wrong. It wrongly deletes events from the event queue in a mistaken attempt to fix something. It then leaves the application in a unusable state.
> I wonder if this is related to the following: > http://www.mail-archive.com/fvwm-workers@fvwm.org/msg02258.html The patch in the message just adds another set of events to be processed. The code correction does no harm and correctly displays a popped down widget when the application requests the widget to pop-up. If you have a failing Qt test case, please send it to me or a pointer to it. I couldn't find it when I was researching this problem. R. On Tue, 1 Mar 2011 09:17:41 +0000 Thomas Adam <tho...@fvwm.org> wrote: > On Mon, Feb 28, 2011 at 10:02:45PM -0600, Rich Coe wrote: > > During map processing event (1) would cause the event to be ignored, > > thus > > pre-empting the request for a successful unmap and re-map action, and > > leaving the window in the unmap state. > > I wonder if this is related to the following: > http://www.mail-archive.com/fvwm-workers@fvwm.org/msg02258.html > > > Correction: > > > > Removed code which erronously removed events from the queue. > > > > Added code to process a map window request for a parented window that > > no longer exists as if the parent was really the root window. > > I don't think this is going to work with Qt-based applications though. > > I'll look at this later on. It's not going in to FVWM now -- it's too big a > change. > > -- Thomas Adam -- Rich Coe r...@wi.rr.com
