===========================
Code clean-up:
- Remove unused args from template_movieclip.
- Remove C-defined "Marker" panel.
- Move all properties from old "Marker" panel to template_marker
template. This properties would be displayed if compact is set to False.
===========================
initial re-design commit:
- Added Mode to Clip Editor. Currently the following modes are present:
* Tracking/Solving mode (default)
* Reconstruction mode
* Distortion mode
- Hide all tools/properties which doesn't make sense in current mode.
- Keep a look at new template template_marker. It's needed to control
marker's properties, changing of which should produce new keyframe.
Currently only "Enabled" property can be control. Probably all
properties from "Marker" panel could go there so this template
wouldn't be so specific.
- No operators are disabled for non-their mode. It means they
can be triggered from Space menu or hotkey.
Need clear map operators into mode to prevent mess of poll function.
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.
infact this is not really a bug, irrespective zero vertex group weights gave overlapping geometry which isn't useful, add an option to set the thickness factor for zero weighted verts.
- add change data operator to strip panel next to image file properties since editing every image manually isnt really usable.
- added new sequencer operator "Clear Offsets" (Alt+O), useful to reset the start/end frames around the strip data.
*BLENDER_VERSION_CYCLE set to alpha
Idea is to set it to alpha for the first 3 weeks (B-Con1)
Beta for B-Con 2 and 3
RC for B-Con 4
Release for B-Con 5
===========================
- Distortion/undistortion were accidentally swapped in both of grease
pencil calibration and grid.
This was fixed but distortion coefficients should be re-adjusted.
There are some issues with high distortion coefficients but it
came from libmv and until it'll be fixed there nothing really
can be done here.
- Fixed displayed aspect ratio for muted footage when pixel/display
aspect ratio is differ from 1.0 or proxy size is not Full Render,
- Added c-api for image distortion/undistortion, Not used yet.
===========================
- Option to hide grease pencil (Display -> Grease Pencil).
- Added grease pencil controls to toolar.
- Fixed display issues when stroke contains one point only
and Manual Calibration is enabled.
===========================
Continue improving grease pencil for manual calibration:
- Fixed bug with local undo which was caused by not dropping
re-done nodes when pushing new undo node.
- Fixed bug with conversion grease pencil to bezier curve
(last point could be dropped away on such conversion).
- Added new mode: poly line drawing.
This mode allows to draw poly-line by clicking on
it's knots. In this mode user is allowed to pan/zoom
to new position before placing next knot.
===========================
Return non-blocking behavior to grease pencil sketch mode.
It is needed to implement more accurate line drawing based
on using mouse click on where line "knot" should be added
and allowing pan/zoom between such knots selection.
There are still issues with vertex paint/sculpt modes,
but they aren't critical -- just behavior could be
improved here.
Currently, grease pencil conflicts with such operators
as undo and set object mode which makes behavior totally
unpredictable and crash for some cases.
The only way to solve this proper is to ger rid of pointers
to data which can chage stored in operator custom data.
if vec.dot(vec) > some_distance*some_distance:
do_something()
might not be quite as obvious looking as:
if vec.length_squared > some_distance*some_distance:
do_something()
As to why you'd want to use length_squared over length is that length uses a square root, which isn't always necessary for simple distance checks (e.g., closest object, checks like the ones above, ect).
