Module: wine
Branch: master
Commit: aea8d5c11ee42642a77911a76f119e2cd9488f1a
URL: http://source.winehq.org/git/wine.git/?a=commit;h=aea8d5c11ee42642a77911a76…
Author: Henri Verbeet <hverbeet(a)codeweavers.com>
Date: Wed Sep 11 08:47:48 2013 +0200
wined3d: Get rid of the render target / overlay check in wined3d_surface_flip().
The surface needs to be part of a swapchain to be flipped, but that doesn't
have much to do with WINED3DUSAGE_RENDERTARGET. We can just remove the check
here, because ddraw_surface7_Flip() already has the correct check.
---
dlls/wined3d/surface.c | 7 -------
1 files changed, 0 insertions(+), 7 deletions(-)
diff --git a/dlls/wined3d/surface.c b/dlls/wined3d/surface.c
index dbf6fef..87ae02d 100644
--- a/dlls/wined3d/surface.c
+++ b/dlls/wined3d/surface.c
@@ -3706,13 +3706,6 @@ HRESULT CDECL wined3d_surface_flip(struct wined3d_surface *surface, struct wined
return WINEDDERR_NOTFLIPPABLE;
}
- /* Flipping is only supported on render targets and overlays. */
- if (!(surface->resource.usage & (WINED3DUSAGE_RENDERTARGET | WINED3DUSAGE_OVERLAY)))
- {
- WARN("Tried to flip a non-render target, non-overlay surface.\n");
- return WINEDDERR_NOTFLIPPABLE;
- }
-
flip_surface(surface, override);
/* Update overlays if they're visible. */
Module: docs
Branch: master
Commit: 891e03ecb915aecb34b7d797d3d013392c96d4fc
URL: http://source.winehq.org/git/docs.git/?a=commit;h=891e03ecb915aecb34b7d797d…
Author: Frédéric Delanoy <frederic.delanoy(a)gmail.com>
Date: Wed Sep 11 10:29:58 2013 +0200
wineusr: Mention forums.
---
en/wineusr-bugs.sgml | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/en/wineusr-bugs.sgml b/en/wineusr-bugs.sgml
index 931ed6e..e251bdd 100644
--- a/en/wineusr-bugs.sgml
+++ b/en/wineusr-bugs.sgml
@@ -179,8 +179,9 @@
</listitem>
<listitem>
<para>
- Wine <ulink url="http://www.winehq.org/site/forums#ml">mailing
- lists</ulink> may also help, especially <literal>wine-users</literal>. The
+ Wine <ulink url="http://forums.winehq.org/">forums</ulink> and <ulink
+ url="http://www.winehq.org/site/forums">mailing lists</ulink> may also help,
+ especially <literal>wine-users</literal>. The
<literal>wine-devel</literal> list may be appropriate depending on the type of
problem you are experiencing. If you post to <literal>wine-devel</literal> you
should be prepared to do a little work to help diagnose the
Module: docs
Branch: master
Commit: 2b7c66dc429bf25d51462764d1a8f86a128f1402
URL: http://source.winehq.org/git/docs.git/?a=commit;h=2b7c66dc429bf25d51462764d…
Author: Frédéric Delanoy <frederic.delanoy(a)gmail.com>
Date: Wed Sep 11 10:29:57 2013 +0200
wineusr: Assorted formatting & tagging fixes.
---
en/wineusr-bugs.sgml | 17 ++++++++++++-----
1 files changed, 12 insertions(+), 5 deletions(-)
diff --git a/en/wineusr-bugs.sgml b/en/wineusr-bugs.sgml
index 5a66456..931ed6e 100644
--- a/en/wineusr-bugs.sgml
+++ b/en/wineusr-bugs.sgml
@@ -154,8 +154,15 @@
<para>
<ulink url="http://www.freenode.net">Freenode.net</ulink>
hosts an IRC channel for Wine. You can access it by using
- any IRC client such as Xchat. The settings you'll need are:
- server = irc.freenode.net, port = 6667, and channel = #winehq
+ any IRC client such as <application>Xchat</application>. The settings you'll need are:
+ <simplelist type="horiz" columns="2">
+ <member>server</member>
+ <member>irc.freenode.net</member>
+ <member>port</member>
+ <member>6667</member>
+ <member>channel</member>
+ <member>#winehq</member>
+ </simplelist>
</para>
</listitem>
<listitem>
@@ -173,9 +180,9 @@
<listitem>
<para>
Wine <ulink url="http://www.winehq.org/site/forums#ml">mailing
- lists</ulink> may also help, especially wine-users. The
- wine-devel list may be appropriate depending on the type of
- problem you are experiencing. If you post to wine-devel you
+ lists</ulink> may also help, especially <literal>wine-users</literal>. The
+ <literal>wine-devel</literal> list may be appropriate depending on the type of
+ problem you are experiencing. If you post to <literal>wine-devel</literal> you
should be prepared to do a little work to help diagnose the
problem. Read the section below to find out how to debug
the source of your problem.