| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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.
|
|
be changing AreaHandler.Key()... again...
|
|
|
|
for parity with the GTK+ and (next commit) Mac OS X files.
|
|
|
|
|
|
|
|
|
|
|
|
OnSelected() event.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the GTK+ backend.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the re-enabling window order one...
|
