Re: 21.0 TTY show-stopper
Andy Piper <andyp(a)parallax.co.uk> writes:
At 22:50 06/01/99 -0800, SL Baur wrote:
>I can't duplicate this because I get something far, far worse. :-(
>Consider the release on hold. (Dang it!)
You're the boss, but for my £0.02 I say ship it. If we don't ship it now it
will be another 6 months more than likely.
I agree. Even if somebody can fix it soon, we should still test it for
a couple of weeks to see if the fix breaks anything else -- this is
redisplay() after all!
I stepped through two instances of redisplay() -- one with a split and
one with an unsplit frame and I must admit that I don't know what is
going on. It's really easy to get confused in redisplay.
One difference I noticed is that in the split case
'windows_structure_changed' was set in the frame structure, while it
wasn't in the unsplit case. Is that intentional? Does that ring a bell
for anybody?
If someone got too much time on their hands it might be instructive to
step through the split case on 20.4...
Gunnar
--
Gunnar Evermann
Speech, Vision & Robotics Group
Engineering Department
Cambridge University