Signed-off-by: Jacek Caban jacek@codeweavers.com --- dlls/user32/property.c | 15 ++------------- dlls/win32u/syscall.c | 1 + dlls/win32u/tests/win32u.c | 21 +++++++++++++++++++++ dlls/win32u/win32u.spec | 2 +- dlls/win32u/window.c | 22 ++++++++++++++++++++++ dlls/wow64win/syscall.h | 1 + dlls/wow64win/user.c | 9 +++++++++ include/ntuser.h | 3 +++ 8 files changed, 60 insertions(+), 14 deletions(-)
Any particular reason that 1/5 uses a specfile import, but none of the rest of these functions do?
On 11/8/21 5:45 PM, Zebediah Figura wrote:
Any particular reason that 1/5 uses a specfile import, but none of the rest of these functions do?
Function's signatures don't match on Windows. As mentioned by the comment, Windows accepts only ATOMs. As such, when calling from user32, I think that using user32 names is better.
Thanks,
Jacek