http://bugs.winehq.org/show_bug.cgi?id=10873
Summary: Various display issues in/with Delphi
Product: Wine
Version: unspecified
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-gui
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ionic(a)ionic.de
Created an attachment (id=9765)
--> (http://bugs.winehq.org/attachment.cgi?id=9765)
Font size set to 12 in Delphi/WINE.
Hey all,
after the installation of Delphi worked without noteworthy problems, I am now
experiencing a couple of issues with WINE drawing/printing things, which might
be easily fixable due to the fact that they are just graphical problems.
First one: in Delphi one can set various font sizes for elements like Labels,
Panel and so on, which works fine in Windows. But WINE shows a strange behavior
here: when changing from font size 12 to 14 WINE does nothing, whereas in
Windows the font size really grows. Also, you could set the the size to 100 (I
did for testing purposes in the screenshots), but WINE does not change any size
but uses still the 12pt size, it seems that something is broken there within
WINE.
Well that's happening in the "designer" mode, but it seems to be the same on
runtime, so I guess there might be also other applications hitting that bug
with binary programs (Screenshots flagged with "Runtime") ...
Second one: properties changed in the object inspector should be bold when they
are not set to the default value. That's a nice feature which helps people to
see which property *they* changed and makes it easy to revert bad decisions.
However, WINE does not print them in bold font or anything
This bug is not limited to object inspector though, NO fonts in Delphi's
"design" mode are bold, even when set to that, but instead WINE ignores it,
even in the compiled program later on.
This does NOT hit the editor in Delphi which is able to show wonderful bold
text.
You can find plenty examples for this bug in the "Delphi-Size-xx" screenshots.
Third issue: that is a little bit more complicated indeed and might not be
easily to fix in contrast to the first ones.
As you may or may not know (at least you will see it) Delphi has something like
a box with verbose compiler messages at the bottom side of the editor.
Now one can double click on the first message and the editor is jumping to that
specific line where an error or a warning occured, setting the background of
that line to red for better visibility.
We fix that issue (or not ;)) and double click on the second entry in that
box... this time the editor should jump to the second error line and so on,
like above, but there are some problems with WINE.
When clicking on the second entry the editor is NOT jumping to the second
erratic line but to the first one and the first entry remains
"activated"/highlighted in that box.
It is possible to override/"fix" that behavior by clicking into that box one
time and then selecting the entry one wants to have a closer look at and THAN
double click on it/in the box.
Well, as that might be possible, it's not very comfortable and not the default
behavior and should be fixed as well. :)
So that are my three points so far, I could not find any other bugs yet. ;)
You will have some screenshots attached both with WINEs (version 0.9.51 with
that little msi patch of truiken) behavior and the one under a natively running
Windows (not on the same boxes, though, but that should not cause any problems)
in the next comment. (By the way, why does Bugzilla allow only one attachment
in the first Bug Commit?)
-Ionic
(The entries in the StringGrid you see there in two of the screenshots are just
plain fiction; neither the names nor the attributes given there correspond to
the reality. (I included this to prevent privacy legality actions.))
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=15377
Summary: 1.1.5 breaks d3d game that worked in 1.1.4
Product: Wine
Version: 1.1.5
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ben.trusty(a)gmail.com
CC: julliard(a)winehq.org
broke both command and conquer & command and conquer: red alert in wine 1.1.5;
both worked in 1.1.4
Regression Testing
d381c7cbf4d463189f479a0b3986f6767aeb8dba is first bad commit
commit d381c7cbf4d463189f479a0b3986f6767aeb8dba
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Fri Sep 19 18:05:36 2008 +0200
Release 1.1.5.
:100644 100644 7a2c61113334222ab571b9cce093dd080fa825bf
982ac735f37215caf4e819c8afb6a8a2f0341585 M ANNOUNCE
:100644 100644 cd289fc7fdb8187487084f08312e3042c1c7cb44
41c2c19075c1b563e1152512ed077b9895bd1f26 M VERSION
:100755 100755 e898943c5e9326274904e3ecc42884b99456e288
ff2c11d3ae4e0afd80c9b62281c510521cef9e87 M configure
--
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=15371
Summary: HDR not rendered correctly (e.g. in Rainbow 6 Vegas)
Product: Wine
Version: 1.1.5
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: normandy(a)web.de
Created an attachment (id=16218)
--> (http://bugs.winehq.org/attachment.cgi?id=16218)
HDR enabled in Rainbow 6 Vegas
Enabling HDR often results in glitches, see image below
--
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=14767
Summary: WGL_SWAP_METHOD_ARB attribute not implemented
Product: Wine
Version: CVS/GIT
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: opengl
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: screwdriver(a)lxnt.info
Created an attachment (id=15283)
--> (http://bugs.winehq.org/attachment.cgi?id=15283)
patch against git head as of 05.08.2008
WGL_SWAP_METHOD_ARB attribute, defined in wgl_pixel_format opengl extension is
not handled.
Attached patch adds trivial handling of this attribute.
This gets rid of fixme messages about unknown/unhandled WGL attributes 0x2007,
0x2028-0x202A.
--
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=13922
Summary: configure script produces misleading warning about
libhal
Product: Wine
Version: 1.0-rc4
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: trivial
Priority: P4
Component: build-env
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: shacklein(a)gmail.com
This is true in 1.0-rc5, but I can't select that as a Version.
The following warning produced by the configure script can be misleading:
configure: libhal development files not found, no dynamic device support.
This warning occurs on Debian Unstable/amd64, where there is no
/usr/lib32/libdbus-1.so by default. Creating a symlink that points to
/usr/lib32/libdbus-1.so.3 fixes the error.
It would be more helpful if the message indicated missing dbus.
--
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=13917
Summary: Supreme Commander won't let me select high fidelity
Product: Wine
Version: 1.0-rc4
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: liquitsnake(a)gmx.net
This game let's me select high fidelity in the options on Windows on the same
hardware. In Wine, I can only choose between Low and Medium.
I think the game determines the available options on the graphics capabilities
that get reported to it. So I don't know if it's really a Wine problem or one
of the Linux Nvidia driver (I use 169.12 on GF8600GT. Even a 6800LE on Windows
allows for high fidelity)
I'm happy to help in case of further questions (like testing what capabilites
the game asks for)
--
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=13705
Summary: keyboard does not work in Trackmania Nations Forever
Product: Wine
Version: 1.0-rc2
Platform: PC-x86-64
URL: http://appdb.winehq.org/objectManager.php?sClass=version
&iId=12137
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: boeser.wolff(a)web.de
Created an attachment (id=13720)
--> (http://bugs.winehq.org/attachment.cgi?id=13720)
stderr from TMNF test run
During a testing run with win 1.0rc2 on Debian lenny/sid (almost all packages
from testing) I found the keyboard is not working:
I cant enter any text inside a game, thus I cant create any accout to test it
further.
Instead the characters entered appear on stderr and are passed to the shell on
exit.
See attachment lines 262-267:
user@host:~/.wine/drive_c/Programme/TmNationsForever$
CFGCCFGasdfsdsdfaasccfadsfsdaddfasdCFfixme:d3d9:Direct3DShaderValidatorCreate9
stub
fixme:d3d:IWineD3DDeviceImpl_EvictManagedResources (0x1622f8) : stub
fixme:dsound:DllCanUnloadNow (void): stub
-bash: CFGCCFGasdfsdsdfaasccfadsfsdaddfasdCF: command not found
--
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=13266
Summary: ArchiCad 11 installer: Crashes after extraction (Java
related?)
Product: Wine
Version: 1.0-rc1
Platform: PC
URL: http://archicad.com/
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kopseng(a)stud.ntnu.no
Created an attachment (id=13111)
--> (http://bugs.winehq.org/attachment.cgi?id=13111)
Output from running AC11-NOR.exe, and Setup.exe manually after extraction
Trying to run the installer for ArchiCad 11, it fails after extraction.
Going into the directory c:\windows\temp\ArchiCad 11, where the files were
extracted, and starting up Setup.exe, if fails within a second with a page
fault.
Before Setup crashes, a "Installing Java Runtime" briefly flashes on screen.
I can't read the output, but it might be Java related, seeing that the Java
Runtime that comes with the demo also crashes (but that might be a whole other
bug report). ArchiCad is java based, so the JRE install is vital.
--
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=12169
Summary: Supreme Commander: Black bar obscuring screen when
fidelity >low
Product: Wine
Version: 0.9.58.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: liquitsnake(a)gmx.net
As soon as the fidelity is set from low to medium, there will be a black bar
obscuring half of the screen (terrain textures, to be to the point)
This seems to be somehow related to shadows. Enabling shadows to either low or
medium settings results in the black bar shrinking from the upper half of the
screen to only obscuring the upper right corner.
--
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.