| Age | Commit message (Collapse) | Author |
|---|
|
Only back was possible.
|
|
- Clear deprecated flags for ID's:
Scene, Sequence, World, Object & Mesh.
- Clear deprecated flags for Spaces: outliner, 3D view & image.
- Remove unused `Mesh.drawflag`
- Remove unused `USER_ALLWINCODECS`, `USER_MMB_PASTE`.
- Remove `V3D_SOLID_TEX` & `V3D_ZBUF_SELECT` - used in a few areas.
- Flip `Object.empty_image_visibility_flag`
(avoids do-version on each new flag)
- Rename 'Backside' -> 'Back' in context of drawing - showing 'Back'
makes sense.
|
|
This adds the functionality requested in T59417 adding a new button near of pressure button of the brush to enable/disable occlude effect for eraser.
|
|
Thanks @billrey
|
|
|
|
Make the background of text editing fields dark to contrast with
selection and the cursor, similar to T59219.
|
|
|
|
No visible changes.
|
|
|
|
This commit adds support for new curve tool and adds more functionalities to the existing primitives, including new handles, editing, stroke thickness curve, noise, preview of the real stroke, etc.
Thanks to @charlie for his great contribution to this improvement.
|
|
The problem was the brush was not initializated because some code was missing (marked as ToDo)
|
|
|
|
Still T58986 not fixed.
|
|
Thanks to Charlie Jolly for find the bug.
|
|
probably an oversight in rBd40bffa17f6d
Reviewers: brecht
Differential Revision: https://developer.blender.org/D4079
|
|
Part of T59335.
|
|
Change default range to 0..2 to improve the slider behavior.
|
|
By default the text button background color was a similar brightness
to the cursor, making it hard to see at times.
Button types number/slider/text background brightness when editing
varied quite a lot too.
- Change the background while editing to match the number button.
- Darken the selection for greater contrast.
Resolves T59219
|
|
|
|
Generated names include the current context mode
which is irrelevant for generic 3D view tools.
|
|
|
|
Sets the header position for newly created windows with few exceptions
(preferences is always bottom, file-selector is always top).
|
|
|
|
Smooth a stroke, in edit mode, similar how mesh operator works with meshes.
|
|
In 2d655d3 the color picker was changed to use display space HSV values.
This works ok for a simple sRGB EOTF, but fails with view transforms like
Filmic where display space V 1.0 maps to RGB 16.292.
Instead we now use the color_picking role from the OCIO config when
converting from RGB to HSV in the color picker. This role is set to sRGB
in the default OCIO config.
This color space fits the following requirements:
* It is approximately perceptually linear, so that the HSV numbers and
the HSV cube/circle have an intuitive distribution.
* It has the same gamut as the scene linear color space.
* Color picking values 0..1 map to scene linear values in the 0..1 range,
so that picked albedo values are energy conserving.
|
|
This is now handled when versioning all startups.
|
|
|
|
|
|
We'll have to update that again once we move 2.8 to master...
|
|
|
|
Somehow those links were forgotten when we renamed API doc to simpler
names last year...
|
|
Now its possibly to ask for only keyboard/mouse/ndof events
when finding key map items.
|
|
use keyword argument
Fixes T59232
|
|
- Key-map items properties now override tool-options
so modifier keys can have different behavior to the default action.
- Box & circle select now have `wait_for_input` properties
instead of detecting this based on selection options being set or not.
This relied on the key-map setting properties which may need to be
initialize from the tool settings.
|
|
Some frequently used editors didn't have F-key access.
|
|
This reverts commit 1bf0a4f4d0d8c7e748f40d634aebf55eb37435ba.
This is a bug, clicks shouldn't remove rulers since it's too easy
to accidentally click instead of dragging.
|
|
Tweak events were masking hotkey access.
Reported in T55162
|
|
It was confusing to have two switches.
|
|
|
|
It's much simpler to just click on one end, than dragging it outside of
view. ;)
Related to T59084.
|
|
the interpolated one
One issue that especially newer users often run into is that they accidentally reset changes to the scene by switching frame without creating a keyframe first.
Therefore, this commit adds a new color that is used to draw properties if their current value differs from the one that would be set when switching to this frame.
This works both for existing keyframes as well as for currently interpolated frames.
Unfortunately the flags in but->flag are full, so I had to move the new flag to but->drawflag and pass that to all relevant functions.
I went with orange for the color since afaics it fits with the green and yellow that are currently used for keyframe states and since it's somewhat reddish to signify that there might be something to look out for here.
Reviewers: campbellbarton, #user_interface, brecht
Reviewed By: campbellbarton
Subscribers: brecht, predoe
Differential Revision: https://developer.blender.org/D3949
|
|
|
|
Having the hostname allows us to identify which machine rendered which
frame in our render farm.
This simply uses the host's name, and doesn't do any DNS lookup of any
IP address of the machine. As such, it's only usable for identification
purposes, and not for reachability over a network.
Reviewers: sergey, brecht
Reviewed By: sergey
Differential Revision: https://developer.blender.org/D4047
|
|
Fixes T58922
Reviewers: brecht, billreynish
Maniphest Tasks: T58922
Differential Revision: https://developer.blender.org/D4046
|
|
|
|
Show folders and start in the users home.
|
|
Differential Revision: https://developer.blender.org/D3926
|
|
|
|
|
|
|
