summaryrefslogtreecommitdiff
path: root/area_windows.go
diff options
context:
space:
mode:
authorPietro Gagliardi <[email protected]>2014-06-06 01:49:23 -0400
committerPietro Gagliardi <[email protected]>2014-06-06 01:49:23 -0400
commit4856790299cf531b874a4e1b835017b0ca9abd03 (patch)
tree6dc89652c64b77096918447a7687314f49498b68 /area_windows.go
parent00ec85dee69130ac4294e71be45470324244324c (diff)
Fixed the standard window class focus behavior on Windows from the previous commit to work. Also updated the SetFocus() call in area_windows.go to boot and removed the relevant TODO after checking both wine and Windows XP work fine.
Diffstat (limited to 'area_windows.go')
-rw-r--r--area_windows.go8
1 files changed, 3 insertions, 5 deletions
diff --git a/area_windows.go b/area_windows.go
index 492595c..344f43f 100644
--- a/area_windows.go
+++ b/area_windows.go
@@ -625,11 +625,9 @@ func areaWndProc(hwnd _HWND, uMsg uint32, wParam _WPARAM, lParam _LPARAM) _LRESU
// 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)
// transfer keyboard focus to our Area on an activating click
// (see http://www.catch22.net/tuts/custom-controls)
- r1, _, err := _setFocus.Call(uintptr(s.hwnd))
- if r1 == 0 { // failure
- panic(fmt.Errorf("error giving Area keyboard focus: %v", err))
- return _MA_ACTIVATE // TODO eat the click?
- }
+ // don't bother checking SetFocus()'s error; see http://stackoverflow.com/questions/24073695/winapi-can-setfocus-return-null-without-an-error-because-thats-what-im-see/24074912#24074912
+ _setFocus.Call(uintptr(s.hwnd))
+// return _MA_ACTIVATE // TODO eat the click?
return defWindowProc(hwnd, uMsg, wParam, lParam)
case _WM_MOUSEMOVE:
areaMouseEvent(s, 0, false, wParam, lParam)