Revision 1d90323 by Ton Roosendaal November 9, 2012, 15:00 (GMT) |
UI scripting: Layout separator should end button aligning. |
Revision 6cdb555 by Campbell Barton November 9, 2012, 14:52 (GMT) |
bmesh refactor - rename some of the BM_****_share_****_count() functions to BM_***_share_check() some of these were only returning a boolean, others returned a count even though only a boolean was needed. split some of the functions in two as well where check/count are both needed. |
Revision dc5ba03 by Brecht Van Lommel November 9, 2012, 13:57 (GMT) |
Fix #33123: lamp nodes drivers not working, now uses same hacks as material to work around dependency graph limitations. |
Revision 079a0a3 by Ton Roosendaal November 9, 2012, 13:33 (GMT) |
Usability: Made SHIFT+drag mouse in Curve and ColorPicker widgets move with more precision. This was only working with UserPref "continuous grab". |
Revision c046b13 by Campbell Barton November 9, 2012, 11:03 (GMT) |
rename template_color_wheel() to template_color_picker() |
Revision 6d31921 by Ton Roosendaal November 9, 2012, 10:41 (GMT) |
Temporarily change: Intel graphics cards now use Triple Buffer when you set it to "Auto". Recent tests proved that this is now working... and better test this now well than a week before a release! |
Revision 3ce1d54 by Ton Roosendaal November 9, 2012, 10:33 (GMT) |
Bugfix #33124 User Preference setting for Color Picker type only affected the popup version. Now it uses it for all color pickers in Panels too. Note for UI Py team: col.template_color_wheel() function follows the userpref - might be a need for rename here? Dunno how to handle this. Comment noted in template code. |
Revision 98e60b2 by Joshua Leung November 9, 2012, 09:57 (GMT) |
Edits for consistency with other parts of code For the record, AnimData vars should be named "adt", not "ad" |
Revision 2bb174c by Campbell Barton November 9, 2012, 09:33 (GMT) |
style cleanup: indentation |
Revision 03cc3b9 by Dalai Felinto November 9, 2012, 09:11 (GMT) |
Fisheye Equidistant Lens algorith bugfix r = lens * theta Thanks for Adriano Oliveira for reporting this and chasing down the right formula. Now fulldome works no longer need to use equisolid + a specific lens+sensor size. And happy birthday to me. And yes, that's how I celebrate it ;) |
Revision ffbf0a1 by Sergey Sharybin November 9, 2012, 08:47 (GMT) |
Cycles: no need in spin lock in memory statistics This functions are called from device code which is guaranteed not to be called simultaneously from different threads. |
Revision 76525d5 by Sergey Sharybin November 9, 2012, 08:46 (GMT) |
Cycles: persistent images option This option enables keeping loaded images in the memory in-between of rendering. Implemented by keeping render engine alive for until Render structure is being freed. Cycles will free all data when render finishes, optionally keeping image manager untouched. All shaders, meshes, objects will be re-allocated next time rendering happens. Cycles cession and scene will be re-created from scratch if render/ scene parameters were changed. This will also allow to keep compiled OSL shaders in memory without need to re-compile them again. P.S. Performance panel could be cleaned up a bit, not so much happy with it's vertical alignment currently but not sure how to make it look better. P.P.S. Currently the only way to free images from the device is to disable Persistent Images option and start rendering. |
Revision eff7342 by Campbell Barton November 9, 2012, 08:28 (GMT) |
add fallbacks for BM_vert_calc_shell_factor() and BM_vert_calc_mean_tagged_edge_length() to avoid divide by zero when a vertex has no connected geometry. also style cleanup. |
Revision 9dcd7f3 by Sergey Sharybin November 9, 2012, 07:29 (GMT) |
Fix crash when copying scene with sequencer's animation using Link Objects or Link Object Data methods - Don't crash if there's any fcurves created for sequencer but no sequencer itself - Don't copy sequencer's fcurves when copy new scene with linking data/objects method |
Revision 9b91da0 by Joshua Leung November 9, 2012, 06:36 (GMT) |
Axis Colours are now Themeable This commit allows you to set the RGB <-> XYZ axis colours used for things like the mini axis indicator, grid axis indicators, manipulators, transform constraint indicators, F-Curves (when using XYZ to RGB colouring option), and perhaps something else I've missed. Previously, these places all used hardcoded defines (220 * i/j/k), but the readability of these colours was often quite poor, especially when used with certain themes. The settings for these colours can be found under the "User Interface" section of the themes (i.e. same set of colours is used across editors). I could have made these per editor, but since it's unlikely that these will need to be too different across editors in practice (+ being easier to version patch), they are stored under the UI section. |
Revision 1369e29 by Campbell Barton November 9, 2012, 06:06 (GMT) |
shrink/fatten was missing from the transform menu |
Revision 0f2c27b by Campbell Barton November 9, 2012, 05:37 (GMT) |
Option for shrink-fatten to maintain shell thickness (hold Alt). |
Revision 56ae13b by Campbell Barton November 9, 2012, 04:20 (GMT) |
add a distance limit to the shrinkwrap modifiers project mode, it was problematic for vertices to fire rays out and hit some unrelated-far-off geometry which is often not what users want. |
Revision 11a5c90 by Campbell Barton November 9, 2012, 04:01 (GMT) |
code cleanup: move shrinkwrap's benchmark macro into PIL_time.h & some minor style edits. |
Revision cf08068 by Campbell Barton November 9, 2012, 03:36 (GMT) |
fix [#33121] crashing when srolling down in text editor ! |
|