http://bugs.winehq.org/show_bug.cgi?id=10805
Summary: EmEditor hangs Product: Wine Version: 0.9.51. Platform: PC URL: http://www.emeditor.com/modules/download2/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gdi-(printing) AssignedTo: wine-bugs@winehq.org ReportedBy: echidnaman@gmail.com
Upon execution, EmEditor prints a single fixme to the console. It then hangs indefinitely, munching CPU.
The fixme: err:statusbar:StatusWindowProc unknown msg 204e wp=0101 lp=7beab99c
http://bugs.winehq.org/show_bug.cgi?id=10805
Louis Lenders xerox_xerox2000@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox_xerox2000@yahoo.co.uk Status|UNCONFIRMED |NEW Component|wine-gdi-(printing) |wine-comctl32 Ever Confirmed|0 |1
--- Comment #1 from Louis Lenders xerox_xerox2000@yahoo.co.uk 2007-12-17 12:26:02 --- Confirming. The bug is likely related to the printed fixme, as it starts just fine for me using native comctl32.dll (changed component)
http://bugs.winehq.org/show_bug.cgi?id=10805
philip.kent@ntlworld.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |philip.kent@ntlworld.com
--- Comment #2 from philip.kent@ntlworld.com 2007-12-17 13:58:27 --- I am using Wine 0.9.49 (sorry for the older release, Fedora is being slow). I am using EmEditor version 6.00.4.
I was able to reproduce this bug, and I got the same error described.
http://bugs.winehq.org/show_bug.cgi?id=10805
--- Comment #3 from Jonathan echidnaman@gmail.com 2007-12-17 14:04:31 --- Ah, my bad. I forgot to specify which version I was using in the original report. I'm using 6.00.4.
Anyway, good to see a workaround. I wasn't sure which native dll to try since the fixme didn't explicitly state which dll it used. <.<
http://bugs.winehq.org/show_bug.cgi?id=10805
Mikolaj Zalewski mikolaj.zalewski@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mikolaj.zalewski@gmail.com
--- Comment #4 from Mikolaj Zalewski mikolaj.zalewski@gmail.com 2008-01-31 14:02:12 --- This is a problem in the rebar code. The app goes into infinite recursion - a relayout generates RBN_CHILDSIZEs whose handler sends RB_SETBANDINFO what generates a relayout.
The native control doesn't send RBN_CHILDSIZE for RB_SETBANDINFO if the children sizes didn't change. We have some code in CommonSetupBand that checks if the values changed which can be improved to make this app start. But this is not the way it is done in native - in native changing the text from "ABC" to "ACB"doesn't generate a RBN_CHILDSIZE what suggests it is done during layouting (or during something similar to ValidateBand)
http://bugs.winehq.org/show_bug.cgi?id=10805
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
--- Comment #5 from Austin English austinenglish@gmail.com 2008-06-04 11:22:56 --- Is this still an issue in 1.0-rc3 or newer wine?
http://bugs.winehq.org/show_bug.cgi?id=10805
--- Comment #6 from Jonathan echidnaman@gmail.com 2008-06-04 15:09:46 --- Yup.
http://bugs.winehq.org/show_bug.cgi?id=10805
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #7 from Austin English austinenglish@gmail.com 2008-12-06 20:20:02 --- Works fine in 1.1.10.
http://bugs.winehq.org/show_bug.cgi?id=10805
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Alexandre Julliard julliard@winehq.org 2008-12-20 09:03:29 --- Closing bugs fixed in 1.1.11.
-
wine-bugs＠winehq.org