Blender Git Loki

GPencil UI: Further cleaning up the UI to not show the "stroke placement" settings

Since we now show the "Stroke Placement" settings in the toolshelf (where available),
we can now afford to not show it in the properties too. The only exception for this
is the sequencer, where there is no toolshelf we can use.

Fix for error in previous commit: Layouts were not getting deactivated properly

GPencil Layers UI: Rearranging buttons for a nicer flow

Tweaks to RNA for GPencil pointers

Some tweaks to the RNA for Grease Pencil data pointers in an attempt to get
these editable via the Outliner datablocks view. It seems though that pointer
editing there is broken everywhere instead. Nevertheless, these tweaks should
make this handling more correct (i.e. refcounts are used accordingly).

For now, the best way of setting Grease Pencil data on objects, etc. is to do
so using Python

Grease Pencil Drawing: Default to storing on the scene when painting in 3D View

Grease Pencil will now draw on scene-level when drawing in the 3D view,
unless the active object has grease pencil data assigned (i.e. for files
saved in old versions).

The per-object method proved to be far too messy and confusing in practice,
as it was often all too easy to forget which object you had painted with.

While at present, the place where it stores strokes isn't able to be configured
from the UI yet, simply hooking up a Grease Pencil datablock into an Object's
Grease Pencil data slot should work (some tweaks are coming in the following commit
to add support for this)

Grease Pencil Layers UI: Ported properties panel to Python and UI Lists

This commit ports the Grease Pencil properties panel (which displayed the layers info)
to Python, and simplifies the design by using UI Lists instead of listing out the
contents of each layer inline. The resulting design is a lot more compact, and should
also be more easily scannable, especially when you have lots of layers.

For now, I've left all the old C-based layers code alone, but just commented out
in case we need to roll back this commit. So far, all the editors seem to be behaving
correctly, but I may have glossed over some details.

Added operator to move active Grease Pencil layers up and down the list

Added an operator to delete the active Grease Pencil layer

GPencil UI: Use the icons defined in RNA

GPencil RNA: Add icons for the toggle settings

Added "gpencil_data_owner" to context for getting the struct/datablock which references the "gpencil_data" instance

Change order of Grease Pencil drawing tools in the toolshelf

Draw and Erase are now on the same row, while the two line-segment drawing modes
are on the bottom row.

Rename "Stroke Tools" panel to "Edit Strokes"

GPencil Toolshelf Panels - Split into two panels

* Split Grease Pencil toolshelf panels into 2: One for drawing tools, and the
other for the new stroke-editing tools

* Added support for Grease Pencil toolshelf panels in Node Editor. As this gets
added before all the other bits and pieces, this currently becomes the first
tab in the menu (which is not what we want). This will do for now, since I'm not
sure what alternatives to doing it this way exist.

GPencil Toolshelf Panel: Add "drawing settings" to toolshelf

The "Drawing Settings" displayed at the bottom of the Grease Pencil data panel
(Properties Region) is now included in the toolshelf too. These really make more
sense here, as they affect how the tool will behave (while the Properties Region
is more how it gets displayed).

However, we can't fully move over to the toolbar yet, since the VSE still lacks
a toolbar for this. Every other place (View3D, MovieClip, Image) all have their
own toolbars now.

GPencil UI: Experimental "tool palette" pie menu

Double-tapping D brings up a pie menu providing access to many of the different
Grease Pencil drawing and editing tools.

The current implementation is a quick test of how this could work.
* Double-tapping D is the best compromise I managed to find so far which allows
the pie to show, but without getting triggered everytime something else happens
* I've left off one or two tools since they didn't work terribly well,
as they rely on mouse position at time of invocation
* Even now, the drawing tools take a little getting used to (i.e. you must immediately
start drawing once you click. But, once gotten used to, it seems to be ok...

Code cleanup: Moving from custom macro-based loopers to the context-based method

GPencil Context Utility API's now work

To work around the bizarre "active object == NULL" issues when doing context
lookups, we now use the "context-free" direct-access API method for getting
the active Grease Pencil data.

GPencil API - API for getting active GP data without context

Note on current bugs which prevent this from working...