summaryrefslogtreecommitdiffstats
path: root/win/tkWinDialog.c
diff options
context:
space:
mode:
authorjan.nijtmans <nijtmans@users.sourceforge.net>2016-05-12 09:43:05 (GMT)
committerjan.nijtmans <nijtmans@users.sourceforge.net>2016-05-12 09:43:05 (GMT)
commit7fb5c8f5101ffff084ff8d1f2516a6c65b3abe92 (patch)
tree5da5917b13cd0eca8869ec2b536fe5e0589a3f1c /win/tkWinDialog.c
parentab67479aa5db8b003ff4f7f1adcd73fac573e3eb (diff)
downloadtk-7fb5c8f5101ffff084ff8d1f2516a6c65b3abe92.zip
tk-7fb5c8f5101ffff084ff8d1f2516a6c65b3abe92.tar.gz
tk-7fb5c8f5101ffff084ff8d1f2516a6c65b3abe92.tar.bz2
PeekMessageA -> PeekMessage
Diffstat (limited to 'win/tkWinDialog.c')
-rw-r--r--win/tkWinDialog.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/win/tkWinDialog.c b/win/tkWinDialog.c
index 64b3eac..a7d8c7d 100644
--- a/win/tkWinDialog.c
+++ b/win/tkWinDialog.c
@@ -679,7 +679,7 @@ static void LoadShellProcs()
* poll the message queue consuming WM_LBUTTONUP messages.
* On seeing a WM_LBUTTONDOWN message, it would exit early, since the user
* must be doing something new. However this early exit does not work
- * on Vista and later because the Windows sends both BUTTONDOWN and
+ * on Vista and later because the Windows sends both BUTTONDOWN and
* BUTTONUP after the DBLCLICK instead of just BUTTONUP as on XP.
* Rather than try and figure out version specific sequences, we
* ignore all mouse events in that interval.
@@ -704,7 +704,7 @@ EatSpuriousMessageBugFix(void)
DWORD nTime = GetTickCount() + 250;
while (GetTickCount() < nTime) {
- PeekMessageA(&msg, 0, WM_MOUSEFIRST, WM_MOUSELAST, PM_REMOVE);
+ PeekMessage(&msg, 0, WM_MOUSEFIRST, WM_MOUSELAST, PM_REMOVE);
}
}