| Age | Commit message (Collapse) | Author |
|---|
|
When dragging in a vertical or horizontal region,
there is no need to detect the drag axis.
Gives minor usability improvement for dragging over vertical tabs.
|
|
Removes the need to keep your cursor over tabs while dragging.
|
|
|
|
|
|
drawing code to registering code.
In drawing it was pretty stupid (since we did not know *which* panels were
affected), and really, really annoyingly noisy!
|
|
The intention is to fix a too low default threshold on high DPI screen.
Users with high DPI screens that have increased the threshold to fix this
or liked the lower threshold will need to lower it again.
This is still somewhat of a guess, ideally this would be based on the
physical distance travalled, and maybe different per type of input device.
However we do not have access to this information, and hope this gives a
better default.
|
|
Jumping to data shouldn't necessarily change hidden status
or visible layers.
|
|
|
|
|
|
Suggestion from Right-Click Select: https://blender.community/c/rightclickselect/Npcbbc/color-ramp-flags-auto-distribution-function
Differential Revision: https://developer.blender.org/D3965
|
|
C code needed to be updated for module move.
|
|
Complex rigs are built from many bones (often overlapping)
connected by constraints.
When investigating or debugging such rigs one often wants to switch to
the target of a constraint, or a parent bone, but it is difficult to do
manually due to overlap confusion.
This adds a right click menu option that automatically selects
and makes the target object or bone active for UI fields where a
suitable reference is readily available.
|
|
This may improve reliability with left click select and pen input, assuming
that the place where the pen first touched the surface is closer to the
intended location than where it was released from the surface.
I'm not sure if this will make a significant difference in practice, but it
seems worth a try.
|
|
It is doable to get it to work, you just need to process it line
by line though, and get the right width of each one.
Disabling it for now since it is not implemented anyways.
|
|
|
|
|
|
Instead check which property has been set.
|
|
|
|
|
|
Without this bugs slip through that don't null check the descriptions
since many were set to empty strings.
|
|
|
|
|
|
Mentioned by Pablo on Blender Today : https://www.youtube.com/watch?v=67NIL5A-07c @ about 27:47
Differential Revision: https://developer.blender.org/D3902
|
|
|
|
Restrict these to displaying in tooltips.
|
|
Generating the keymap for the tooltip stopped shortcuts from running.
While this could be supported - the shortcuts show in the button,
so remove shortcuts from these tips.
|
|
|
|
Maniphest Tasks: T57737
Differential Revision: https://developer.blender.org/D3923
|
|
This should be purely an implementation change,
for end users there should be no functional difference.
The entire key configuration is in one file with ~5000 lines of code.
Mostly avoiding code duplication and preserve comments and utility
functions from the C code.
It's a bit long but for searching and editing it's also convenient to
have it all in one file.
Notes:
- Actual keymap is shared by blender / blender_legacy
and stored in `keymap_data/blender_default.py`
This only generates JSON-like data to be passed into
`keyconfig_import_from_data`, allowing other presets to load and
manipulate the default keymap.
- Each preset defines 'keyconfig_data'
which can be shared between presets.
- Some of the utility functions for generating keymap items still
need to be ported over to Python.
- Some keymap items can be made into loops (marked as TODO).
See: D3907
|
|
|
|
Makes it simpler to make some changes...
Also fix order of some includes (use alphabetical please).
|
|
That kind of implicit includes should really only be done when totally,
absolutely necessary, and ideally only with rather simple 'second-level'
headers.
Otherwise not being explicit with includes always end up biting in
unexpected ways...
|
|
Cursor motion was often causing redraws.
Distance to scrollbars that don't exist in hidden regions
caused redraws (for alpha fading).
Check if scrollbars are used before calculating fade.
|
|
While this shouldn't ever happen there have been reports
of tooltip creation failure - keep this until the issue is resolved.
|
|
|
|
Replace grease pencil specific brush select operator.
|
|
|
|
|
|
From own changes in that area... Now we also enforce handling shortcuts
in case relevant drawflag of searchbutton is set. Should allow to cover
all cases, hopefully.
|
|
|
|
- Vertex & weight paint now use the 'blend' setting.
- Weight paint now has it's own tool setting,
since weight paint doesn't deal with color - we'll likely
support different tools eventually.
|
|
D3894 by @charlie with edits
|
|
|
|
Differential Revision: https://developer.blender.org/D3891
|
|
|
|
As pointed out by Harleya in DevTalk. Thanks!
|
|
Resetting the theme to default would set the shadow brightness to 1.0f,
which was used as emboss when we used dark text on brighter backgrounds.
Now that we use white labels, bright shadows just makes all text fuzzy.
|
|
When use the template in the topbar for only select an ID is very annoying to have the buttons after the name and only adds noise to the selector.
This option hide the number of users, new and delete buttons to get a cleaner topbar selector.
By default the parameter is disabled in order to keep all existing code/UI running.
|
|
The new parameter allows to define the scale of the space.
|
|
Set the names to match the original order again, to avoid breaking addons and
various places in the code that relied on them.
|
