Re: More correctly handle the presence of the default ime inputwindow on Ime open and close
"Aric Stewart" <aric(a)codeweavers.com> wrote:
diff --git a/dlls/imm32/imm.c b/dlls/imm32/imm.c index 4acbde3..f3ed6f9 100644 --- a/dlls/imm32/imm.c +++ b/dlls/imm32/imm.c @@ -190,19 +190,17 @@ static LRESULT ImmInternalSendIMENotify(WPARAM notify, LPARAM lParam)
static void ImmInternalSetOpenStatus(BOOL fOpen) { - TRACE("Setting internal state to %s\n",(fOpen)?"OPEN":"CLOSED"); + TRACE("Setting internal state to %s\n",(fOpen)?"OPEN":"CLOSED");
Wouldn't it be better to change indentation to commonly used 4 spaces instead of a strange mix of 3 and 4 spaces? -- Dmitry.
Good point, resending. thanks, -aric Dmitry Timoshkov wrote:
"Aric Stewart" <aric(a)codeweavers.com> wrote:
diff --git a/dlls/imm32/imm.c b/dlls/imm32/imm.c index 4acbde3..f3ed6f9 100644 --- a/dlls/imm32/imm.c +++ b/dlls/imm32/imm.c @@ -190,19 +190,17 @@ static LRESULT ImmInternalSendIMENotify(WPARAM notify, LPARAM lParam)
static void ImmInternalSetOpenStatus(BOOL fOpen) { - TRACE("Setting internal state to %s\n",(fOpen)?"OPEN":"CLOSED"); + TRACE("Setting internal state to %s\n",(fOpen)?"OPEN":"CLOSED");
Wouldn't it be better to change indentation to commonly used 4 spaces instead of a strange mix of 3 and 4 spaces?
participants (2)
-
Aric Stewart -
Dmitry Timoshkov