https://bugs.winehq.org/show_bug.cgi?id=45553
Bug ID: 45553
Summary: the hiarcs program stopped working after the
installation of wine 3.12
Product: Wine
Version: 3.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: winelib
Assignee: wine-bugs(a)winehq.org
Reporter: visconde77(a)yahoo.com.br
Distribution: ---
Created attachment 61974
--> https://bugs.winehq.org/attachment.cgi?id=61974
stop
the hiarcs program stopped working after the installation of wine 3.12
--
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.
https://bugs.winehq.org/show_bug.cgi?id=2082
--- Comment #170 from Saulius K. <saulius2(a)gmail.com> ---
Found some MSDN article called "Redirecting GDI, DirectX, and WPF applications"
[4]. How do devs think, can it bring some simplicity for the situation?
--- quote ---
Mixed DirectX and GDI Windows
The other reasonably common rendering to a top level window involves mixing
DirectX and GDI. There are two forms of "mixing" here, one is perfectly fine,
and the other is problematic.
_The form of mixing that is fine_ is when there is a window tree of the top
level HWND and child HWNDs (and further children, etc), where each individual
HWND is either rendered by DirectX or by GDI. In this situation, the
redirection component of the DWM forms its own "composition tree" where each
node in the tree represents a node or a set of "homogenously rendered nodes" in
the "window tree" rooted at the top level HWND. Rendering occurs by having
each of these render to their own surface, and then compositing this tree of
surfaces to the desktop. Thus, mixed DirectX and GDI rendering works well, so
long as the boundary between them is at least at the child HWND level.
_The form of mixing that _doesn't work well_ is when an application uses
DirectX and GDI to target the same HWND. This has never been a supported
scenario with DirectX, but there have been scenarios where it has happened to
work. Under the DWM, this is much more problematic, because there can be no
guarantee of ordering between the DirectX and the GDI rendering. This is most
troublesome when GDI and DirectX are not only rendering to the same HWND, but
to overlapping areas of the same HWND. As such, this usage pattern is not
supported. Note that there is an alternative that can often work for an
application -- DirectX is capable of handing back a DC to a DirectX surface,
and applications can perform GDI rendering to that DC. From the DWM's
perspective, that DirectX surface remains purely rendered by DirectX, and all
is well.
--- quote ---
[4]
https://blogs.msdn.microsoft.com/greg_schechter/2006/05/03/redirecting-gdi-…
--
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.
https://bugs.winehq.org/show_bug.cgi?id=45058
Bug ID: 45058
Summary: Neverwinter Nights GOG installer failure
Product: Wine
Version: 3.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: bronsonmathews(a)gmail.com
Distribution: ---
GOG version of Neverwinter Nights Diamond Edition installer fails to run.
Looks possibly like a comctl32 issue?
Log here:
https://pastebin.com/
--
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.
https://bugs.winehq.org/show_bug.cgi?id=7284
lsh(a)ccxx.cx changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lsh(a)ccxx.cx
--- Comment #85 from lsh(a)ccxx.cx ---
Bug is present in wine-3.13 (Staging). Regression?
--
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.
https://bugs.winehq.org/show_bug.cgi?id=2082
Jimmy Christensen <jichr86(a)dusted.dk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jichr86(a)dusted.dk
--- Comment #169 from Jimmy Christensen <jichr86(a)dusted.dk> ---
But is also present in version 3.0, tried with Diablo, the intro movies render,
the menu does not (blank screen), if I blindly enter the game, loading screen
and gameplay is displayed.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=8606
spottedowl <spambuster300(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |spambuster300(a)gmail.com
--- Comment #41 from spottedowl <spambuster300(a)gmail.com> ---
Wine 3.0.2 with version 1.7.5.7 of Joint Ops Typhoon Rising still produces the
"Unable to create a network socket" error upon load. If you install from disc
and don't update you can at least run the single player training mode, but
updating the game makes this error appear upon loading the exe.
--
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.