UI: don't use operators anymore for handling user interface events, but rather

a special UI handler which makes the code clearer. This UI handler is attached
to the region along with other handlers, and also gets a callback when all
handlers for the region are removed to ensure things are properly cleaned up.
This should fix XXX's in the UI code related to events and context switching.

Most of the changes are in interface_handlers.c, which was renamed from
interface_ops.c, to convert operators to the UI handler. UI code notes:
* uiBeginBlock/uiEndBlock/uiFreeBlocks now takes a context argument, this is
  required to properly cancel things like timers or tooltips when the region
  gets removed.
* UI_add_region_handlers will add the region level UI handlers, to be used
  when adding keymap handlers etc. This replaces the UI keymap.
* When the UI code starts a modal interaction (number sliding, text editing,
  opening a menu, ..), it will add an UI handler at the window level which
  will block events.

Windowmanager changes:
* Added an UI handler next to the existing keymap and operator modal handlers.
  It has an event handling and remove callback, and like operator modal handlers
  will remember the area and region if it is registered at the window level.
* Removed the MESSAGE event.
* Operator cancel and UI handler remove callbacks now get the
  window/area/region restored in the context, like the operator modal and UI
  handler event callbacks.
* Regions now receive MOUSEMOVE events for the mouse going outside of the
  region. This was already happening for areas, but UI buttons are at the region
  level so we need it there.

Issues:
* Tooltips and menus stay open when switching to another window, and button
  highlight doesn't work without moving the mouse first when Blender starts up.
  I tried using some events like Q_FIRSTTIME, WINTHAW, but those don't seem to
  arrive..
* Timeline header buttons seem to be moving one pixel or so sometimes when
  interacting with them.
* Seems not due to this commit, but UI and keymap handlers are leaking. It
  seems that handlers are being added to regions in all screens, also in regions
  of areas that are not visible, but these handlers are not removed. Probably
  there should only be handlers in visible regions?

1 files changed, 11 insertions, 5 deletions

diff --git a/source/blender/windowmanager/wm_event_system.h b/source/blender/windowmanager/wm_event_system.h
index 0c37c56778f..61670388879 100644
--- a/source/blender/windowmanager/wm_event_system.h
+++ b/source/blender/windowmanager/wm_event_system.h
@@ -40,15 +40,21 @@ struct ARegion;
 typedef struct wmEventHandler {
 	struct wmEventHandler *next, *prev;
 	
-	int type, flag;	/* type default=0, rest is custom */
+	int type, flag;				/* type default=0, rest is custom */
 	
-	ListBase *keymap;	/* pointer to builtin/custom keymaps */
+	/* keymap handler */
+	ListBase *keymap;			/* pointer to builtin/custom keymaps */
 	
-	rctf boundbox;	/* float, in bContext space (window, area, region) */
-	
-	wmOperator *op;		/* for derived/modal handlers */
+	/* modal operator handler */
+	wmOperator *op;				/* for derived/modal handlers */
 	struct ScrArea *op_area;	/* for derived/modal handlers */
 	struct ARegion *op_region;	/* for derived/modal handlers */
+
+	/* ui handler */
+	wmUIHandlerFunc ui_handle;  		/* callback receiving events */
+	wmUIHandlerRemoveFunc ui_remove;	/* callback when handler is removed */
+	struct ScrArea *ui_area;			/* for derived/modal handlers */
+	struct ARegion *ui_region;			/* for derived/modal handlers */
 	
 } wmEventHandler;