Re: [1/6] internal cursor / icon memory layout change
"H. Verbeet" <hverbeet(a)gmail.com> writes:
This patch adds an header with animation info (number of frames, delay between frames) to the front of the internal cursor / icon memory layout, in order to support animated mouse cursors.
That's quite ugly, and it will break any app that depends on the cursor format, which is the only reason we are storing them in a memory block in the first place. -- Alexandre Julliard julliard(a)winehq.org
On 19/04/06, Alexandre Julliard <julliard(a)winehq.org> wrote:
That's quite ugly, and it will break any app that depends on the cursor format, which is the only reason we are storing them in a memory block in the first place. How is that supposed to work? Calling GlobalLock16 or GlobalLock on a cursor handle doesn't seem to work very well on win2k.
Anyway, any suggestions on how to implement this in a cleaner way?
"H. Verbeet" <hverbeet(a)gmail.com> writes:
How is that supposed to work? Calling GlobalLock16 or GlobalLock on a cursor handle doesn't seem to work very well on win2k.
No, it's a Win16 thing. What we need is to make cursors and icons into real user handles, and then we can store anything we like in them. Then when passing handles to 16-bit code we need to rebuild a global memory structure in the right format. -- Alexandre Julliard julliard(a)winehq.org
participants (2)
-
Alexandre Julliard -
H. Verbeet