===========================
- Internal changes:
* Rename uiTemplateMarker to uiTemplateTrack.
* Fixed some comments in movieclip.c.
- Control channels which are affect on track.
- Fixed track deletion when it's point isn't selected.
Fix for bug found by psy-fi.
* gpu_buffers.c was using GL_ARB_vertex_buffer_object to check for VBO
support, should be using GLEW_ARB_vertex_buffer_object.
===========================
- Fixed "sliding" when panning footage in high zoom.
This was most noticeable near right top corner of footage.
- Fixed 1px flickering of marker during playback with
"Lock to Selection" toggled on. This was caused by
precision errors. Used UI_view2d_to_region_no_clip-like
offsets calculations, but in float values. Maybe there
could be something smarter..
- Implemented tarcking along single frame.
Hotkey is ALT+left/right array. Also changed a bit
tracking tools buttons in Tools panel.
- Fixed "Lock to Selection" during tracking -- tracks
synchronization should happen before centering view.
- Approximate marker's position for frames, which haven't
got marker for them.
Use the nearest marker from left side for approximation.
For frames above first marker's framenr sue first marker
position.
- Markers now could be disabled. Added checkbox to
"Active Marker" panel.
- Changes in cache line:
* Bright line means active track has marker for frame.
* Dark line means marker's position is approximated.
* Yellow-less line means marker is disabled for that frames.
NOTE: .blend files which are saved with previous tomato version
would fail to work properly. I don't want to spend time
on making that files work properly atm, so don't blame on this.
error messages on start. These were coming from initializing the SDL video
subsystem as part of Joystick init. We do not need this, as video stuff is
covered by GHOST, most likely this was conflicting.
On clicking in a non-active Blender window (when you activated others),
the mouse position of the first click was still the old position.
Problem is in GHOST; it sends out the 'activate window' event after the
mouseclick event itself. Code now checks for this case and reads the
correct mouse position.
Toggling options on the selection is better done as a generic operator.
Replace ARMATURE_OT_flags_set and POSE_OT_flags_set with WM_OT_context_collection_boolean_set and use menus to access it with specific settings.
This way its easy make a key shortcut which toggles any boolean on any collection - sequences, metaballs, objects, bones etc.
Fix for bug #27710, 'Multires lost from 2.49 file in 2.5x'
Reported by Gaia Clary.
Problem was that the old multires data didn't flush changes to
vertices out to the Multires structure on filesave. So, recent bits of
sculpting could be lost if the multires level wasn't changed before
filesave.
We already had code to deal with missing multires vertex data, which
simply copies the Mesh vertex data into the multires vertex data if it
matches the number of vertices in the highest level. Moved this code
up a bit so that we always make this copy if the numbers match up.
Was able to reproduce the bug fresh in 2.49b, and confirmed that the
fix works. However, this does not help if changes were sculpted on a
multires level other than the highest level and saved without a
subsequent level change.
- comment/remove assignments from values to themselves.
- add case break statements (no functional change but some source code checkers notice).
- fix python errors when the sculpt brush is None.
lambda_cp_line --> line_point_factor_v3
lambda_cp_line2 --> line_point_factor_v2
correction to previous commit function name
isect_seg_sphere_v3 --> isect_line_sphere_v3
... since its not clipped.
added a clip argument to the python version of the function.
Thumbnail save for .blend crashed, when being in editmode for a mesh
that has other object users as well. Derivedmesh confusement...
Thanks to Sergey for finding the cause!
Default startup theme used same node header color for "in/out" nodes
as for "inactive or undefined" nodes. This made it impossible to see
which of the output nodes in node setup was 'active'. Made the active
in/out color a slight blueish shade of grey now.
Python:
* adds bpy.app.handlers which contains lists, each for an event type:
render_pre, render_post, load_pre, load_post, save_pre, save_post
* each list item needs to be a callable object which takes 1 argument (the ID).
* callbacks are cleared on file load.
Example:
def MyFunc(scene): print("Callback:", data)
bpy.app.handlers.render_post.append(MyFunc)
C:
* This patch adds a generic C callback api which is currently only used by python.
* Unlike python callbacks these are not cleared on file load.
Usage currently is limited to:
- Panel text, widget text and label text style:
point size, shadow effects
Setting individual fonts to these is not possible yet, it uses the
default for it.
Access goes via outliner now; check "User Preferences". UI team could
add this in userpref scripts :)
This was causing a lot of backward compatibility problems and side effects.
It has to be done properly, linked with Material ObjectColor shader_flag or at least the TF OBCOLOR (which apparently worked at some point so I've been told).
If you need to use OBCOLOR simply keyframe the obcolor and it will work as before.
In addition the billboards can be scaled by the particle velocity with optional head and tail factors (similar to line drawing options). This allows for pseudo-motionblur effects.
The rna set function clamps to the property range however properties with range functions were ignored when set by python or the animation system.
Now call the range function for ints and floats when setting.
===========================
- Corrected copyrights in my new files header.
- Added debug option to dump as PNG image content of search
areas tracking between which was failed.
- Removed internal tracking settings like pyramid level and
tolerance. Weren't useful neither for me nor for artists.
- Fixed bug in BKE_tracking_get_marker which could lead
to failure of getting marker for current frame when
there's marker for requested frame.
- Fixed bug with disappearing markers after tracking for
cases when marker was added at frame different from
tracking start frame and tracking start frame is
equal to tracking end frame.
- Stop tracking when no markers could be tracked.
- Changed marker selection rules:
* If marker isn't selected, all it's areas are getting
selected with mouse.
* If marker is selected and selection type doesn't have
"extend" mode (SHIFT isn't holded down) the nearest
to mouse cursor area would be selected. All the reast areas
would loose selection.
- Limit number of frames which would be used in "Track Markers"
operator. So now you could easily track along 10/20/etc frames.
- Change scene current frame after "Track Markers" operator.
- Implemented speed limitors. Now tracking could happen:
* As fast as possible
* With reatime speed (scene FPS)
* With half of realtime speed
* With quarter of realtime speed.
- Got rid of orig_user in MovieTrackingContext and user
in TrackMarkersJob. This prevents crashes when user
joins some space to SpaceClip from which tracking was started.
- Made keyframes on path bigger and do not draw keyframes for
non-selected markers.
TODO: need to get rid of storing main, scene and screen
in TrackMarkersJob. This is needed to set scene's
current frame after tracking (such behavior is comfortable
for artists) but this could lead to crash if scene is
getting removed when tracking job is running.
Render animation operator also stores scene and main,
so such solution could be fine for first time before
we've got something smarter.
