[ros-bugs] [Bug 4778] Class rewrite, bugs and all related
ReactOS.Bugzilla at reactos.org
ReactOS.Bugzilla at reactos.org
Fri Sep 4 23:43:53 CEST 2009
http://www.reactos.org/bugzilla/show_bug.cgi?id=4778
--- Comment #8 from jimtabor <jimtabor at adsl-64-217-116-74.dsl.hstntx.swbell.net> 2009-09-04 23:43:52 CET ---
Fixed the line 399 to line 409 failures for kernel32.
In UserRegisterClass we call IntGetClassAtom and that tests for four conditions
that return a class and keeps failing. So I copied paste the first two
conditions from IntGetClassAtom and reordered it. Now we pass those conditions
and move on to the last set of problems.....
class.c:215: Test failed: System class #32769 does not exist
class.c:215: Test failed: System class #32771 does not exist
class.c:552: Test failed: Wrong GCL instance 00400000/77E30000 for class BUTTON
class.c:553: Test failed: Wrong GCL instance 00400000/77E30000 for class BUTTON
class.c:554: Test failed: Wrong GCL instance 00400000/77E30000 for class BUTTON
class.c:292: Test failed: Wrong GCL instance 00400000/77E30000 for class BUTTON
class.c:292: Test failed: Wrong GCL instance 00400000/77E30000 for class BUTTON
class.c:292: Test failed: Wrong GCL instance 00400000/77E30000 for class BUTTON
class.c:569: Test failed: Wrong GCL instance 00400000/77E30000 for class EDIT
class.c:292: Test failed: Wrong GCL instance 00400000/77E30000 for class EDIT
class: 677 tests executed (0 marked as todo, 10 failures), 0 skipped.
I've been at work the last two months so I could not log any of my results....
The next rewrite (Window/Msg/Timer/Menu) expect more logging.
Again, the first two will not be fixed, those are Switch and Desktop. Both are
Server Side (Win32k) WndProc's so they are special. ATM Server Side is a hax so
we can pass w(h)ine tests and most of those WndProc's are pointers in User32.
HWNDMESSAGE still points into User32 even when it is Registered in our
win32k....
--
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the Ros-bugs
mailing list