November 29, 2016, 01:14 (GMT) |
Replacing UI_view2d_scrollsers_draw() to immedaite mode Part of T49043 Reviewers: krash, merwin Reviewed By: krash, merwin Differential Revision: https://developer.blender.org/D2364 |
November 29, 2016, 01:11 (GMT) |
Moved UI_view2_multi_grid_draw() to Gawain Part of T49043, to replace gl immediate calls with Gawain Reviewers: krash, merwin Reviewed By: krash, merwin Tags: #bf_blender_2.8 Differential Revision: https://developer.blender.org/D2363 |
Revision 2b25fe3 by Martin Felke (fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) November 28, 2016, 21:45 (GMT) |
fix for possibly different object / shard order after loading a baked simulation |
November 28, 2016, 20:22 (GMT) |
[msvc] change linker options from /opt:noref to /opt:ref, saves about 20% off the executable size Nobody appears to know why this option was on (and just on for just x64 at that) |
November 28, 2016, 18:03 (GMT) |
UI: Add 'x' icon to text buttons to clear content This is useful e.g. for search buttons to quickly clear the filter string. We might want to make this optional for python scripts. |
November 28, 2016, 17:12 (GMT) |
[msvc2017] remove eigen vector workaround for msvc2017. |
November 28, 2016, 16:56 (GMT) |
removed the '(Default)' addition from the Collada menu entries |
November 28, 2016, 16:54 (GMT) |
Added 'use collada 2' options to importer/exporter to make testing easier during development (will eventually be removed again) |
November 28, 2016, 16:23 (GMT) |
November 28, 2016, 11:27 (GMT) |
Cleanup: remove include of ED_view3d.h from paint_intern.h Really always better to avoid includes in includes, unless totally impossible/unreasonable to do otherwise... |
November 28, 2016, 11:20 (GMT) |
Cleanup: get rid of unused functions and vars, and indentation fixes. |
November 28, 2016, 10:28 (GMT) |
Merge branch 'master' into soc-2016-pbvh-painting |
November 28, 2016, 06:26 (GMT) |
Remove sensor-size to int conversion Currently harmless since the value is always set at its default (32). Even so, it's confusing since its used with floats after. |
Revision 77599a6 by Martin Felke (fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) November 27, 2016, 23:52 (GMT) |
fix for crash of loading files with split shards or island detection in fracture |
November 27, 2016, 15:28 (GMT) |
Enable multi-selection editing by default (Alt-key behavior) This means editing a property will now always affect all selected objects, bones or sequencer strips. Support for this was added in rBdfbb876d4660 but you had to hold the Alt-key to use it. The old behavior of only editing the active object will not be kept like decided in the 2.8 workflow meeting (reports comming). If you only want to edit the active object, you have to deselect others. There are still a couple of issues to be resolved (listed below), but having it enabled by default helps testing and getting used to it and should motivate us to fix them ;) To be fixed: * Give users hint when edits are applied to all objects/bones/strips ("Applying to x objects") - there are ideas but we need to finalize and implement them * Make it work better in corner cases (material editing, modifier property editing, etc) Note: Values usually override the initial value of the object/bones/strips, except of number buttons where it depends if you enter the value (absolute override) or drag the value (add value change). This behavior is consistent with multi-button editing. |
November 27, 2016, 13:33 (GMT) |
A number of other minor RNA fixes and precautionary safeguards against further crashes here |
November 27, 2016, 13:33 (GMT) |
GPencil RNA API: "set_active" option for layer.new() and palette.new() is now true/enabled by default To bring the API more into line with the UI (and the general expected behaviour of Blender when it comes to adding stuff), newly created layers and palettes will be made the active ones by default. It's possible to override this behaviour still (e.g. in cases where you're auto-generating a large number of them), but otherwise, this change will help prevent errors like T50123. |
November 27, 2016, 13:33 (GMT) |
Fix T50123 - GreasePencil: Modifying name of new color in new palette via bpy segfaults When there were no prior palettes, creating a new one didn't automatically make it active. This caused problems when trying to rename the color, as the RNA code assumed that if there's a color, it must come from the active palette. This commit partially fixes the problem by ensuring that if there are no palettes, the first one will always be made active. |
November 27, 2016, 13:33 (GMT) |
Typo fix |
November 27, 2016, 02:44 (GMT) |
Add cent_poly_v3 function |
|
|
|


Master Commits
MiikaHweb | 2003-2021