test case pointers?
wine-devel at kievinfo.com
Sun Nov 13 15:38:16 CST 2005
Sunday, November 13, 2005, 1:41:14 PM, Molle Bestefich wrote:
> Dmitry Timoshkov wrote:
>> Molle Bestefich wrote:
>> > Patching winpos.c to not touch those 4 variables does not seem to
>> > cause any other regressions (as far as I can see), so my immediate
>> > thought is that this is the right and correct thing to do.
>> you haven't even shown real windows behaviour, or a test case.
> COULD SOMEONE KNOWLEDGEABLE IN MinMax STUFF KINDLY POINT ME AT: WHAT
> EXACTLY NEEDS TO BE TESTED Re: ABOVE MENTIONED PATCH + A GUIDE HOW TO
> CREATE A WINE TEST CASE?
> (mail quantity doesn't work, maybe turning the volume knob up will :->..)
> (yes, I do realize I'm a helpless newbie.)
Look inside dlls/user/msg.c tests. Basically you need to test what CreateWindow
and ShowWindow does when called on different kinds of windows (overlapped,
popup, mdi, child). That code is a really tricky one when you fix one case, you
brake other cases.
More information about the wine-devel