Revision 54c4ed4 by Ton Roosendaal December 10, 2008, 13:56 (GMT) |
2.5 Cleanup in area/region management - more intelligence in area management for adding handlers and setting data correct. Space/Region type callbacks only have to do own things. - added option for adding default handlers to areas/regions. (flag in type definition) - ensured that region-types store the minsizes for regions. - added boundbox check for handlers; note that it accepts pointer to boundbox, because handlers don't get reset on area-resizing or view changes. Example: view2d handlers use mask rect. - handlers get now added on correct context levels (example frame change also worked in header) - removed ->refresh() callback. Context refreshing is Listener. - the ->init() is being called on all WM level actions, also after a file read, moving areas, re-opening areas etc. - fixed bug: crash on exit was caused by cleaning up Screen too late. - UI_view2d_size_update() removed from draw callback, is init() - regions now store (winx, winy) subwindow size. |
Revision 1fdb9da by Joshua Leung December 10, 2008, 12:00 (GMT) |
RNA - Wrapped a few more Armature/Bone settings * I've only got a few more Armature settings to go (path stuff) * Bones have still only got name + layers so far |
Revision 6dc2714 by Campbell Barton December 10, 2008, 11:42 (GMT) |
fix for [18069] open nurbs curve snaps end to centerpoint made nurbs surface curves use the same number of points as nurbs curves. |
Revision 2ef5af6 by Campbell Barton December 10, 2008, 09:45 (GMT) |
merge from trunk - r17500 to HEAD |
Revision a8726cd by Joshua Leung December 10, 2008, 09:07 (GMT) |
View2D - Bugfixes Fixed a few typos in View2D code, which included the zoom-locking flags not being checked for correctly by the zoom operators. This commit does NOT fix the problems with the Outliner 'cur' rect expanding/contracting as the view changes size. I still haven't found the cause of this, but it might be related to the off-by-1 errors with UI-widgets that brecht noted in TimeLine header... |
Revision 2f39ae3 by Campbell Barton December 10, 2008, 05:41 (GMT) |
move the paint buttons from the image view and buttons window into one function. |
Revision 4a9ee46 by Brecht Van Lommel December 10, 2008, 04:36 (GMT) |
UI: don't use operators anymore for handling user interface events, but rather a special UI handler which makes the code clearer. This UI handler is attached to the region along with other handlers, and also gets a callback when all handlers for the region are removed to ensure things are properly cleaned up. This should fix XXX's in the UI code related to events and context switching. Most of the changes are in interface_handlers.c, which was renamed from interface_ops.c, to convert operators to the UI handler. UI code notes: * uiBeginBlock/uiEndBlock/uiFreeBlocks now takes a context argument, this is required to properly cancel things like timers or tooltips when the region gets removed. * UI_add_region_handlers will add the region level UI handlers, to be used when adding keymap handlers etc. This replaces the UI keymap. * When the UI code starts a modal interaction (number sliding, text editing, opening a menu, ..), it will add an UI handler at the window level which will block events. Windowmanager changes: * Added an UI handler next to the existing keymap and operator modal handlers. It has an event handling and remove callback, and like operator modal handlers will remember the area and region if it is registered at the window level. * Removed the MESSAGE event. * Operator cancel and UI handler remove callbacks now get the window/area/region restored in the context, like the operator modal and UI handler event callbacks. * Regions now receive MOUSEMOVE events for the mouse going outside of the region. This was already happening for areas, but UI buttons are at the region level so we need it there. Issues: * Tooltips and menus stay open when switching to another window, and button highlight doesn't work without moving the mouse first when Blender starts up. I tried using some events like Q_FIRSTTIME, WINTHAW, but those don't seem to arrive.. * Timeline header buttons seem to be moving one pixel or so sometimes when interacting with them. * Seems not due to this commit, but UI and keymap handlers are leaking. It seems that handlers are being added to regions in all screens, also in regions of areas that are not visible, but these handlers are not removed. Probably there should only be handlers in visible regions? |
Revision ce5b9d2 by Campbell Barton December 10, 2008, 03:13 (GMT) |
tweaks to brush falloff and alpha, giving nicer looking strokes. |
Revision 6651af4 by Martin Poirier December 9, 2008, 21:25 (GMT) |
When not using quick mode, automatically select the last drawn stroke. |
Revision 2b9a625 by Martin Poirier December 9, 2008, 20:46 (GMT) |
Reeb graph filtering Add exception to normal nodes preservation when that node is the root node. In that case, pruning the arc is A-OK and in fact needed. |
Revision 12debd4 by Maxime Curioni December 9, 2008, 17:14 (GMT) |
corrected crash caused when enabling scene vectors |
Revision b205ec4 by Ton Roosendaal December 9, 2008, 15:59 (GMT) |
2.5 Area Manager: revised how an area subdivision gets managed. Originally the 'spacedata' would store regiondata too, but this already became impractical (like having view2d data in region is useful). So I left that part how it is. See new diagram: http://wiki.blender.org/index.php/BlenderDev/Blender2.5/AreaManager This means that regions in an Area define location/size or constraints for how they get arranged. The "RegionType" which is linked to this defines its functionality. For fun, test, and code validation: two temporary hotkeys added. SKEY: splits current region horizontally SHIFT+S: splits vertically Note - in outliner - that "context" sticks to the Area as whole, the region here only defines view. That's the purpose. :) For two outliners with different context you open 2 areas. Also note that dragging screen-edges shows the region-alignment type (split with percentage). |
Revision 42f7923 by Campbell Barton December 9, 2008, 14:30 (GMT) |
bugfix - [#18063] Projection paint branch: draw tool "drops out" when model extends beyond view borders reported by michael williamson. Was caused by point inside triangle test using an error limit that didnt adjust for different size triangles. |
Revision cd47292 by Benoit Bolsee December 9, 2008, 14:16 (GMT) |
ImageMirror: add clip attribute to limit clipping distance of mirror rendering |
Revision b9e04c6 by Joshua Leung December 9, 2008, 11:29 (GMT) |
RNA: Start of RNA wrapping for Armatures Wrapped most of Armature settings, but bones are not yet complete. |
Revision 4251912 by Campbell Barton December 9, 2008, 08:21 (GMT) |
* tablet pressure changing opacity while painting didnt work * pixels with <= the current opacity are not painted onto, speeds up painting especially with low spacing. (only when airbrush is disabled) * use qsort rather then own crufty sorting function * grouped projection painting functions together. |
December 9, 2008, 07:19 (GMT) |
wip commit to work on at home, nothing to see |
Revision 13c634c by Joshua Leung December 9, 2008, 06:23 (GMT) |
2.5 - Swapped order for adding View2D keymaps in TimeLine so that they can still work. |
Revision 12fbd93 by Diego Borghetti December 9, 2008, 04:57 (GMT) |
Fix mistake in last commit.. it's pic + 1 ;) |
December 9, 2008, 04:27 (GMT) |
* Added back the GR: field for volume materials, limiting lighting to a certain group |
|
|
|


Master Commits
MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021