| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
returning translated strings, which should never get into data. And it may generates dummy names in some situations (like all new Filter nodes were getting "Soften" as name (default option), better to always get "Filter" in this case!).
(Note for Lockal: also checked fcurves/drivers, but those names are directly taken from RNA prop name, hence they are as UI label, translated in the current language, but not stored in data. So no problem here ;) ).
|
|
then they needed to be.
update to clang_array_check.py - parse function definitions lazily for some speedup.
|
|
|
|
There are still a lot more in bmo_bevel.c and bmo_extrude.c, but those don't
seem that easy to fix.
|
|
cleanup)
* Enum tooltips will only be detected in the case that we assign that as the
default property (ot->prop) of the operator. Set all of the offending properties
to get this status, since those operators would be useless without that property
anyway
* Improved the wording/capitalisation of a few of these tooltips and labels
|
|
property
Changes:
This commit adds a second line to the tooltips (below the generic operator
description) showing the appropriate description for each enum option. This
brings it more into line enum properties in Blender which also show this sort of
information.
Rationale:
Operators such as Snap and Mirror in the Action and Graph Editors use an enum to
control their behaviour (respectively, "how to snap" or "what to use as the
mirror line"). In the menus, these options are displayed using a submenu, but
hovering over each of these items for more information from a tooltip only shows
the (relatively unhelpful) generic operator tooltip/description.
Another area where these descriptions are useful is for Keying Sets, where it's
now possible to see the descriptions for what each Keying Set
does/affects/requires. Again, this is more helpful than just the generic
tooltip, which would be something like "Insert keyframes using a Keying Set".
|
|
Thanks Julien DUROURE (julien)
|
|
own regression since 2.63,
The path length for FILE_OT_select_bookmark was too short as well (256 --> FILE_MAXDIR).
|
|
|
|
check on imbuf),
all other uses of sequencer_imbuf_assign_spaces() check for NULL or assume IMB_allocImBuf() succeeds.
|
|
|
|
|
|
var as possibly NULL.
|
|
* new/remove for GPencil frames/strokes/
* add/pop for points
* clear for frame/layer & grease_pencil
* copy for frame
+ fix for free_gpencil_frames() not clearing the active frame
|
|
wm_window_title.
|
|
rename V3D_PROJ_RET_SUCCESS -> V3D_PROJ_RET_OK
|
|
coords of a point, move into a static function.
|
|
- range check on hair_velocity_smoothing() was off by one.
- cloth sim parm's are used before NULL check in readfile.c
|
|
|
|
|
|
|
|
|
|
from Andreas Schwab (schwab)
modified to use code from BLI_endian_switch.
|
|
temp char (approx 18x speedup on my system).
|
|
from Sunny Gogoi (darkowlzz)
|
|
should have been optional.
|
|
Note that this is just an RNA change, underlying dualcon octree
already supports even higher values.
|
|
Separate vertex copies are now made for flat-shading, such that the
normal is correctly flat-shaded. The element index buffer is not
created in this case.
|
|
* De-duplicate GPU code to check if VBO should be used.
* Add a flag to indicate if the buffer should be drawn smooth or not,
rather than checking each time the node is drawn.
|
|
also correct array sizes in othere areas.
|
|
draw_tracking_tracks().
|
|
Used the same hack as BLI gzip is using -- calculate short path and
send it to OCIO library.
|
|
definition (EDBM_selectmode_convert())
Cheers to Sebastian Nell (codemanx) for catching this.
|
|
the mouse about to see the result).
also remove print from last commit.
|
|
bmesh is empty
was missing set typecheck
|
|
utility metaball functions to (de)select all.
|
|
|
|
which DNA ignores.
tag operator callbacks as needing their return values used. These are not directly called in many places so the inconvenience is minimal.
|
|
As suggested by Campbell on the IRC gave grease pencil its own notifier type (NC_GPENCIL) and made the makesrna notifier functions actually update properly.
Also got the #ifdef'd GreasePencil.layers.[new/remove] functions working.
|
|
|
|
also add boundbox checking for lasso select.
|
|
|
|
radius-squared for circle select comparisons.
edge_fully_inside_rect() & edge_inside_rect() args were shorts when all callers were passing ints.
|
|
* Added/fixed some comments
* Swapped order that invoke/exec calls are defined in the operator definitions
to reflect flow better
|
|
Added a convenience operator to the Follow Path constraint which adds a F-Curve
for the path (or the operator's "fixed position" value if no path is assigned),
with options for setting the start frame and length of motion. This makes it
easier for common users to just set up a quick follow-path animation where the
camera (e.g. flying around a set over certain number of frames).
A key advantage of this is that it takes care of the underlying math required
for setting up the generator curve accordingly (I've got some plans for making
this a bit friendlier to use later). Now, animating the paths is a one-click
operation, with the start and length properties able to be controlled using the
operator properties.
|
|
|
|
Recently on the bf-funboard list, there have been some requests for clearer
indications for animators that autokeying has been enabled when transforming so
that corrective action can be taken sooner if this wasn't expected. This is
especially important in distributed+collaborative environments where multiple
artists may work on a single shot file: someone working on a shot from
another animator may not be aware that autokeying was enabled, thus accidentally
setting a whole bunch of extra keyframes.
In this current incarnation, we display using red (not hardcoded, but using an
existing theme color) a solid 1px border around the 3D view while transforming
with autokeying enabled. In addition to the border, a blinking indicator (record
icon + "Auto Keying On" text) appear in the top right corner, as inspired by the
traditional recording indicator icons on camcorders.
|
