http://bugs.winehq.org/show_bug.cgi?id=4605
--- Comment #10 from Bernd Buschinski <b.buschinski(a)web.de> 2008-01-22 07:21:57 ---
Created an attachment (id=10402)
--> (http://bugs.winehq.org/attachment.cgi?id=10402)
reisederpinguine_exe 1/3
it runs again with recent cvs wine but the issue is still present
It gets bigger as it should, but in windows I cant make the window smaller,
works fine in wine, it shouldnt
I am going to attach the app, as it might help
cat reisederpinguine_exeaa >> reisederpinguine_exe.tar.bz2
cat reisederpinguine_exeab >> reisederpinguine_exe.tar.bz2
cat reisederpinguine_exeac >> reisederpinguine_exe.tar.bz2
and again on windows the app windows doesnt get smaller
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=2596
Jan Vitense <jvschrott(a)hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvschrott(a)hotmail.com
--- Comment #25 from Jan Vitense <jvschrott(a)hotmail.com> 2008-01-22 06:51:23 ---
Hi there,
I figured out that the lower the graphics settings in FS 98, the longer you can
fly. The lowest setting gives me approx. one minute of flying time. With the
highest graphic setting, the game crashes just after takeoff, giving a
"segmentation fault".
I am using wine-0.9.46 under Ubuntu 7.10 on a 700MHz Pentium 3.
I would be really happy getting FS 98 to run. My computer is too slow for
Flightgear, and FS 4 is a little too old...
Greetings,
Jan Vitense
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8683
--- Comment #23 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2008-01-22 05:45:34 ---
(In reply to comment #22)
> Just saw the reason. in unicode, ß is 0xdf and uppercase ß (ẞ) is 0x1e9e.
> (I didn't even know that an uppercase ß exists - AFAIK it's not used in the
> german language.)
> Unless WoW running under Windows with the DE keyboard layout have the same bug
> (unlikely, since it's also sold in Germany) it seems that we found an exception
> to the rule that MapVirtualKeyEx always returns uppercase characters.
You can't trust Wine implementation, that's why I said that you need to write
a test case to how it's supposed to behave.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8683
--- Comment #22 from Fábio Capela <fabio.capela(a)yahoo.com> 2008-01-22 05:33:00 ---
(In reply to comment #21)
> So, both return a properly encoded UTF-8 string but with different unicode
> characters.
Just saw the reason. in unicode, ß is 0xdf and uppercase ß (ẞ) is 0x1e9e.
(I didn't even know that an uppercase ß exists - AFAIK it's not used in the
german language.)
Unless WoW running under Windows with the DE keyboard layout have the same bug
(unlikely, since it's also sold in Germany) it seems that we found an exception
to the rule that MapVirtualKeyEx always returns uppercase characters.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=1503
Saulius K. <saulius2(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|-unknown |user32
--- Comment #14 from Saulius K. <saulius2(a)gmail.com> 2008-01-22 00:39:30 ---
A new location of a patch in mail-archives:
http://www.winehq.org/pipermail/wine-cvs/2004-June/010516.html
Hence, setting strict component.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=3966
--- Comment #59 from Peto <tuharsky(a)misbb.sk> 2008-01-21 23:13:45 ---
Cannot test because the bug 6789 is blocking any further testing.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=3937
--- Comment #33 from Peto <tuharsky(a)misbb.sk> 2008-01-21 23:11:53 ---
Yes, with 0.9.53 it seems fixed.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=5851
--- Comment #4 from Peto <tuharsky(a)misbb.sk> 2008-01-21 23:10:53 ---
Yes, it is still an issue with 0.9.53
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=5849
--- Comment #28 from Peto <tuharsky(a)misbb.sk> 2008-01-21 23:09:52 ---
Yes, it is still an issue with 0.9.53
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8683
--- Comment #21 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2008-01-21 21:59:51 ---
(In reply to comment #20)
> added a trace and saw that for the ß key the call to XLookupString inside
> X11DRV_MapVirtualKeyEx seems to be generating bad results.
> When called inside X11DRV_KeyEvent and inside X11DRV_ToUnicodeEx:
> keysym=DF (ssharp), # of chars=2 / "\xc3\x9f"
ret = MultiByteToWideChar(CP_UTF8, 0, "\xc3\x9f", 2, buf, 10);
ret = 1, buf[0] = 00df
> When called inside X11DRV_MapVirtualKeyEx to map the same keycode:
> keysym=1001E9E, # of chars=3 / "\xe1\xba\x9e"
keysym 1001E9E is an X11 direct unicode mapping of 0x1E9E
ret = MultiByteToWideChar(CP_UTF8, 0, "\xe1\xba\x9e", 3, buf, 10);
ret = 1, buf[0] = 1e9e
So, both return a properly encoded UTF-8 string but with different unicode
characters.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.