September 12, 2013, 13:29 (GMT) |
scons + mingw Compile Fixes for r.59942 * SCons files for guardedalloc module requires all the source files to be listed out, like in CMake. * mingw32 (or at least gcc 4.6.2) seems to follow the Windows convention of using _msize() instead of having a "malloc_usable_size()" |
September 12, 2013, 12:51 (GMT) |
Added an option to pin the operator redo panel. When it is pinned it stays open when the toolbar is closed. |
September 12, 2013, 12:07 (GMT) |
September 12, 2013, 11:43 (GMT) |
Dividers can now be dragged. Buttons display a bit of text if there is no icon yet. |
September 12, 2013, 00:13 (GMT) |
Modify modal solver to use only camera 0 Match recent changes to how tracks are stored. |
September 11, 2013, 23:47 (GMT) |
merge with trunk -r 60055 |
September 11, 2013, 15:14 (GMT) |
Dividers can be folded, but not dragged yet. |
September 11, 2013, 14:48 (GMT) |
Clearer association between markers and cameras As the camera identifier associated with a marker is simply bookkeeping for multicamera reconstruction, make it an optional attribute when handling tracks and reconstructed views. This means that the libmv API is still nice for users that don't need to associate images with cameras. |
September 11, 2013, 12:13 (GMT) |
Added dividers and made the tool shelf context dependent |
September 11, 2013, 11:18 (GMT) |
Merging from trunk r60041 into soc-2013-motion_track |
September 11, 2013, 10:34 (GMT) |
Fix: BKE tracking compilation error Previous commit was incomplete and didn't include blender-side changes to the libmv API. |
September 10, 2013, 21:07 (GMT) |
Modify data structure for storing tracks The Tracks data structure stores Markers. The current design has it so that a marker's image identifier denotes the frame from the associated camera that the marker belongs to. That is, it treats the image identifier more as a frame identifier. You could have markers in image 0 for camera 0 and image 0 for camera 1 and they wouldn't be considered to be in the same image. However, this design doesn't make much sense because the reconstruction algorithms don't care about frames or the cameras from which a frame came, only that there is a set of images observing the same scene. A better design is for all frames from all cameras to have unique image identifiers. The camera identifiers can then denote a subset of those images. No image captured by camera 0 will have the same image identifier as images from camera 1. This way, the algorithms can continue to just treat all frames as one big set of images and the camera identifier provides the association of an image to the camera it originated from. This makes it much easier to implement multicamera reconstruction without significant changes to the way libmv behaves. |
September 10, 2013, 18:32 (GMT) |
Implemented drag and drop for the icon shelf. Removed code for menubar menus that was commented out. |
September 10, 2013, 14:59 (GMT) |
September 10, 2013, 12:22 (GMT) |
September 10, 2013, 12:20 (GMT) |
Small tweaks to the custom panel button dragging. |
September 10, 2013, 10:57 (GMT) |
Update doxygen comments for reconstruction initialization EuclideanReconstructTwoFrames and ProjectiveReconstructTwoFrames currently assume that the passed markers belong to a single camera. That is, we're not reconstructing frames from different cameras. Ideally, this restriction should be removed. |
September 10, 2013, 09:13 (GMT) |
Merged revision(s) 59930-59994 from trunk/blender into soc-2013-dingto. |
September 10, 2013, 07:42 (GMT) |
Fix for OSL volume closure flattening, this was not copying settings from the OSL closures. |
September 10, 2013, 07:42 (GMT) |
Removed invalid code from volume closure, the OSL distinction has to happen on a different level and doesn't make any sense. The function body works in both SVM and OSL case. |
|
|
|


Master Commits
MiikaHweb | 2003-2021