Hi! The class regression will require new code which is now running in my test tree. Modifying ComCtl32 class initialization will fix it. The new code is for side by side support that is in it's infancy. Due to, wine is not enough, themes are relegated to Linux/X11, but there are patches available that have provided us with clues.
http://www.winehq.org/pipermail/wine-patches/2009-December/082963.html <-- simple fix for classes http://www.winehq.org/pipermail/wine-patches/2009-December/082965.html http://www.winehq.org/pipermail/wine-patches/2009-December/082967.html
Also, wine actctx.c does not support everything, this too, will need ReactOS patches.
TME, I've reopened bug 6257, when the mouse moves over an icon and it is raised, move off to the caret of quickly move off, without moving to another icon, it stays raised. I have fixed this (again) in the test tree with less or same amount of errors from the ApiTest. Restored the user call API and the timer. The latest patches to TME, has errors, these too have been fixed.
I do not see anything I have here other than sharing code will effect anything if I decide to commit it. Worse case just #if it out. These are critical for themes! This should be push upward not just wait for the next release with broken class code.
Thanks, James
On Tue, Oct 11, 2011 at 3:38 AM, Aleksey Bragin aleksey@reactos.org wrote:
Hello! As per discussion during the last status meeting, I proposed to set up a deadline for having a 0.3.14 Release Candidate available by the time of the next meeting. Olaf, Amine and others were kind enough to make an up-to-date list of critical bugs and regressions to be fixed. It's available here: http://www.reactos.org/wiki/Buglist (indeed this page should be in your web browser's Favorites!) .
I want to ask all of you to concentrate on fixing regressions and critical/blocker bugs first, before going into fancy features or implementing something else. It's really important, we need to make 0.3.14 as the last release before switching to 0.4. We have all necessary prerequisites, and just need to sit down and fix regressions.
I personally put off all of my ReactOS-related "fancy" projects because I want a solid trunk first, and I am working only on stuff which is urgently needed - fixing remaining LDR rewrite regressions, special pool to catch pool corruptions, etc. It's meaningless to work on something else now if regressions aren't fixed.
Hopefully you will follow my advice and we will have a wonderful bugfixing week(s)!
Thank you!
WBR, Aleksey Bragin.