http://bugs.winehq.org/show_bug.cgi?id=6971
--- Comment #301 from Forest Hale <lordhavoc(a)ghdigital.com> 2009-12-10 11:30:37 ---
(In reply to comment #299)
> (In reply to comment #297)
> If you so want to have DGA mouse - why don't you actually look at what it is,
> how it works, and if it meats the DInput requirements? If it's freezing pointer
> in place - it's automatically won't work for Wine. that mode already works just
> fine. It's the non-exclusive background coop level that's needed by soo many
> apps that doesn't work.
Actually I was saying that DGA mouse freezes the mouse pointer but it can still
be forcefully warped by wine, to mimic normal movement and interact with other
applications - but it disables mouse acceleration in doing so, so such behavior
is only acceptable when the active window has cooperative dinput active, in all
other situations the DGA mouse grab must be released and normal mouse movement
used.
To the user the only difference between having a cooperative dinput window
active and having a normal window active, is that mouse acceleration changes,
and there might be a very slight lag (1 refresh).
All normal application interaction would be preserved.
> Also you seems to totally ignore what I said here numerous times - warping
> mouse is out of the question period end of story. You can not make all
> applications work this way. You will fix one type and break another type.
I did say that DGA support is necessary, I only brought up the "hidden mouse"
fallback (where warping is required and the pointer MUST be hidden) as a
possible fallback that has many undesirable side effects, I recommended against
using such a method if at all possible, because it is not robust at all.
It was only in a summary of possible solutions, and noted as having many
problems.
Where as DGA + mouse warping to mimic real movement would be at least somewhat
robust.
> The best example are all Quake 2+ engine based games that use dinput (Half-Life
> even tho based on Q2 engine doesn't use dinput at all). These games incorrectly
> acquire mouse in game mode as non-exclusive background coop. If you start
> warping mouse in this coop mode you'll break all programs that show system
> cursor in the menu for example.
You are clearly not understanding what I am talking about then.
This cooperative mode using DGA would ALTER the mouse movement behavior
(because wine is really doing the movement), but not disable it, it would still
be able to interact with all normal applications even while the cooperative app
is focused - but as soon as the app is defocused it would return to normal
movement to restore expected behavior (mouse acceleration).
> XInput2 does exactly what Wine needs and that's what Wine will use to fix this
> bug no matter if you like it or not. This means you'll be getting XOrg 7.5
> sooner then you wanted.
I look forward to seeing an XInput2 solution.
However users will continue this discussion until everyone is running xorg 7.5
- and I do not expect that to happen for years, there are still people running
debian stable and expecting wine to work.
--
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=4264
Juan Lang <juan_lang(a)yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|winex11.drv |-unknown
Summary|the 4th coming runs but |the 4th coming refuses to
|deadlocks after a few |install, complain about
|seconds (and mouse is |incorrect registry
|frozen all along) |permissions
--- Comment #9 from Juan Lang <juan_lang(a)yahoo.com> 2009-12-10 11:02:10 ---
Changing summary and changing component to unknown. The crypt32 crash escaped
my attention before, but it's an easy fix. I've sent a patch for it:
http://www.winehq.org/pipermail/wine-patches/2009-December/082541.html
--
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=20974
Summary: Setting drive as Local disk in winecfg does not work
Product: Wine
Version: 1.1.34
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gore(a)projectpontiac.com
In winecfg, setting a drive as "Local disk" does not work.
For example:
- I have a drive called X:\ that resides at ~/.wine/drive_x
- ~/ is a network share that gets auto-mounted from the server when I log in
- I use winecfg to set X:\ to a "Local disk" (under the "Show Advanced"
parameters of the "Drives" tab)
- Windows applications still see X:\ as a Network share
This prevents certain applications from installing. For example, Photoshop CS2,
a Platinum-level application, refuses to install to a network share.
This can be repeated easily by trying to install the Photoshop CS2 trial onto a
drive that is hosted on a network share.
http://download.adobe.com/pub/adobe/photoshop/win/cs2/Photoshop_CS2_tryout.…
So far I've seen this behaviour in Wine version 1.1.28, 1.1.32 and 1.1.34. I
did not try any other versions.
--
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=6971
--- Comment #300 from Warren Dumortier <nwarrenfl(a)gmail.com> 2009-12-10 06:45:25 ---
I'm very happy to see this bug is being discusses to find a solution, however i
have a question, not really important to post in this bur report, but i ask! ;)
Vitaliy Margolen: Do you already have a prototype using XInput 2 or not? But if
you have something beginning to work i would really like to test it out.
--
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=9087
Vitaliy Margolen <vitaliy(a)kievinfo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
--- Comment #25 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2009-12-09 22:19:05 ---
> I wonder why it is so difficult to revert a buggy patch if it is clearly
> identified!
Because the patch is not buggy. DInput has tests that validate this change was
correct.
What happened is this change uncovered another bug somewhere else (d3d/dsound)?
And that's where you should be concentrating.
Confirming per comment 23.
--
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=6971
--- Comment #299 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2009-12-09 22:13:11 ---
(In reply to comment #297)
If you so want to have DGA mouse - why don't you actually look at what it is,
how it works, and if it meats the DInput requirements? If it's freezing pointer
in place - it's automatically won't work for Wine. that mode already works just
fine. It's the non-exclusive background coop level that's needed by soo many
apps that doesn't work.
Also you seems to totally ignore what I said here numerous times - warping
mouse is out of the question period end of story. You can not make all
applications work this way. You will fix one type and break another type.
The best example are all Quake 2+ engine based games that use dinput (Half-Life
even tho based on Q2 engine doesn't use dinput at all). These games incorrectly
acquire mouse in game mode as non-exclusive background coop. If you start
warping mouse in this coop mode you'll break all programs that show system
cursor in the menu for example.
XInput2 does exactly what Wine needs and that's what Wine will use to fix this
bug no matter if you like it or not. This means you'll be getting XOrg 7.5
sooner then you wanted.
--
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=20973
Summary: Windows Live Essentials installer fails
Product: Wine
Version: 1.1.34
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: leighmanthegreat(a)hotmail.com
Created an attachment (id=25139)
--> (http://bugs.winehq.org/attachment.cgi?id=25139)
terminal output
Both wlsetup-web.exe and wlsetup-all.exe available at http://download.live.com/
exit silently.
Terminal output attached.
--
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=6971
Vincent <weber.vincent(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |weber.vincent(a)gmail.com
--- Comment #298 from Vincent <weber.vincent(a)gmail.com> 2009-12-09 19:13:14 ---
I once had this very strange bug with Doom3 on Windows XP (not Wine). From that
very bug I came to understand how Windows XP handles the mouse in FPS games:
It keeps track of the position of the mouse cursor but simplay doesn't display
it and reads out the movement of the mouse too.
So when I played doom, the mouse cursor was displayed. When I moved my mouse to
the right, the camera turned right. When I turn it left, the camera turned
left, etc, etc.. When the mouse hit the side of the screen, the camera kept
going in the direction I moved the mouse.
So... Mouse movement used by DirectInput and also by whatever handles the
cursor, but the cursor just isn't displayed and can't focus...
I am not an experienced programmer but this should be extremely easy to
implement correctly, in a non ugly manner...
--
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=9087
--- Comment #24 from Klaus Ethgen <Klaus+wine(a)Ethgen.de> 2009-12-09 14:59:09 ---
Yes, the problem still exists. Even with newer versions.
I wonder why it is so difficult to revert a buggy patch if it is clearly
identified!
However, some people seems to not see the problem. Might it be that the problem
only occurs on window managers which have no desktop window? Might it be that
this GetDesktopWindow() give a undefined value back or something like that?
Please, please, please, please revert this buggy patch which raised this
problem!
--
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=8394
Juan Lang <juan_lang(a)yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #8 from Juan Lang <juan_lang(a)yahoo.com> 2009-12-09 14:46:07 ---
Reported 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.