http://bugs.winehq.org/show_bug.cgi?id=23282
Summary: SpeQ: Wrong coded linefeed Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: samoth@gmx.de
Since the 1.1.4x releases the editor in SpeQ Mathematics doesn't work right anymore. Normally if entering an expression an hitting the return key, SpeQ prints the result. This works allright with the first wine-version I used (1.1.38 ?).
But now hitting the return key results in additional unvisible characters and nothing happens until I do a sheet-calculation. Then SpeQ cannot calculate the expression due to these unvisible characters. Maybe it is the order of coding a linefeed via 0d 0a.
SpeQ ist available for free at http://www.speqmath.com
http://bugs.winehq.org/show_bug.cgi?id=23282
--- Comment #1 from Andrew Nguyen arethusa26@gmail.com 2010-06-20 10:01:22 --- Please perform a regression test:
http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=23282
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Version|unspecified |1.1.40
http://bugs.winehq.org/show_bug.cgi?id=23282
Niko Sandschneider nsandschn@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nsandschn@gmx.de
--- Comment #2 from Niko Sandschneider nsandschn@gmx.de 2010-06-22 14:43:48 --- Confirming with wine-1.2-rc4-70-g802c4de. But I'm not sure that it is indeed a regression. I went as far back as wine-1.1.25 and I always saw the same behaviour. 'winetricks riched20' works around it. There is no terminal output. Thomas, are you sure that wine-1.1.38 was your wine version? And that you didn't have native riched20 installed?
http://bugs.winehq.org/show_bug.cgi?id=23282
--- Comment #3 from Thomas samoth@gmx.de 2010-06-24 02:43:31 ---
Thomas, are you sure that wine-1.1.38 was your wine version? And that you didn't have native riched20 installed?
I don't really remember. I started to use linux some months ago and I've installed the wine-version from kubuntus software management. But I'm sure that the version number was 1.1.38 or 1.1.39. I don't have manually installed anything like riched 2.0. Maybe using winetricks or installing mupad did the job. (I had tried to install the mediaplayer).
In my system32-directory I find riched20.dll and riched32.dll.
But I know that SpeQ works fine to me and then after having upgraded to 1.1.40 or 1.1.41 this error appears.
Sorry, that I cannot give you better informations.
Please perform a regression test:
Due to lack of time I can't do the regression-test now. (I didn't have done this before so I expect that I need some more time as usual.) So perhabs next week.
http://bugs.winehq.org/show_bug.cgi?id=23282
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://www.speqmath.com CC| |mstefani@redhat.com
http://bugs.winehq.org/show_bug.cgi?id=23282
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #4 from Michael Stefaniuc mstefani@redhat.com 2010-11-14 17:39:30 CST --- Confirming the bug per comment #2
http://bugs.winehq.org/show_bug.cgi?id=23282
--- Comment #5 from Thomas samoth@gmx.de 2010-11-17 11:35:17 CST --- I found this workaround:
I've downloaded a fresh riched32.dll and in wine-config I set
riched20.dll disabled riched32.dll native windows
then speq works again. I wonder that before I'd never done this.
regards, thomas
http://bugs.winehq.org/show_bug.cgi?id=23282
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |richedit
--- Comment #6 from Austin English austinenglish@gmail.com 2010-11-19 01:12:31 CST --- Please attach a +richedit log with builtin richedit.
http://bugs.winehq.org/show_bug.cgi?id=23282
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh@gmail.com
--- Comment #7 from Jerome Leclanche adys.wh@gmail.com 2011-10-08 17:32:23 CDT --- Does this still happen/is anyone able to test? I'll try it tomorrow otherwise.
http://bugs.winehq.org/show_bug.cgi?id=23282
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.1.40 |1.1.12 Regression SHA1| |603be645d2d77a028c3f209be17 | |42d7dccb64372
--- Comment #8 from Austin English austinenglish@gmail.com 2011-11-01 22:18:00 CDT --- Fails in 1.3.35/1.3.38 for me. Does work in 1.0, though.
Still in wine-1.3.31-261-g3f74c58.
Regression testing indicates: austin@aw25 ~/wine-blah $ git bisect bad 603be645d2d77a028c3f209be1742d7dccb64372 is the first bad commit commit 603be645d2d77a028c3f209be1742d7dccb64372 Author: Dylan Smith dylan.ah.smith@gmail.com Date: Sun Jan 11 02:59:09 2009 -0500
richedit: Pressing enter adds newline on WM_KEYDOWN rather than WM_CHAR.
:040000 040000 bc87106bcdaaccf9e6d33db93b7bca266dbf898b df13f937cfa4710cbecc85049cbde50d72558c71 M dlls
which makes the first broken version wine-1.1.12-472-g603be64.
I'll attach logs.
http://bugs.winehq.org/show_bug.cgi?id=23282
--- Comment #9 from Austin English austinenglish@gmail.com 2011-11-01 22:18:15 CDT --- Created attachment 37252 --> http://bugs.winehq.org/attachment.cgi?id=37252 +richedit trace, broken
http://bugs.winehq.org/show_bug.cgi?id=23282
--- Comment #10 from Austin English austinenglish@gmail.com 2011-11-01 22:18:30 CDT --- Created attachment 37253 --> http://bugs.winehq.org/attachment.cgi?id=37253 +richedit trace, working
http://bugs.winehq.org/show_bug.cgi?id=23282
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dylan.ah.smith@gmail.com
--- Comment #11 from Austin English austinenglish@gmail.com 2011-11-01 22:18:58 CDT --- CC'ing author.
http://bugs.winehq.org/show_bug.cgi?id=23282
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.1.12 |1.1.13
--- Comment #12 from Dmitry Timoshkov dmitry@baikal.ru 2011-11-01 23:14:36 CDT --- The offending patch has been released first as a part of wine-1.1.13
http://bugs.winehq.org/show_bug.cgi?id=23282
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.1.13 |1.1.12
--- Comment #13 from Austin English austinenglish@gmail.com 2011-11-01 23:32:54 CDT --- (In reply to comment #12)
The offending patch has been released first as a part of wine-1.1.13
It was agreed a while back that we would use whatever wine --version reported.
(if memory serves correctly, you were the one that pushed for that most..).
http://bugs.winehq.org/show_bug.cgi?id=23282
--- Comment #14 from Dmitry Timoshkov dmitry@baikal.ru 2011-11-02 00:05:32 CDT --- (In reply to comment #13)
(In reply to comment #12)
The offending patch has been released first as a part of wine-1.1.13
It was agreed a while back that we would use whatever wine --version reported.
(if memory serves correctly, you were the one that pushed for that most..).
Only for cases when you'd use GIT instead.
http://bugs.winehq.org/show_bug.cgi?id=23282
--- Comment #15 from Dylan Smith dylan.ah.smith@gmail.com 2011-11-03 08:35:50 CDT --- Richedit version 1.0 (used by this app) responds to the enter key in WM_CHAR, but version 3.0 responds to the enter key in WM_KEYDOWN. This seems to be the source of the regression.
I simply tested by commenting out TranslateMessage(&msg); in wordpad.c, since that seems to produce the WM_CHAR events from the WM_KEYDOWN events. Afterword typing in wordpad will quickly reveal what events are handled in WM_KEYDOWN, and those that don't work are handled in WM_CHAR.
http://bugs.winehq.org/show_bug.cgi?id=23282
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |frederic.delanoy@gmail.com
--- Comment #16 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-04-02 02:57:10 CDT --- Still in wine-1.5.1
http://bugs.winehq.org/show_bug.cgi?id=23282
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=23282
--- Comment #17 from Bruno Jesus 00cpxxx@gmail.com 2013-03-01 17:53:16 CST --- Still in wine 1.5.25.
http://bugs.winehq.org/show_bug.cgi?id=23282
--- Comment #18 from Frédéric Delanoy frederic.delanoy@gmail.com 2013-06-30 12:46:28 CDT --- Still in 1.6-rc4
https://bugs.winehq.org/show_bug.cgi?id=23282
--- Comment #19 from Frédéric Delanoy frederic.delanoy@gmail.com --- Still in wine-1.9.18-121-g4e9cc30
https://bugs.winehq.org/show_bug.cgi?id=23282
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #20 from joaopa jeremielapuree@yahoo.fr --- Is still a bug in current wine (3.20)?
https://bugs.winehq.org/show_bug.cgi?id=23282
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #21 from Fabian Maurer dark.shadow4@web.de --- Still present as of wine-3.21. "winetricks riched20" fixes the issue.
https://bugs.winehq.org/show_bug.cgi?id=23282
--- Comment #22 from Fabian Maurer dark.shadow4@web.de --- Submitted a patch to fix this issue: https://source.winehq.org/patches/data/155751
https://bugs.winehq.org/show_bug.cgi?id=23282
--- Comment #23 from Fabian Maurer dark.shadow4@web.de --- Patch was broken, submitted a new patchset. As noted, the actual problem is that riched v1 handles VK_RETURN in WM_CHAR while v2 does in WM_KEYDOWN.
https://bugs.winehq.org/show_bug.cgi?id=23282
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Fixed by SHA1| |52c106418c60141ab816b065eb1 | |56df271218228 Status|NEW |RESOLVED
--- Comment #24 from Fabian Maurer dark.shadow4@web.de --- Fixed as of https://source.winehq.org/git/wine.git/?a=commit;h=52c106418c60141ab816b065e...
https://bugs.winehq.org/show_bug.cgi?id=23282
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #25 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 4.0-rc2.