Re: user32: Remove leftover HINSTANCE16 code from LoadCursor/LoadIcon.
Michael Stefaniuc <mstefani(a)redhat.de> writes:
The Wine code doesn't seem to pass a 16bit hinstance to LoadCursor/LoadIcon; the only calls to those functions from 16bit code use a 0 hinstance which is fine.
16-bit instances can come from 32-bit calls too, if we are dealing with a 16-bit window. -- Alexandre Julliard julliard(a)winehq.org
Alexandre Julliard wrote:
Michael Stefaniuc <mstefani(a)redhat.de> writes:
The Wine code doesn't seem to pass a 16bit hinstance to LoadCursor/LoadIcon; the only calls to those functions from 16bit code use a 0 hinstance which is fine.
16-bit instances can come from 32-bit calls too, if we are dealing with a 16-bit window. Hehehe, that was just a "probe patch" to describe the problem. Will you accept the standard if((ULONG_PTR)hinstance >> 16) patch or do you want to fix the problem yourself? ;)
bye michael
Michael Stefaniuc <mstefani(a)redhat.com> writes:
Alexandre Julliard wrote:
Michael Stefaniuc <mstefani(a)redhat.de> writes:
The Wine code doesn't seem to pass a 16bit hinstance to LoadCursor/LoadIcon; the only calls to those functions from 16bit code use a 0 hinstance which is fine.
16-bit instances can come from 32-bit calls too, if we are dealing with a 16-bit window. Hehehe, that was just a "probe patch" to describe the problem. Will you accept the standard if((ULONG_PTR)hinstance >> 16) patch or do you want to fix the problem yourself? ;)
The standard fix is fine. -- Alexandre Julliard julliard(a)winehq.org
participants (2)
-
Alexandre Julliard -
Michael Stefaniuc