| Age | Commit message (Collapse) | Author |
|---|
|
The issue was caused by some code accessing R from a functions which
are marked as safe for use from outside of render pipeline.
Now those functions are safe(er) for use.
|
|
Gives better context especially when operators have generic names.
|
|
Needed to support alternate search UI's, no functional changes.
|
|
Dont attempt to clip empty string
|
|
|
|
User request, this matches 2.6x behavior more closely.
|
|
|
|
|
|
|
|
Needed to allow modal UI keymaps, but I'm sure we'll need this more often in future.
First item will be modal eyedropper keymap coming in a following commit.
|
|
Steps to reproduce fixed glitches were:
* Change any editor to be file browser from menu, Ctrl+O *from the file browser area*, Esc -> area reset to what it was before changing to file browser initially
* Ctrl+O from any area, F12, Esc -> returns to initial editor in full-screen (expected is file browser in full-screen)
Fixes T46229
Core of the fix is removing old area from spacedata list when going back to previous area (see ED_area_prevspace -> BKE_spacedata_remove). Also, when creating a new temp area we now don't exit old area anymore (needed so SpaceFile->op is kept, but it also makes sense in general)
Aaand finally removes some ugly hacks.
Tested quite a bit, so I think it's safe to apply (besides of remark below), just would like to get things double checked and confirmed. After all, this full-screen stuff finally starts to feel like it's working :P
Note, there's still a memory leak when quitting Blender with temp area open. Haven't found out how to solve yet, but it's not that important for review anyway.
Reviewers: campbellbarton, brecht
Reviewed By: brecht
Subscribers: plyczkowski, Blendify
Maniphest Tasks: T46229
Differential Revision: https://developer.blender.org/D1531
|
|
wmOrtho2_region_pixelspace and wmOrtho2_region_ui were doing exact same thing since rBSa86482f81cf3.
|
|
|
|
- store layer lookup
- single hash adding to set
|
|
|
|
|
|
|
|
|
|
To be backported to 2.77.
|
|
usable, if still slightly offset
|
|
|
|
Splash and RC1 AHOY are incoming.
|
|
|
|
ked->iterflags actually already had an enum defined, but at the time of the previous
fix, I'd forgotten that it was defined. As a result, "f1 needs NLA remap" got given
the same flag as "include handles when doing keyframe selection checks".
|
|
|
|
In response to user feedback, this commit brings back the ability to
limit motionpath clearing to only happening for those on selected
objects/bones.
By default, the "Clear" operator will clear from all objects/bones,
unless the Shift key is held.
|
|
This feature wasn't exposed anywhere in the interface.
|
|
With continuous grab disabled, non-linear mapping for int buttons
wasn't working usefully with small mouse movements.
Now 2x pixels motion adjusts by at least 1 w/ int buttons.
|
|
Also name more clearly
|
|
|
|
Was confusing since zoom icons were used for add/remove elsewhere (color-ramp & presets).
|
|
|
|
|
|
|
|
This wasn't working and used extra undo steps.
|
|
Displaying a button would clamp the value if the button was outside the range.
This could be OK in some cases,
however it's problematic with object dimensions which would re-scale objects on showing the panel.
Add `ui_but_update_edited` when its OK to modify the value.
|
|
When selecting file-paths from the interface, initialize the 'Relative' setting from existing paths.
|
|
Having to change this with the slider each time isn't so convenient
and invert in this case does nothing.
|
|
|
|
Previously the grab brush could only move ourwards when normal aligned.
|
|
|
|
|
|
Don't use materials when showing weight colors.
|
|
object.
Also re-reported through IRC by Thomas Beck (@plasmasolutions), thanks.
Though it's not ideal in theory, we have quite poor handling of object datablock currently
from user PoV - before this commit, it was not easily possible to get fully rid of an object
anymore if you did not removed it from all its groups before deleting it.
So for now, restore 2.76 behavior (namely, unlink an object from avaerything in Blender
once it is no more used by any scene).
Better handling of all this is TODO for later (also related to much more heavy changes
done in id-remap branch regarding sanitizing our ID deletion process).
|
|
|
|
|
|
This generates warnings with MSVC. Similar typecast was
already done in other cases, so think it's all fine.
|
|
Was accessing already freed action in temp nodegroup animation data...
|
|
was broken
Thanks Alexander Romanov (a.romanov) for the fix!
|
|
Was drawing wire when mixed with non-wire nurbs.
|
