Age | Commit message (Collapse) | Author |
|
In 2.7x UV sculpt was a kind of sub-mode
(a toggle with it's own key-map & drawing code).
Move this to an operator that uses the tool-system,
this simplifies internal logic, especially brush selection
which now matches sculpt and other paint modes.
- Remove toggle used to enable uv sculpt.
- Expose the brush, which was already used but there was no way to
select different brushes.
- Make UV sculpt use paint paint tool slots
(using brushes how all other paint mode currently do).
- Move UV Sculpt keymap to the tools keymap.
- Remove Q to toggle UV sculpt mode,
S/P/G keys to switch tools.
|
|
Already used by install_deps.sh
|
|
In a separate step, all new functions should be added.
However, the best way to do this, is not clear yet.
A list of functions, that have to be added is available
in D4280.
Differential Revision: https://developer.blender.org/D4280
|
|
Suggested by Germano Cavalcante.
|
|
|
|
Use fields for properties
|
|
|
|
|
|
|
|
cases.
As exposed in T62406, we can have some rare cases of crashes due to
memory re-allocation happening outside of expected scenarii.
Ideally this should be re-designed, but at least keep track of those
known exceptions to general rules...
|
|
Needed for UI scripts to detect mixed weight paint + pose mode.
|
|
* Added a TL;DR first paragraph summarizing that one shall not keep any
reference to Blender data when modifying its container.
* Added some info about fact that adding items to some data containers
(like Collection) can also invalidate existing items (due to array
re-allocation).
* Added a Do/Don't example which shows a crash after adding some items
to a collection.
Related to T61297.
|
|
|
|
|
|
We don't attempt to have docs for all args, so don't warn about this.
|
|
|
|
Following removal from C source code.
See: 8c68ed6df16d8893
|
|
|
|
|
|
Needed for Python to easily support multi-object edit/pose modes.
|
|
We don't have this for other painting modes,
no need for a special case here.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Makes it clear seconds are not integers,
also avoids conversion to float.
|
|
|
|
`gpu_extras` was always visible
|
|
There is a new `bpy.app.timers` api.
For more details, look in the Python API documentation.
Reviewers: campbellbarton
Differential Revision: https://developer.blender.org/D3994
|
|
The HTML title did not make it clear that these are docs for the API rather
than a general Blender documentation. Some of the page titles were also too
long and redundant.
|
|
|
|
|
|
|
|
I think this example does not belong into the api docs and certainly not in the place where it was until now.
Maybe this can become a template in Blender but personally I don't see much value in it as an "official example" because it is hard to see what is going on exactly.
There are a few other examples that show how to use the GPUOffScreen object now.
|
|
|
|
|
|
|
|
found by Omar Ahmad
|
|
|
|
|
|
Technically this is only the view matrix, not model view matrix.
And view layer was missing from the pydoc.
|
|
- Was setting active state, making it necessary to backup/restore
active object in cases where this isn't needed.
Existing scripts are explicitly setting the active object when needed.
- Use a boolean select arg (toggle selection wasn't used anywhere).
- Add an optional view layer argument since scripts should be able to
operate outside the user context.
|
|
|
|
|
|
RNA's ViewLayer would present 'first level' of layer collection as a
list (collection property), when it is actually now only a single item,
same as the scene's master collection.
Note: did not try to update view_layer python tests, those are already
fully broken for quiet some time I guess (they still assume
view_layer.collections to be mutable e.g.)...
|
|
Was still 2.7x code... ;)
|
|
|
|
|