http://bugs.winehq.org/show_bug.cgi?id=10701
Summary: Renegade 64 RAM viewer fonts are too small.
Product: Wine
Version: 0.9.50.
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: wine-gdi-(printing)
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: echidnaman(a)gmail.com
Created an attachment (id=9535)
--> (http://bugs.winehq.org/attachment.cgi?id=9535)
Renegade 64's RAM viewer.
Renegade 64 has this nice RAM viewer that views the RAM of whatever emulator
R64 happens to be attached to.
Thing is, that the font used to render the addresses and their data are a tad
too small. The application seems to be programmed with one font size in mind,
and has no tolerance for fonts being a size their not supposed to.
Since the separators separating the RAM addresses are fixed, the characters
display over the separators rendering them useless. This also makes it display
too much information before a line break. I've included a picture with the
problem.
There is one fixme that also seems somewhat important:
fixme:font:WineEngCreateFontInstance Untranslated charset 255
--
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=609
Bug 609 depends on bug 1163, which changed state.
Bug 1163 Summary: Accelerator underscore appears in the wrong place for Hebrew menus
http://bugs.winehq.org/show_bug.cgi?id=1163
What |Old Value |New Value
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |ABANDONED
--
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=9210
--- Comment #63 from Artem S. Tashkinov <t.artem(a)mailcity.com> 2013-05-15 13:06:12 CDT ---
(In reply to comment #62)
>
> That's a separate issue, you can open a new bug report for that if you want
> (and installing native d3dcompiler e.g. via "winetricks d3dx9_36" should
> workaround it).
It doesn't make a lot of sense until this bug report is not 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=15342
Summary: Black & White does not exit well - crashes
Product: Wine
Version: 1.1.5
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: normandy(a)web.de
Created an attachment (id=16165)
--> (http://bugs.winehq.org/attachment.cgi?id=16165)
Crash log eine 1.1.5, exiting b&w
Crash log of exiting Black & White 1.3 on Wine 1.1.5
--
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=33508
Bug #: 33508
Summary: Spotify won't install
Product: Wine
Version: unspecified
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dmn2004404(a)gmail.com
Classification: Unclassified
Spotify won't install; says "Please install Spotify using a normal account
instead of an Administrator account."
--
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=9210
Matteo Bruni <matteo.mystral(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matteo.mystral(a)gmail.com
--- Comment #62 from Matteo Bruni <matteo.mystral(a)gmail.com> 2013-05-15 08:46:45 CDT ---
(In reply to comment #61)
> This is what I see in console:
>
> fixme:win:EnumDisplayDevicesW ((null),0,0x32d2e8,0x00000000), stub!
> fixme:hlsl_parser:hlsl_parse Check for valued return on void function.
> fixme:hlsl_parser:hlsl_parse Implicit conversion to the return type if needed,
> error out if conversion not possible.
> err:d3dcompiler:compile_shader HLSL shader parsing failed.
>
> P.S. The previous error message in text:
>
> "C:\Program Files\Futuremark\3dMark06\data\timeline\loading\proxycon_in.txt:
> D3DXCompileShader failed: Invalid data (D3DXERR_INVALIDDATA)"
That's a separate issue, you can open a new bug report for that if you want
(and installing native d3dcompiler e.g. via "winetricks d3dx9_36" should
workaround it).
--
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=33062
Bug #: 33062
Summary: wined3d can't handle surfaces created off-screen in
application memory
Product: Wine
Version: 1.5.24
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andy(a)positality.com
Classification: Unclassified
Created attachment 43706
--> http://bugs.winehq.org/attachment.cgi?id=43706
Start of "wine <app.exe>" log
Target application: ICR Touch
Application brief: Commercial EPOS software for Windows x86
Interesting feature: uses DirectX calls for skinned UI generation.
Looking at the attached log you will see the main error:
"wined3d_surface_getdc Not supported on surfaces with application-provided
memory"
This error is from dlls/wined3d/surface.c
I have spoken to the programmers an they state that their program creates
off-screen surfaces by default. However, if the original Create Surface request
fails their program will fall back to storing surfaces in graphics memory.
If wined3d_surface_getdc cannot (or does not yet) support off-screen surfaces
shouldn't the creation code (wined3d_surface_create?) also return an error
(e.g. check for SFLAG_USERPTR.)
Apologies if I've missed something obvious, my knowledge of DirectX is a little
rusty! I did post on the forums first.
Best Regards,
Andy
--
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.