to scale towards zero
This is an attempted bugfix for a bug which seems to be very fickle to
reproduce (it only happens sporadically after quickly jerking the
strips around in a certain way). So far when testing, I haven't had
any more problems after applying this fix, though it may just be
unreliable testing.
Use PageUp/Down for moving up/down, and Shift PageUp/Down for moving
to top/bottom. This is more comfortable than the old combinations
involving shift+ctrl.
Thanks pepeland and 3duan for the suggestions. I've been looking at
improving these for a while...
* Left/Right Arrow = Single Frame stepping as before
* Up/Down Arrow = Jumps to next/previous keyframe (used to be the
uncomfortable Shift PageUp/Down)
* Shift Up/Down Arrow = Jumps forward/back in 10 frame increments
(used to be Up/Down Arrows). 10 frame increment should get
customisable again as in 2.4, but need to find some UI space to put
that!
* Ctrl Shift Up/Down/Left/Right = Jump to start/end frame (used to be
Shift <Arrow Key>)
* Removing check if Node is in between, so in-/output nodes can be muted as well. Useful for example if you want to temporarily mute a file output node.
linked
Shapekey actions weren't getting copied when their owner data was.
This was due to the IMO totally convoluted way in which the duplicate
action flags have been set up:
- the function to copy animdata takes a param to specify whether
actions are copied or not, but this is never touched (i.e. this always
just gets FALSE passed in)
- instead, we jump around in hoops later figuring out whether the
userpref wants copying to occur, then fixing up the links
IIRC, part of this may be due to a desire/need to not duplicate
actions when dealing with NodeTree copies for multi-threaded
rendering, but at the expense of complicating everything else.
High quality resampling on mixdown, linear for playback.
* Lots of improvements and fixes for the JOS resampler, now it works fine!
* High quality filter coefficients for the JOS resampler (sorry for the 5 MB source file).
* Fix for GE orientation bug. Note: moto uses x,y,z,w quaternion storage, while rest of blender uses w,x,y,z.
* Minor changes/fixes.
There's no reason to have it really, this situation is totally normal, and it
means a terminal window is opened on Windows as long as you haven't saved any
default settings yet.
in a particular setup with two nested material nodes. Material active texture
was looking also recursively into material node, but this was already done
outside of this function.
