Age | Commit message (Collapse) | Author |
|
merged)
|
|
DopeSheet/Action Editor Channel menus were not working properly
They were not allowing users to choose which setting they affected, which
resulted in "protect" (i.e. the same setting as the editability toggle handles)
always being used.
Also, set hidden flags on a few internally used properties here...
|
|
were not merged due to complex differences)
|
|
|
|
or Link Object Data methods
- Don't crash if there's any fcurves created for sequencer but no sequencer itself
- Don't copy sequencer's fcurves when copy new scene with linking data/objects method
|
|
This commit allows you to set the RGB <-> XYZ axis colours used for things like
the mini axis indicator, grid axis indicators, manipulators, transform
constraint indicators, F-Curves (when using XYZ to RGB colouring option), and
perhaps something else I've missed. Previously, these places all used hardcoded
defines (220 * i/j/k), but the readability of these colours was often quite
poor, especially when used with certain themes.
The settings for these colours can be found under the "User Interface" section
of the themes (i.e. same set of colours is used across editors). I could have
made these per editor, but since it's unlikely that these will need to be too
different across editors in practice (+ being easier to version patch), they are
stored under the UI section.
|
|
KKEY
Previously this would happen silently, so users may not have noticed that these
had been added. Let's see how this goes before seeing if a hotkey change is
needed to prevent even more errors.
|
|
hair_velocity_smoothing()
and a unlikely NULL pointer dereference in unlink_material_cb().
|
|
Use the "Selected" color instead of the "Active" color when the group has active
status. This should help make the text just a little more legible, though in
some cases it still might not be enough.
|
|
|
|
|
|
|
|
few others), and another bunch of UI messages tweaks/fixes, as well as some BKE_report()<->BKE_reportf()...
|
|
|
|
|
|
|
|
This was caused by the x^n labels being far too large. Also, replaced old string
functions with "safer" versions
|
|
|
|
|
|
with errors
This filtering option is useful when rigging and you want to figure out if any
of your drivers are not functioning, and/or which one(s) are not, so that you
can go through fixing them. It saves you from having to check on each one
individually, or going into the console to try to infer which ones are not
working.
|
|
had a typo too.
|
|
of warnings before committing)
|
|
|
|
commit.
|
|
from selected objects and bones
|
|
|
|
transform_conversions.c), so better leave it for now, at least with r50836 mask datablocks display in the dope sheet by default now.
|
|
can be edited in the dope sheet. (was cause of masks mysteriously not showing in the dope sheet, making masks fake user by default made this more common an issue)
|
|
or good to keep for completeness. quieted some warnings and add flags -Wmissing-include-dirs and -Wno-div-by-zero to cmake/gcc
|
|
|
|
|
|
|
|
C with gcc.
helps for finding unused functions and making functions static, also did some minor code cleanup.
|
|
have been removed by accident as code has been updated.
|
|
rasterizer.
|
|
checked it for NULL after.
also made it more clear that some areas assume the pointer isnt null (remove redundant NULL checks).
|
|
types to the end of the switch statement when evaluating metaballs.
|
|
BKE_utildefines is now unused but keep incase we want to add defines there later.
|
|
|
|
summery wasn't checking fcurve types.
|
|
|
|
our naming convention.
|
|
Summer of Code against trunk revision 50064.
Note: The new flag LIB_LOAD_ASYNC in the GE conflicted with trunks new LIB_LOAD_SCRIPTS, so I changed the value of ASYNC. So, heads up if these values has been saved in any .blend files!
Once again (see last merge note) it seems like node_draw.c had a bunch of wierd conflicts that make it look like it missed a merge or update. Not sure what is going on with that file.
Other parts of the merge had some difficulty resolving proper bracket nesting in places where it seems like the merge should have gone smoothly. Maybe that was KDiff3's fault? This reduces my confidence on if bugs were not introduced.
|
|
|
|
|
|
|
|
For now, the notifiers on bone group color setting won't trigger the necessary
color syncing, so it will be necessary to select another bone/object before the
view responds properly.
|
|
|
|
More specifically, selecting bones didn't update the active F-Curve/Groups. This
meant that when editing drivers, it was often easy to accidentally edit the
drivers for the wrong bone.
|
|
references in bmesh docs.
|