Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* remove copying of libjack dll's, libjack is statically linked now.
|
|
* Change ICON_NULL --> ICON_NONE to avoid two #defines with the same meaning.
|
|
* Moved two #defines out of the enum to make code more readable.
|
|
Curve widget editing used bad pointer, unsure in which cases it
would crash though...
|
|
* Moved ICON_BLENDER away from (0,0) spot in blenderbuttons, since ICON_BLENDER=0 define is conflicting ICON_NULL define as well as with logic checks for nonzero icon id.
* This solved bug where ICON_BLENDER can't be set from Python as well as when using new UI functions from within Blender.
|
|
- Invalid shape when deformation mesh was disabled befoe undoing
- Crash when deformation modifier was enabled before undoing
Still got problems with undoing multires changes when toggling modifiers.
|
|
scripts but considered bad practice by python devs)
|
|
* Added a NC_OBJECT|ND_TRANSFORM notifier to it, so we get a refresh when using the operator from python console. Issue reported by calli in IRC.
|
|
limits etc) by Juha Mäki-Kanto + ui changes pour moi
From the tracker:::
Issues fixed:
- ConeTwist-constraint's params weren't making it to the CcdPhysicsEnvironment, also added Hinge's params.
- UI wasn't using angles where applicable.
- btHingeConstraint's constructor can create frame-matrices which don't align so the hinge doesn's start at 0 degree tilt.
This is an issue when setting limits.
Changes:
- UI: Hinge limits can be set (and disabled).
- UI: ConeTwist only has max-limits and only the twistX can be disabled
- PyApi via rna_constraint.c: added the functions limit_xyz_min, limit_xyz_max (for 6dof), limit_angle_xyz_min,
limit_angle_xyz_max (for 6dof), limit_angle_x_min, limit_angle_x_max (for hinge).
- PyApi: dropped python-function limit_cone_min.
.:. Extra:
UI Changes:
- renamed "RigidBody Joint" to "Rigid Boidy Joint"
- reorganized UI to conform with other parameters (e.g. Limit Rot)
- added dis/active all over the place :)
|
|
using a different method.
|
|
to be safer).
- detect includes for qtcreator projects as well as the ones from cmake (it didnt return all of the right paths).
|
|
|
|
to sequential error by adopting a two-pass smoothing strategy instead.
This seems to give some minimal reductions in the amounts of unwanted
shrinkage that occurs
|
|
- Fixed problem where just trying to replace existing keyframes would
result in the intepolation set on that keyframe to get lost. This was
mostly an issue if trying to re-block some animation in the middle of
a shot, with the rest of the keys set to Bezier, but the first
keyframe in this new segment needing to be Constant so that we don't
get sloppy automatic interpolation in the way
- Hooked up Media-Play/Stop/Next/Prev controls to animation playback
and keyframe jumping functionality in default keymap in addition the
existing controls. I'm also considering whether to migrate Next/Prev
Keyframe key mappings off the Ctrl-PageUp/Down keys for a more
ergonomic option (i.e. shift <, shift >)
|
|
Let's make it four! :)
|
|
Mesh editing: operator "Blend From Shape" had blending off as default.
A bit weird... so let's change :)
|
|
- errors would jump to the line which gets in the way.
- the window wouldn't always redraw.
|
|
|
|
Two bugs in one:
- Lukas commit monday for new group/socket handling accidentally removed
to set socketype in stacks, which as used by (texture) nodes to detect
whether value, color or vector had to be read.
Result was that all texture nodes were rendering as B&W
- Old 2.5 bug: preview renders for texture nodes didn't call a
NodeEndExec function, which gave crashes on deleting nodes.
The change in interface_hanlers.c is only a comment to explain
how keymaps are being found.
|
|
|
|
markers were always drawn as local pose-markers, even when they were
not.
|
|
markers.
This is useful for when working with lipsync shots, where you've used
markers for noting down key syllables and want to separate these out
into chunks to manage things better.
|
|
the strength of the brush, as it was in 2.49
Layer height used to be controlled with brush radius, quite confusing decision.
Added new property for brushes - height for adjusting affectable brush height
(it could be not only layer height in the future).
|
|
Shift+A "add primitive" menu didn't allow to set shortcuts on the
sublevels.
|
|
Menu Help -> Operator Cheat Sheet crashed, calling function with NULL context.
|
|
|
|
also add WITH_PYTHON define to qtcreator project generator until we get a way to add them properly.
|
|
by Alex Fraser (z0r)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|