| Age | Commit message (Collapse) | Author |
|---|
|
in multiple Go files like this, but meh.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
becasue when I tried doing it alll at once the program broke in utterly mysterious ways.
|
|
their own checkbox image list. This will be needed to properly handle WM_THEMECHANGED.
|
|
|
|
function because HRESULTs were designed to be extensible in vendor-specific ways.)
|
|
|
|
fixed those.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
http://stackoverflow.com/questions/25462989/why-am-i-getting-wm-mouseactivate-when-i-click-on-my-child-window-i-have-it-cha
|
|
irc.freenode.net/#macdev.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
on: we store the Area's width/height already; no need to get it back out from GTK+ itself.
|
|
issue left in GTK+ Areas...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the need for our focus stuff.
|
|
was handled; implemented this on Windows. It does sledgehammer some edge cases I wanted to avoid, but it also avoids fussing about scrolling and focus and what not.
|
