Nice update to xgettext replacement, now finds 608 strings, think this covers all cases...

Will run a complete test case tomorrow, regexes killed me this evening!

git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48513 954f8c5b-7b00-dc11-b283-0030488c597c
Bugfix [#31976] Bone Group Custom color set is not respected when creating an
Action

Custom color set colors were not getting copied over when creating new action
groups. Instead, a "default set" was initialised for use instead.


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48514 954f8c5b-7b00-dc11-b283-0030488c597c
Bugfix [#31834] Cycles materials cannot be manipulated using drivers

Until now, there was never any code for making drivers on materials get
recalculated when their dependencies were changed. However, since changing
material colors with drivers is something that is quite common, a workaround was
introduced to ensure that materials could still be driven (albeit with the
relevant drivers rooted at object level). This worked well enough so far with
traditional materials - though it was sometimes clunky and confusing for some
users - and would have been ok to tide us over until the depsgraph refactor.

The introduction of Cycles changed this, as it has in many other ways. Now that
people use Cycles to render, they'll need to drive the material colors through
the nested nodetree (and other things nested deeply within that). However, this
is much more difficult to generate hacks to create the relevant paths needed to
work around the problem.

== This Commit... ==
* Adds a recursive driver calculation step to the BKE_object_handle_update()
(which gets called whenever the depsgraph has finished tagging object datablocks
for updates), which goes through calculating the drivers attached to the object
(and the materials/nodetrees attached to that). This case gets handled everytime
the object is tagged as needing updates to its "data" (OB_RECALC_DATA)

* When building the depsgraph, every dependency that the drivers there have are
treated as if they were attached to object.data instead. This should trick the
depsgraph into tagging OB_RECALC_DATA to force recalculation of drivers, at the
expense perhaps of modifiers getting recalculated again.

== Todo ==
* The old workarounds noted are still in place (will be commented out in the
next commit). This fix renders at least the material case redundant, although
the textures case still needs a bit more work.

* Check on whether similar hacks can be done for other datablock combinations

* So far, only simple test cases have been tested. There is probably some
performance penalty for heavy setups still (due to need to traverse down all
parts of material/node hierarchy to find things that need updates). If there
really is a problem here, we could try introducing some tags to limit this
traversal (which get added at depsgraph build time).  <--- USER TESTING
NEEDED!!!


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48515 954f8c5b-7b00-dc11-b283-0030488c597c
Followup for r.48515

* Removed material driver creation hack. However, the textures one remains, as
texture eval isn't ready yet
* Shuffled some code


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48516 954f8c5b-7b00-dc11-b283-0030488c597c
Ack! Missed some compiler warnings


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48517 954f8c5b-7b00-dc11-b283-0030488c597c
Bugfix: Fix crashes with empty material slots


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48518 954f8c5b-7b00-dc11-b283-0030488c597c
fix for smoke writing uninitialized values to pointcache, not a big deal since they are ignored on reading.


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48519 954f8c5b-7b00-dc11-b283-0030488c597c
fix for memory leak in BKE_mesh_ensure_navmesh(), it would add 2 navmesh layers, once referencing the other.


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48520 954f8c5b-7b00-dc11-b283-0030488c597c
Check for nullpointers.
The ID of group nodes are not always filled.


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48521 954f8c5b-7b00-dc11-b283-0030488c597c
Style edit (mostly), use """ for docstrings (not ''').

Should also fix the broken py ops tips...

git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48522 954f8c5b-7b00-dc11-b283-0030488c597c
Optimized the area of interest of the lensdistortion node.
This will have faster feedback to the user, as lensdistortion is mostly
a node that is located at the end of a composite


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48523 954f8c5b-7b00-dc11-b283-0030488c597c
fix (actually nasty workaround), for groups incorrectly drawing in the object panel when the blend file has naming collisions with library data.

also minor style cleanup in bpy_rna.c


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48524 954f8c5b-7b00-dc11-b283-0030488c597c
removing libfribidi.dll, no libs in our source dirs.


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48529 954f8c5b-7b00-dc11-b283-0030488c597c
rename module to something less generic.


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48530 954f8c5b-7b00-dc11-b283-0030488c597c
Fix [#31977] Export Animated Mesh, terminate baking in fluid-sim

* Elbeem exporter code now overrides user settings to No Slip in case the object is animated;
* UI of fluid obstacles now disables slip settings when export animated is enabled;
* Added in this later option's tooltip a mention that it enforces No Slip!

git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48531 954f8c5b-7b00-dc11-b283-0030488c597c
Minor edits.

git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48534 954f8c5b-7b00-dc11-b283-0030488c597c
More exception words to the ui dico... :/

git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48535 954f8c5b-7b00-dc11-b283-0030488c597c
Fix for the "black F-Curves" bug on undo
(From personal stash of bugs - since early 2.5 versions)

F-Curve colors get applied only on Graph Editor "refresh()". In some cases, undo
was reverting back to a state where the colors had not yet been set. In these
cases, there would be no refresh() after that undo (until expanding a channel or
some other similar action), resulting in "black F-Curves" appearing. So, now we
force such an update after undo to ensure that the curves never display black.

(Noticed while investigating another bug for Mango related to
CLIP_OT_constraint_to_fcurve not sending notifiers required when new F-Curves
are added)


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48536 954f8c5b-7b00-dc11-b283-0030488c597c
dont display image sequences outside the frame range in the 3D viewport.


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48537 954f8c5b-7b00-dc11-b283-0030488c597c
image sequence - apply cyclic option AFTER the image offset,
there was no way to properly loop on a sequence of images that didnt start frame 1.


git-svn-id: https://svn.blender.org/svnroot/bf-blender/trunk/blender@48539 954f8c5b-7b00-dc11-b283-0030488c597c