| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Noisy and annoying with new gcc5...
|
|
Since these FCurves for these properties cannot be deleted, this operator is useless
in this case.
|
|
|
|
It was possible to perform actions while performing a drag-toggle.
|
|
|
|
Caused entering an invalid number to leak.
|
|
|
|
|
|
|
|
|
|
Not such a nice solution, but good to have this working.
|
|
Conflicted with Alt for editing multiple values.
This could also conflict with global frame change at times.
|
|
Mouse wheel was used as home/end.
Was annoying since it could happen by accident.
|
|
This would enable multi-value-editing in the middle of the drag action.
|
|
|
|
Some of them are just brain dead code, some are potential bugs.
|
|
|
|
Currently re-uses node-flag (which is only used to tint color too)
|
|
|
|
Add basic support (holding Alt) to edit all selected objects/bones/sequences.
|
|
|
|
In practice this isn't useful (for scale especially).
For float buttons with a very large range, don't attempt to match the snap to the range.
|
|
|
|
D1031, implement proposal T37478 to give easy access to the online manual.
Use Alt+F1 while hovering over a button/setting.
|
|
Tooltips for buttons in the Outliner could overlap the Outliner's RMB
menu in some cases (and there's no way to get rid of the tooltip again).
This disables the button's tooltip before creating the menu (as we do it
for the normal RMB menu)
|
|
In addition to the unlink icon to clear a value,
When cleared, show an eyedropper to select objects or object-data
(was already available via the EKey).
|
|
Our current keymap doesn't give us enough room to make such changes in
the event system. To fix small issues caused by this, we would need to do
drastic changes in Blender's keymaps and internal handling. It was worth
a try, but it didn't work.
I can write down a more descriptive statement in a few days, but for now
I need a break of this stuff.
|
|
Design task: T42339
Differential Revision: D840
Initial implementation proposal: T41867
Short description:
With this we can distinguish between holding and tabbing a key. Useful
is this if we want to assign to operators to a single shortcut. If two
operators are assigned to one shortcut, we call this a sticky key.
More info is accessible through the design task and the diff.
A few people that were involved with this:
* Sean Olson for stressing me with this burden ;) - It is his enthusiasm
that pushed me forward to get this done
* Campbell and Antony for the code and design review
* Ton for the design review
* All the other people that gave feedback on the patch and helped to
make this possible
A big "Thank You" for you all!
|
|
tab-completing textedit buttons.
We now have a specific flag for that, use it! Note that for all 'search menu' buttons,
there is already a similar behavior, so there is no need to force apply butt in this case
anyway, which means in practice this change only has effect in the single place
it is needed currently - file browser dir/file fields.
In this case (dir field), applying button even on partial matches leads code
to ask to create a new dir, which breaks completely the expected behavior of
completion. And we do not need immediate apply at all here.
Note this is the only 'autocomplete' button not using search menu, so this change
does not affect anything else in UI.
|
|
For me, weird characters are drawn if IME is enabled but translation
is not set to a supported language.
Could become an utility function if needed later.
|
|
|
|
Internal change only,
use UI_BTYPE_SEARCH_MENU with an unlink flag instead.
They are really the same button type, one just happens to have the option to unlink.
|
|
Based on HSV ordering, SV+H had S<>V swapped.
|
|
was used because of UI memory access only.
|
|
|
|
|
|
Useful for UI handling where its common to check multiple modifiers at once.
|
|
|
|
Campbell once told me such checks can cause warnings on some compilers, so
let's try to avoid them.
From the theoretical view, this check works quite different than the old
one, but in this case everything should work just like previousely.
|
|
D1019 by @gregzaal (minor edits by me).
Thanks for the patch!
|
|
|
|
Auto-opening of pulldown menus didn't take overlapping popups into account.
|
|
|
|
Currently this is mainly useful for picking camera DOF depth.
- EKey over a distance field prompts you to pick a depth from the camera.
- WKey (Specials menu) to pick from the 3D view (when the active camera's selected).
|
|
was accessing freed menu region.
|
|
Currently, code just checks whether a text-edited button uses a given icon (VIEWZOOM) to decide to apply changes on each typed char.
This patch adds a propper button flag (UI_BUT_TEXTEDIT_UPDATE) and a dedicated RNA flag (PROP_TEXTEDIT_UPDATE) for that.
It's also now usable not only for text buttons, but also for example for num buttons when in 'text edit' mode, etc.
It also fixes an actual bug, which is for text properties, in 'immediate' mode, hitting escape would not restore org value, because `ui_apply_but_TEX()` would set its orgstr to NULL on first call (giving it to `but->rename_orig` instead of copying it).
Note no change in behavior is expected from user POV.
Update for addons using that 'VIEWZOOM' icon 'feature' will follow (if any).
Reviewers: campbellbarton
Reviewed By: campbellbarton
Projects: #user_interface, #bf_blender:_next
Differential Revision: https://developer.blender.org/D938
|
|
|
|
We could now also remove the win->ime_data assert in wm_window_IME_end,
but think it's better to leave it for further development.
|
