Re: [2/2] user32: make wineserver calls to get and set window droptargets [try 2]
Damjan Jovanovic <damjan.jov(a)gmail.com> writes:
Changelog: * user32: make wineserver calls to get and set window droptargets
Get and set the window drop targets from user32.dll, and not ole32.dll like in try 1.
That's not much better, you are still having ole32 do server calls, only hidden behind a Wine-specific export. You should be able to do this with only standard user32 APIs, or you need to make a very convincing case that it's impossible without private exports. -- Alexandre Julliard julliard(a)winehq.org
On Mon, Feb 8, 2010 at 4:19 PM, Alexandre Julliard <julliard(a)winehq.org> wrote:
Damjan Jovanovic <damjan.jov(a)gmail.com> writes:
Changelog: * user32: make wineserver calls to get and set window droptargets
Get and set the window drop targets from user32.dll, and not ole32.dll like in try 1.
That's not much better, you are still having ole32 do server calls, only hidden behind a Wine-specific export. You should be able to do this with only standard user32 APIs, or you need to make a very convincing case that it's impossible without private exports.
About these "standard user32 APIs"... Are you referring to calling DefWndProc() with custom messages, somehow using the undocumented WM_DROPOBJECT family of messages, doing what Windows does (which is RPC into RPCSS.EXE according to Rob Shearman) or something I haven't thought of?
-- Alexandre Julliard julliard(a)winehq.org
Thank you Damjan Jovanovic
Damjan Jovanovic <damjan.jov(a)gmail.com> writes:
About these "standard user32 APIs"...
Are you referring to calling DefWndProc() with custom messages, somehow using the undocumented WM_DROPOBJECT family of messages, doing what Windows does (which is RPC into RPCSS.EXE according to Rob Shearman) or something I haven't thought of?
Whatever Windows does, unless there are good reasons for not doing it that way. -- Alexandre Julliard julliard(a)winehq.org
participants (2)
-
Alexandre Julliard -
Damjan Jovanovic