Hi, I noticed that wine always uses it's own mouse cursor image looking like the standard windows cursor. Is there a reason why the X server mouse cursor isn't used?
It's only a minor cosmetic issue, but i have wondered what the reason for this is and if it can be fixed.
Cheers, Stefan
On Tue, 09 May 2006 13:49:53 +0200, Stefan Dösinger wrote:
I noticed that wine always uses it's own mouse cursor image looking like the standard windows cursor. Is there a reason why the X server mouse cursor isn't used?
Doubtful ... I imagine the reason is that apps rely on the Win32 cursor API doing what they expect, and making Wine lie about certain cursors would be a bit awkward. Why not see if it can be easily implemented?
thanks -mike
On Thursday 11 May 2006 15:53, Mike Hearn wrote:
On Tue, 09 May 2006 13:49:53 +0200, Stefan Dösinger wrote:
I noticed that wine always uses it's own mouse cursor image looking like the standard windows cursor. Is there a reason why the X server mouse cursor isn't used?
Doubtful ... I imagine the reason is that apps rely on the Win32 cursor API doing what they expect, and making Wine lie about certain cursors would be a bit awkward. Why not see if it can be easily implemented?
Lying is one thing, another thing is that there might be some apps that actually read the cursor, modify the bitmap and use that modified bitmap for a new cursor. In that case we'd better make sure that we actually give the app the real image.
Color X11 cursors shouldn't be a big deal since even in win95 you had color cursors, albeit with one bit alpha if memory serves me right.
So methinks as long as the app can retrieve a real in-use cursor bitmap, that'd be good enough. Then Wine would just need to use these X default cursors as its own defaults, rather then the stock defaults that come with Wine.
Does Wine support color cursors at all on the API side? As that might be a thing to support first, before we start talking about color X cursors.
Cheers, Kuba
On 12/05/06, Kuba Ober kuba@mareimbrium.org wrote:
Lying is one thing, another thing is that there might be some apps that actually read the cursor, modify the bitmap and use that modified bitmap for a new cursor. In that case we'd better make sure that we actually give the app the real image.
Color X11 cursors shouldn't be a big deal since even in win95 you had color cursors, albeit with one bit alpha if memory serves me right.
So methinks as long as the app can retrieve a real in-use cursor bitmap, that'd be good enough. Then Wine would just need to use these X default cursors as its own defaults, rather then the stock defaults that come with Wine.
Does Wine support color cursors at all on the API side? As that might be a thing to support first, before we start talking about color X cursors.
API wise, yes. Note that modifying the cursor is only supposed to work with 16-bits applications, which can call GlobalLock16 on the cursor handle. Supporting color or animated cursors on the x11drv side isn't terribly hard, but at least in the case of animated cursors we need to store extra information in the cursor, which isn't compatible with the way some 16-bits applications use the cursor.
-
H. Verbeet -
Kuba Ober -
Mike Hearn -
Stefan Dösinger