Bill.Chiles@WB1.CS.CMU.EDU (03/09/89)
I'm having two problems with the R3 version of twm, one of which is much
more severe than the other. I only experience these using CLX, but I used
xscope to verify the data was bad before it entered CLX. I don't think
anything has gone by about these problems, but if I missed something, I'm
sorry for the repeat.
The first and more important problem is that configure notifications are
coming in with the above-sibling field set to a non-window ID, such as 8.
I notice this occurs when I do something that cause the new twm to send a
configure notification to my client. Under CLX, I get an error that this
ID is not a window ID. Probably no one is C land has been bitten by this
because they just don't look at the trash in the event structure, but CLX
always maps this ID to a window to pass a Lispy thing to handlers instead
of an ID. I note that twm causes the event to be forwarded by the server
because the high bit is on in the event ID; somewhere I picked up that this
is some indication that the event was not generated by the server.
Has anyone else noticed this behaviour? Do you have a fix for it?
The second, not so serious problem, is that I'm getting exposure
notifications before reconfiguation notifications when using the new twm
(R3). This never happened with uwm or awm or the R2 twm. I know these are
out of order because I sent the reconfiguration request to the server
myself. Because I know when I'm doing this, I can warped my code to ignore
exposures on this window until the reconfiguration notification comes,
processing exposures after that.
Has anyone else noticed this, and if so, do you have a twm fix?
Bill
P.S.,
I would be happy to have this behavious either confirmed by someone
else or to learn of fixes, especially for the first one.