Blender Git Loki

Merge branch 'master' into wiggly-widgets

Complete shaded arrow widget code. It will need sorting if keep the
shading.

WIP redesign of the system. Nothing functional (not even manipulator).

There is first code for display of an arrow widget. The manipulator will
use those when they are ready.

Basically the manipulator is now a WidgetGroup. WidgetGroups are a new entity and
they manage a group of related widgets. They should be responsible for state update,
drawing and polling of their widgets and can be bound to specific rules.

There is a big design plan on a whiteboard beside me, it will take a few
big commits still to take shape though. One thing at a time, I am first making
reusable arrow widgets that will allow us replace the translate widgets properly.

There are a few reusable widgets planned, more to come later.

Dragging the light handle will now point the lamp to the point in 3D
where user is dragging over.

Merge branch 'master' into wiggly-widgets

Logic for light position operator.

WIP, operator to tweak the lamp "focus", driven through widgets.

Lamp widget:

* Make a lamp widget design for the active lamp.
* Fix some handler errors for widgets + autoupdate for different widget
handles.

Placeholder widget code for spotlamps

Merge branch 'master' into wiggly-widgets

Move widget drawing at a higher level - try drawing on top of rendering
too.

Rationale - widgets might be useful to have even on rendered scenes -
we'll have to see about how this will work

Also use area initialization code to register region specific widgets once.

lala

Merge branch 'master' into wiggly-widgets

Fix release comfirm for central widget in transform operator

Fixes to highlight code, now widgetmaps remember last active widget and
reset accordingly.

Highlighting for manipulator widget.

This should use an "active" system, similar to buttons to detect if last
widget has changed and act accordingly. Currently, when the active
widget changes, there is no change in highlights.

Tidy up the widget API, only do 3d intersection on widgetmaps that
support it (determined during creation)

Widget API:

Code that handles 3D object intersection via GPU selection. We might
want to use raycasting here, but leaving that for when we have it.

Manipulator code now uses this API to do intersection testing

Refactoring of manipulator code to use selection evaluation and codes
that can be shared with other widgets.

WIP code reshuffling for widgets

Manipulator now uses the widget system (no operators used).

Widgets use a similar notification system as operators. It might be
worth using WM_BREAK messages like the rest of the handlers. For now
this should do.