| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This makes it possible to do a border render inside a viewport even
when not looking through the camera.
Render border could be defined by Ctrl-B shortcut (works for both
camera render border and viewport render border).
Camera render border could still be defined using Shift-B (so no
muscule memory would be broken). Currently used a special flag of
operator to do this, otherwise you'll need to either two operators
with different poll callback or it could go into conflict with a
border zoom,
Border render of a viewport could be enabled/disabled in View
panel using "Render Border" option.
|
|
|
|
Was discussed in De Balie with lots of artists and we agreed it makes more
sense to behave this way
|
|
the camera could try include its own boundbox in its view.
now just skip the camera if 'All Regions' and lock view option is enabled.
|
|
view-selected.
|
|
quad-view),
currently not assigned to any keys.
|
|
function.
|
|
cleanup)
* Enum tooltips will only be detected in the case that we assign that as the
default property (ot->prop) of the operator. Set all of the offending properties
to get this status, since those operators would be useless without that property
anyway
* Improved the wording/capitalisation of a few of these tooltips and labels
|
|
rename V3D_PROJ_RET_SUCCESS -> V3D_PROJ_RET_OK
|
|
ED_view3d_project_float_ex function calls and cleanup cursor3d set function which had some odd logic.
|
|
|
|
|
|
view.
|
|
- make view3d project names more consistent.
- remove apply_project_float() its not needed.
- update comments referencing an old function name.
- move doxygen docs into the C file, prefer they are kept here to avoid getting out of sync with code.
|
|
|
|
also remove some redundant conversions int -> short -> int
|
|
|
|
|
|
var in math_rotation.c
|
|
|
|
|
|
|
|
- ColorBalanceModifierData wasn't aligned on 32bit systems.
- BM_vert_find_first_loop() was missing NULL check.
|
|
Additional changes:
- Option to the ndof menu letting you pick turntable/trackball independently
of the mouse viewport navigation style
- Option to change the rotation sensitivity separate from the panning
Holding shift + moving the ndof does just as before locking it to panning
Holding ctrl + moving will lock it to only rotation
Patch by Fredrik Hansson, thanks!
Reviewed by self and Mike Erwin.
|
|
into account
|
|
border zoom, view selected, view all.
|
|
pedantic report but may as well name them the same.
|
|
dont always want both.
|
|
|
|
views already
|
|
|
|
|
|
also some minor style cleanup.
|
|
|
|
|
|
|
|
also fix for building ghost test and fix double free in one of the tests
|
|
doesn't work if weight paint mode is active
Some operators like curve presets, color sample and some more were using object's
mode to distinguish in which mode user is currently painting. Such approach fails
in cases when there's paint mode active in 3D viewport and Image Editor.
Changed logic here to use some context's state like active space which helps
distinguishing current paint mode more accurate.
Ported all areas which uses paint_get_active() to new paint_get_active_from_context().
There're still some calls to paint_get_active(), but that shouldn't be harmful due
to that places indeed have object's mode as priority when getting paint mode.
|
|
replace do prefix with do_ for bool vars.
|
|
This commit adds some first building blocks for the two operators to work modally based on mouse input. To make their function easier, two hotkeys are introduced, Ctrl+B for bevel and I for inset.
TODO:
After discussion with Campbell, we would like to add scale-style line indicators for the operators. This is already done for transform operators but a new interface for mesh operations may have to be written using pieces from that code since, strictly speaking bevel and inset are not exactly "transform" operators.
Also, a better input method for inset is needed and more options exposed. The method implemented right now uses mouse move for thickness and ctrl-mouse move for depth. These are calculated using the distance of the selection center in screen space and the mouse position. While that may work and prevents abrupt changes in values when switching from thickness tweak mode to depth tweak mode, it limits the magnitude of values that can be put into the tool especially in small or large scale.
Alternatives until a better method is written include:
* use relative offset (works but may give strange results)
* tweak manually after the operation.
|
|
vector function edits.
|
|
DO_MIN/MAX re-reading same value from array 4 times when it can do once (use minf rather then MIN2, same for maxf)
|
|
|
|
|
|
a string.
|
|
tedious setting the object and bone manually (especially if you have it right in front of you)
uses keys
- Shift+PadPeriod --- to set
- Alt+PadPeriod --- to clear (also clears cursor and camera locking)
|
|
also use ..._find_name(..., name) rather then ..._find_named(..., name) --- both were used.
|
|
new image. (not use existing one)
|
|
also stop numpy from being found in /usr/include with cmake.
|
