interesting
/
andlabs-ui
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed Areas on Windows no longer obeying click count rules after adding the WM_ACTIVATE handler.

This commit is contained in:
Pietro Gagliardi 2014-05-25 14:34:19 -04:00
parent d6e7eda29c
commit e7327f2378
1 changed files with 1 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
area_windows.go
View File

@ -626,11 +626,9 @@ func areaWndProc(s *sysData) func(hwnd _HWND, uMsg uint32, wParam _WPARAM, lPara
case _WM_ACTIVATE: case _WM_ACTIVATE:
// don't keep the double-click timer running if the user switched programs in between clicks // don't keep the double-click timer running if the user switched programs in between clicks
s.clickCounter.reset() s.clickCounter.reset()
// MSDN says this message will be sent alongside WM_MOUSEACTIVATE, but we'll reset there too, just in case
return 0 return 0
case _WM_MOUSEACTIVATE: case _WM_MOUSEACTIVATE:
// don't keep the double-click timer running if the user switched programs in between clicks // this happens on every mouse click (apparently), so DON'T reset the click counter, otherwise it will always be reset (not an issue, as MSDN says WM_ACTIVATE is sent alongside WM_MOUSEACTIVATE when necessary)
s.clickCounter.reset()
// transfer keyboard focus to our Area on an activating click // transfer keyboard focus to our Area on an activating click
// (see http://www.catch22.net/tuts/custom-controls) // (see http://www.catch22.net/tuts/custom-controls)
r1, _, err := _setFocus.Call(uintptr(s.hwnd)) r1, _, err := _setFocus.Call(uintptr(s.hwnd))