| Age | Commit message (Collapse) | Author |
|---|
|
We'll want some 3D shapes, so name existing shapes 2D
|
|
|
|
They weren't used anywhere,
both C & Py manipulators better assign to vars (no lookup needed).
|
|
Non-float properties should be editable too.
|
|
Naming was confusing, while technically correct -
the result is no scaling (manipulator ignores zoom-level).
Also remove 3D from name since this can be supported for 2D views too.
|
|
Rename:
- matrix -> matrix_basis
- user_scale -> scale_basis
- scale -> scale_final
Match RNA names being added to custom-manipulator branch.
|
|
Changes from custom-manipulator branch.
- use property type definitions.
- add property free callback.
- move properties into the wmManipulator struct (over alloc).
- use array length from property types instead of arg passing.
|
|
Naming was too confusing between properties of a manipulator
and properties it edits.
|
|
This makes manipulator access closer to operators,
and allows Python access.
This adds RNA for manipulators, but not Python registration yet.
- Split draw style into 2x settings:
`draw_style` (enum) & `draw_options` (enum-flag)
- Rename wmManipulator.properties -> properties_edit,
Use wmManipulator.properties for ID-properties.
Note that this area of the API will need further work since
manipulators now have 2 kinds of properties & API's to access them.
|
|
|
|
|
|
Remove type-specific axis functions.
|
|
This avoids having to use manipulator-type specific functions
to set the orientation.
And will make it simpler to access transformation from Python.
Currently the matrix is still used as an offset in places.
Also per-type orientation values still need to be removed.
|
|
- Option to start helper angle lines based on a vector
instead of the initial mouse coords (useful for bisect & spin).
- Option to show 2x helper lines
useful when dial is used to rotate an axis value.
|
|
|
|
Instead use generic 'WM_manipulator_new', adding a new 'setup'
callback (like wmManipulatorGroup.setup) used to initialize type vars.
This moves conventions closer to wmOperator and simplifies exposing to
Python.
|
|
|
|
|
|
Example that uses library widgets to control an operator,
the API hasn't been reviewed yet so this can be seen as a test.
|
|
|
|
|
|
- Add blentranslation `BLT_*` module.
- moved & split `BLF_translation.h` into (`BLT_translation.h`, `BLT_lang.h`).
- moved `BLF_*_unifont` functions from `blf_translation.c` to new source file `blf_font_i18n.c`.
|
|
INT_/FLOAT_MAX are sometimes valid choices, but most of the time more
sensible values should be used here!
|
|
|
|
Opted to keep includes if they are used indirectly (even if removing is possible).
|
|
|
|
Fixes T37700
Reviewed By: brecht
Differential Revision: https://developer.blender.org/D166
|
|
also check a similar case for bisect
|
|
|
|
|
|
|
|
update some descriptions, others were removed and operators tagged as internal.
add a script to detect duplicate operator descriptions.
|
|
|
|
|
|
already set or if there is no 3d view available.
|
|
|
|
(using cursor + numeric values was too clumsy for defining orientation).
once the cut is done numeric input still works as before
|
