Disable operator register and redo flags because it might modify non-mesh
data when in edit mode. This doesn't work properly with current undo stack
design.
* Replaced the hard coded viscosity presets with Python ones.
* Added version check, so older files load fine.
Loading new files into 2.62 also works fine.
- Changed regions to use the whole main region for such views as
curves and dopesheet. This allows to have own panels with
tools/properties in this areas.
- Active clip is getting synchronized between different clip editor
editors in the same screen, so updating of curve/dopesheet views
happens automatically when one changes current clip in one of this
editors.
- Curves and dopesheet are still using PREVIEW region type instead of
re-using main region.
- To deal with vertical synchronization in dopesheet, re-initialization
of preview region happens.
- Panels in toolbox and properties panels are now separated to rely
on current view mode, some operators and poll functions still need
to be updated.
- Added new screen called "Movie Tracking" where layout is configured to
display timeline, main clip window, curves and dopesheet.
Expose option into interface to use modal solver which currently
supports only tripod motion.
This solver requires two tracks at least to reconstruct motion.
Using more tracks aren't improving solution in general, just adds
instability into solution and slows down things a lot.
Refirement of camera intrinsics is supported by this solver.
To use this solver just activate "Tripod Motion" checkbox in
solver panel.
Previously it used to use cursor location from time when panel was drawn,
which in some cases lead to using previous cursor location instead of current.
* Negate label in the Vertex Groups panel was misleading to the string buttons, rather then the check boxes. Fixed it by having 2 columns.
Not ideal still, but better! :)
Issue reported by Tobias Kummer. Thanks!
backup files like .py~ for eg had their own menu entries which got annoying.
added optional filter_ext function callback argument to Menu.path_menu() to avoid displaying invalid types.
This report points out thet absolute shape keys are unusable.
The problem is there was no way to adjust the play time of a shape key (all absolte shape keys would start at frame zero with no way to change the speed).
Added an 'eval_time' property to the key block that works like the curve path evaluation time, so the time in the keyblock can be controlled.