weird ?clipping? errors

[James Hawkins]

Hi,

After my last patch that fixed a stack-trasher was committed, the
Kazaa Lite configuration wizard, KLConfigWizard.exe, can successfuly
run to completion, but the user better not press the 'Back' button
whilst running through the wizard, because he won't see anything anymore.  So
the problem is, if the user presses the back button on the wizard,
any text or images etc that were originally on that frame of the
wizard are now gone
and cannot be seen.  I have a couple of screenshots to show what im
talking about.  Take a look at [1].  This is what the user should see
when he runs the program initially.  You'll notice in [2] that the
left hand side of the window does not show what should be shown as
seen in [1].  After clicking 'Next' we're presented with [3].  This
frame actually is complete (except for a weird ?font spacing? problem
at the bottom), but when we press the 'Back' button to go back to the
first frame, we have [4].  The entire window is now missing, and that
is what happens on all of the windows when you try to go back to them.
I've tried to examine the relay traces to see what could be
happening, but I just dont know what im supposed to be looking for
with this error.  It seems to me to be a clipping problem, but that
might not be it either.  If you have any ideas about this, please let
me know, because I'm sure this isnt the only program affected by this
bug.

[1] http://www.andrew.cmu.edu/user/jhawkins/klite-actual.jpg
[2] http://www.andrew.cmu.edu/user/jhawkins/klite-1.jpg
[3] http://www.andrew.cmu.edu/user/jhawkins/klite-2.jpg
[4] http://www.andrew.cmu.edu/user/jhawkins/klite-3.jpg

[Mike McCormack]

James Hawkins wrote:
> After my last patch that fixed a stack-trasher was committed, the
> Kazaa Lite configuration wizard, KLConfigWizard.exe, can successfuly
> run to completion, but the user better not press the 'Back' button
> whilst running through the wizard, because he won't see anything anymore.  So

As you're dealing with a wizard/propsheet control, to check whether the 
problem is in the code for that control, or a problem with the painting 
code, try substituting comctl32.dll from a Windows 2000 machine, and see 
if the error goes away.  You should notice some differences between the 
way the native comctl32.dll and Wine's implementation draw things...

If they error stays, then you're dealing with a painting bug, which is 
probably hard to solve.

If the error disappears, then you're dealing with a bug in Wine's 
comctl32.dll. You can compare the +message traces with the native dll 
and the builtin one, and see if you can spot the difference.  I usually 
run the trace until I see the first instance of the error then press ^C, 
then repeat for the working case, then compare the two logs in two 
xterms the same size.

Mike

[James Hawkins]

> If the error disappears, then you're dealing with a bug in Wine's
> comctl32.dll.

I used native comctl32.dll and both of the errors disappeared, so I
will take your advice and search around in comctl32.

On Sun, 05 Sep 2004 12:40:58 +0900, Mike McCormack  wrote:
> James Hawkins wrote:
> > After my last patch that fixed a stack-trasher was committed, the
> > Kazaa Lite configuration wizard, KLConfigWizard.exe, can successfuly
> > run to completion, but the user better not press the 'Back' button
> > whilst running through the wizard, because he won't see anything anymore.  So
>
> As you're dealing with a wizard/propsheet control, to check whether the
> problem is in the code for that control, or a problem with the painting
> code, try substituting comctl32.dll from a Windows 2000 machine, and see
> if the error goes away.  You should notice some differences between the
> way the native comctl32.dll and Wine's implementation draw things...
>
> If they error stays, then you're dealing with a painting bug, which is
> probably hard to solve.
>
> If the error disappears, then you're dealing with a bug in Wine's
> comctl32.dll. You can compare the +message traces with the native dll
> and the builtin one, and see if you can spot the difference.  I usually
> run the trace until I see the first instance of the error then press ^C,
> then repeat for the working case, then compare the two logs in two
> xterms the same size.
>
> Mike

[Steven Edwards]

Hi,

--- James Hawkins  wrote:
> me know, because I'm sure this isnt the only program affected by this
> bug.

The mozilla installers show this as well.

Thanks
Steven

_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush