Node Editor: Minimap #86723
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
28 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#86723
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A mini-map is a bird's-eye of the entire node tree. A quick way to see in which area of the node graph we are.
The map is represented by a rectangle shape in the bottom right corner, its aspect ratio matches the editor size. It's background color matches the nodes editor's. It doesn't contain a grid.
Each node in the node tree is represented by a tiny rectangle in the map.
When zoomed in, the area is outlined:
Dragging this area will pan the view.
State
Active and selected nodes are highlighted:
Colors
Nodes could receive the color of its category.
Custom colors on nodes will take precedence over category.
Frames
When using frames, show the frame as a whole (coloured). Don't show the nodes inside the frame, as it can become too complex to read. Once there is a working prototype we can test and see if having the nodes inside works, but I'd start without the inside nodes.
The Minimap is shown by default but it can be hidden from the header via the Overlay icon and popover. The icon toggles all overlays, the popover includes options to toggle Minimap, breadcrumbs, and gizmos.
For the first prototype the minimap could be:
Added subscriber: @pablovazquez
Added subscriber: @KenzieMac130
Added subscriber: @PratikPB2123
Added subscriber: @lone_noel
Added subscriber: @tintwotin
Nice design. Question is, when implementing this, how to avoid generating inconsistency with all of the other editors(ex. animation editors), which also could need a mini-map, and keep Blender consistent?
Added subscriber: @MiroHorvath
Rather handy feature! Here's my 2cents:
"Nodes could receive the color of its category" - When looking at node tree from bird's view users care less about what particular nodes do(or what type they're of), more valuable information for them is to distinguish what bigger blocks of nodes do. Users typically represent such blocks by:
Would it be possible to color nodes by:
Added subscriber: @DuarteRamos
Added examples of frames and custom color nodes, and changed how to toggle the minimap on/off.
Added subscriber: @Ko
Errors shown as exclamation signs, maybe? And nodes which have only inputs or only outputs shown as triangle arrows.
Added subscriber: @elfoglalt
Added subscriber: @Blendify
This should also be placed in the upper right to be consistent with the 3D Viewport navigation helpers.
Added subscriber: @Harley
Could work!
Added subscriber: @ThinkingPolygons
Please don't.
Bottom right is the standard for this, and it's easier to reach. Also less clutter around the navigation gizmos.
Removed subscriber: @tintwotin
Added subscriber: @jc4d
Totally agree.
Added subscriber: @AndresStephens
A toggle for top or botton corner would be nice, I personally would prefer top right for muscle memory from visual widgets and also consistency with the rest. Keep up the awesome proposal! Hope to see this soon, from what I understand the drawing code from the editor is a tricky beast to do something like this, so best luck to you!
Added subscriber: @Eary
Input and output nodes are not like other nodes, the users should be able to recognize them is the minimap, right?
It looks like the in and output nodes are only recognizable in the category design, I think this might be problematic, because the category design is still up to debate, like what Miro said, but the in and output nodes need to be the anchor points for the users to know where they are in the node tree. Therefore I think the input and output nodes need to be recognizable even without the category design.
Another idea: While user holding a hotkey entire node view is replaced by this schematic minimap, and to move "rectangle of interest" user just moving mouse around so no need to click and drag it.
Added subscriber: @Strike_Digital
Added subscriber: @GeorgiaPacific
Added subscriber: @cmzw
Added subscriber: @Florian-10
thought this is going to be implemented in 3.0.
Looks like it was canceled :(
Verry sad
Removed subscriber: @cmzw
Added subscriber: @BD3D
Added subscriber: @dodododorian
Some inspiration:
I both love this idea and struggle with it.
The struggle is that this is a rectangular area that represents a special thing in a area of many rectangles. I want the purpose of it to read quicker. At the moment it doesn't scream "I am a min-map".
At the extremes, I imagine going into Nodes at first when there are no nodes. At this point it is an empty field, but there is also an empty rectangle at bottom-right, and there is nothing to explain the relationship. If I add a single node then I now have a singular rectangle in the center, and at bottom right is a rectangle with a rectangle inside.
Is it a consideration to NOT show the mini-map when it is not needed? That way it is not shown immediately and only appears when you zoom, have lots of content, etc. It would not add clutter at the start when it is a clean slate, only appears when it can assist. That might help explain its existence.
Had an idea for a while that if the overlaid version is not wanted, the mini map could be only shown on a hotkey. The user could hold the key down to turn the entire viewport into the minimap (basically zoom out to fit the entire node tree and show the view area as a rectangle), and while the key is held, moving the mouse would pan the view around (and scrolling zooms in and out).
This way you have the overview at the press of a button, you can spare a whole lot of mouse clicks and zooming that you'd normally need for navigation, with the bonus of no overlay constantly obstructing the viewport. Would be a convenient way to frame a group of nodes.
Added subscriber: @Nurb2Kea
Added subscriber: @MarinGoleminov
For me, the main job of the minimap would be navigating as fast as possible through large working areas, just like the navigator in Photoshop or Illustrator. One example of a nicely working minimap in node based apps is BMD Fusion: it can be toggled on and off, or switched to auto: if nodes are outside of the visible area, it appears. Usually, when building node trees, I mainly remember what function blocks are in which areas of the tree. Color coding on the other hand is not terribly important to me.
But honestly, even the most basic implementation in Blender would be very appreciated, as long as navigation is faster than now.
Added subscriber: @Low_Polygon42
Added subscriber: @blenderrocket
Added subscriber: @dodo-2
When release please ?
Added subscriber: @FDesimpel
Indeed. Why not have it as a panel in the sidebar?
Or even an editor / property editor tab in it's own right, with multiple minimap panels showing multiple nodegroups at once. That could also ease switching between groups on different objects, and keep view state per nodegroup that uses it.
Another possibility is in the modifier panel of the geonode, but i suppose soon there will be a generic geo(node) datablock where you don't need the modifier anymore.
Made a quick mockup to have this as a panel.
This way you could add additional ux functionality like zoom level buttons, stored views, etc...
Implementation wise, if done trough python, this would need a way to be able to draw to a panel using the gpu module, maybe trough a render to texture or something. Which would also benefit the Blender Apps project.
EDIT: Didn't realise there is already a patch being written for the original idea to have this in the main area ( https://developer.blender.org/D10776) , referenced back to this there.
I am removing the
Needs Triagelabel. This is under the general rule that Design and TODO tasks should not have a status.If you believe this task is no longer relevant, feel free to close it.