Revision 53bf66a by Campbell Barton June 23, 2011, 06:13 (GMT) |
checks in rna range functions that the max value cant be less than the min. also fix for invalid rage for FILE_OT_filenum. |
Revision 353cd44 by Campbell Barton June 23, 2011, 06:11 (GMT) |
fix for building on arch linux with ffmpeg version: LIBAVCODEC_VERSION_MAJOR 52 LIBAVCODEC_VERSION_MINOR 122 |
Revision f511409 by Campbell Barton June 23, 2011, 05:58 (GMT) |
fix [#27726] Driven properties not checked for legal UI bounds 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. |
Revision 5211a68 by Sergey Sharybin June 22, 2011, 17:43 (GMT) |
Camera tracking integration =========================== Minor fix: curfra could be set to 0 when tracking fails on first tracking frame. |
Revision c710c2c by Sergey Sharybin June 22, 2011, 16:28 (GMT) |
Camera tracking integration =========================== Fixed bug with invalid colors for space clip when startup.blend is created in 2.58 release build. |
Revision d30504c by Sergey Sharybin June 22, 2011, 16:16 (GMT) |
Probably merging conflict. Reverting startup.blend to version from trunk. In my local GIT repo i've got rid of changing startup.blend -- it's unneeded due to all needed stuff should be done via themes do_versions. |
Revision 60948c9 by Sergey Sharybin June 22, 2011, 15:58 (GMT) |
Accidentally commited unneded change to libmv. This change helps to track more stable, but it's a bit hackish way of making things better. |
Revision 0bb215e by Sergey Sharybin June 22, 2011, 14:54 (GMT) |
Camera tracking integraiton =========================== - 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. |
Revision 68b7d48 by Sergey Sharybin June 22, 2011, 14:44 (GMT) |
Revision 5021dd3 by Joshua Leung June 22, 2011, 13:30 (GMT) |
Bugfixes for recent commits: * Insert Key on Selected Channels in Action Editor was broken * Transform/Select All tools in Action Editor were broken as result of filtering changes. * Set Visibility operator, when used from Graph Editor now does similar things to the TabKey lock/unlock operator with regards to the flags it uses for filtering |
Revision c48e146 by Joshua Leung June 22, 2011, 12:54 (GMT) |
Bugfix [#21276] The Tab key is not working in the Graph Editor when the list of animated curves is closed At long last, this old bludger can be put out to pasture. I figured it would involve some of the visibility-filtering stuff I added, but this required a bit extra effort than anticipated. |
Revision fb1ded6 by Campbell Barton June 22, 2011, 12:05 (GMT) |
update automatic rna changelog |
Revision ab2026b by Joshua Leung June 22, 2011, 11:41 (GMT) |
Animation Channel Filtering Refactor - Part 3 (Visibility Flag Split) * This (big) commit is aimed at cleaning up the filtering flags used by the animation channel filtering code. The list of filtering flags has been growing a bit "organically" since it's humble origins for use in the Action Editor some 3 years (IIRC) ago now during a weekend hackathon. Obviously, some things have ended up tacked on, while others have been the product of other flag options. Nevertheless, it was time for a bit of a spring clean! * Most notably, one area where the system outgrown its original design for the Action Editor was in terms of the "visibility" filtering flag it was using. While in the Action Editor the concept of what channels to include was strictly dictated by whether the channel hierarchy showed it, in the Graph Editor this is not always the case. In other words, there was a difference between the data the channels represented being visible and the channels for that data being visible in the hierarchy. Long story short: this lead to bug report [#27076] (and many like it), where if you selected an F-Curve, then collapsed the Group it was in, then even after selecting another F-Curve in another Group, the original F-Curve's properties would still be shown in the Properties Region. The good news is that this commit fixes this issue right away! * More good news will follow, as I start checking on the flag usage of other tools, but I'm committing this first so that we have a stable reference (of code similar to the old buggy stuff) on which we can fall back to later to find bugs (should they pop up). Anyways, back to the trenches! |
Revision 1309f17 by Campbell Barton June 22, 2011, 08:43 (GMT) |
cmake was installing .bfont.ttf in ~/.blender/VER/config, use ~/.blender/VER instead (as with scons) |
Revision be94dc1 by Campbell Barton June 22, 2011, 05:30 (GMT) |
split cmake check configuration out |
Revision 352c0ba by Geoffrey Bantle June 22, 2011, 00:39 (GMT) |
Fix for boolean modifier: ---------------------------------------------- Patch for making faces stop dissapearing when using the boolean modifier submitted by howardt in IRC. |
Revision 1bb7639 by Geoffrey Bantle June 22, 2011, 00:34 (GMT) |
Fix for decimator: ---------------------------------------------- Patch for making faces stop dissapearing when using the decimator submitted by howardt in IRC. Also fixed crash for when input mesh had less than three triangles |
Revision 11c0ee5 by Joerg Mueller June 21, 2011, 21:10 (GMT) |
Merged with trunk r37717. |
Revision 2d3d025 by Joerg Mueller June 21, 2011, 20:39 (GMT) |
3D Audio GSoC: - Sequencer dynamics: Now it's possible to change the output channels and the resampling quality also increased (previously maximum quality was 44,1 kHz) - Changed two buffers to use ffmpeg allocation, not sure if that helps somehow. |
Revision 8e6b559 by Joerg Mueller June 21, 2011, 20:35 (GMT) |
3D Audio GSoC: Adapting all readers to maximally support dynamic resampling/rechanneling, introducing a DynamicIIRFilter for example. |
|
|
|


Master Commits
MiikaHweb | 2003-2021