Re: [PATCH v4 0/6] MR2598: imm32: Move IME UI window proc to the default implementation.

[Jacek Caban (＠jacek)]

On Fri Apr  7 14:53:00 2023 +0000, Rémi Bernon wrote:
> > I'm not sure what you mean by very integrated with win32u. Exposing
>
> builtin IMEs as "normal" IMEs is not affected by changes that I suggest.
> For driver interface, it would just replace one driver entry by another.
> I think I was confused by the idea of adding win32u specific interface
> for the callbacks. I'll consider doing this, as I think it also make
> sense to pass NtUserNotifyIMEStatus calls.
> I'm curious then, is there any advantage of using `NtUserMessageCall` vs
> `NtUserCallOneParam` or one of the other flavor? `NtUserMessageCall`
> takes a hwnd as first parameter, it feels a bit wrong to use an HIMC there.

I'd expect that `NtUserMessageCall` would be a bit nicer for wow64, because it may just pass through arguments like `NtUserSpyGetMsgName`, but yeah, handle type mismatch is not that nice.