| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Align the lower side of the navigation gizmo with the top of the icons.
|
|
This addresses crowding in the top right area of the view
with the existing header and tool header.
D5670 by @CandleComet
|
|
Avoids calculating the visible part of a region whenever
on-screen overlays are drawn.
|
|
This was done intentionally so mouse press events tools didn't prevent gizmos
receiving click events before `USE_GIZMO_MOUSE_PRIORITY_HACK` was added.
|
|
- Add 'Navigation Buttons' preference, used for 2D views
(previously this couldn't be disabled).
- Add "Off" option for 3D view axis.
- Support minimal axis with navigation buttons.
|
|
|
|
In preparation for view navigation gizmos.
|
|
Existing functions were written to match the setup_keymap callback.
Add versions that can be called with the window manager for convenience.
|
|
Don't use plural because single/multiple isn't relevant
for keymap definitions and reads badly for specific gizmo types
that only use a single gizmo.
|
|
Minor changes to recent gizmo click/drag logic 08dff7b40bc6a
Changing the gizmos highlighted part in the invoke_prepare
callback is too error prone since it needs to run
before it's known which operator will execute.
Add back 'drag_part', since it simplifies click-drag use.
While this isn't essential with custom keymaps per gizmo
it avoids having to define a keymap in the case a drag
event needs a different action.
|
|
Remove click-drag support for tweak gizmo,
rely on keymap events instead.
This is needed for some gizmos to use modifiers keys
without having all gizmos use all modifier keys (see: T63996).
|
|
User request to see axis even when in camera view,
it's also useful when the camera is locked to the view.
|
|
Apply clang format as proposed in T53211.
For details on usage and instructions for migrating branches
without conflicts, see:
https://wiki.blender.org/wiki/Tools/ClangFormat
|
|
Gizmo's now have their own popover in preparation
for making transform gizmos accessible without having to use tools
See: T63518
|
|
Match the UI naming (changed since 2.7x).
|
|
Using white with low alpha made it hard to use on a white background.
Since the axes themselves highlight to white.
|
|
- Avoid using white with low alpha to make grey.
Note that this is the second time we've run into this problem: T59626.
- Use a light backdrop when the icons are dark
so they're visible over a black background.
|
|
While \file doesn't need an argument, it can't have another doxy
command after it.
|
|
Move \ingroup onto same line to be more compact and
make it clear the file is in the group.
|
|
BF-admins agree to remove header information that isn't useful,
to reduce noise.
- BEGIN/END license blocks
Developers should add non license comments as separate comment blocks.
No need for separator text.
- Contributors
This is often invalid, outdated or misleading
especially when splitting files.
It's more useful to git-blame to find out who has developed the code.
See P901 for script to perform these edits.
|
|
|
|
|
|
Bright backdrop would get lost when having bright elements/background in the viewport.
This makes it use a darkened/lighten version of the theme space header color.
Since icons are colored using the 'text' value of the Theme Space, it's likely that any
theme is going to have a contrasting background color, but just in case darken/lighten it slightly.
|
|
'mp' was a reference to 'manipulator'
|
|
This will look a bit better once the icon outline is gone.
|
|
I had to make the viewport navigation icons a bit smaller in the SVG since
the edges were being clipped off, we only support 16x16 icons currently.
They are a bit blurry because of this.
|
|
|
|
- Only show axis backdrop when hovering.
- Move closer to the screen corner.
|
|
|
|
|
|
Simplify the default navigation gizmo.
See: T54723
|
|
|
|
Edit doxy files and header guards only.
|
