| Age | Commit message (Collapse) | Author |
|---|
|
Edit doxy files and header guards only.
|
|
This is a common, short, distinctive term often used for this purpose.
Changes to internal API's still needed.
|
|
|
|
Support for adjusting a setting from the last executed operator.
|
|
Allows for each workspace to have it's own add-ons on display.
Filtering for: Panels, Menus, Keymaps & Manipulators.
Automatically applies to add-ons at the moment.
Access from workspace, toggled off by default
once enabled, add-ons can be white-listed.
See D3076
|
|
Rename to WM_manipulator_group_type_poll,
use convention of other poll functions.
|
|
|
|
|
|
|
|
|
|
Makes the 3D view navigation widget easier to use: dragging anywhere
in the rotation region now rotates without having to avoid the XYZ axis
hotspots which only activate on a single click.
Logic for drag detection is complicated by manipulators reliance
on keeping the modal operator running.
Currently this is wrapped in an ifdef,
we may want to implement it differently later.
|
|
|
|
While not the main purpose of manipulators, it's handy to be able
to use operators without modal callbacks sometimes.
|
|
Also move descriptions into doxy header
|
|
Caused glitch with Scale-Cage tool.
|
|
Name wasn't right since this only unlinks from manipulator maps.
|
|
Running spin or bisect twice in a row added widget groups each time.
|
|
This reverts commit 134e927965c9871df8a9e13806f1cd48f4d43f16.
Writing into const event is very bad,
but this change broke compositor manipulators.
Will look into better solution eventually.
|
|
A single manipulator could only assign a single operator to each part.
Now each part can have it's own.
Also modify 2D selection callback, 2D started at 1, 3D at 0.
Now use -1 for unset value, start both at 0.
|
|
|
|
Re-use operator return flags for manipulator modal & invoke,
this means manipulators can allow navigation or other events to be
handled as they run - see T52499
|
|
|
|
- WM_manipulatorgrouptype_remove- > free
- WM_manipulator_group -> WM_manipulator_group_type
Naming here is still a bit confusing,
now at least free/remove are differentiated.
|
|
Duplicating strings caused problems using strings in
both struct hash and manipulator group types own hash.
|
|
|
|
|
|
|
|
Split up manipulator free & unlink, so freeing window data doesn't
run callbacks that might use freed data.
|
|
They weren't used anywhere,
both C & Py manipulators better assign to vars (no lookup needed).
|
|
Manipulator enum types are easy to confuse, use typedefs.
|
|
- Cleanup array access, move into functions.
- Store allocated size to avoid realloc's on every add/remove.
- Make select editable from Python.
- Rename select callback to select_refresh
(collided with select boolean).
- Call select_refresh when de-selecting as well as selection.
|
|
This matches operators naming and should avoid confusion in future if we
want to use active as term for last-selected.
|
|
|
|
Manipulators which are registered before UI initialized would have their
keymaps initalized twice (duplicate keymap items).
|
|
Was only handling keymap items when the cursor
was hovering over a manipulator.
|
|
|
|
|
|
|
|
Avoids lookups on each access.
|
|
|
