|
Blender V5.3
|
Establish and manage Outliner trees for different display modes. More...
#include "DNA_listBase.h"#include <cstdint>#include <memory>#include <utility>#include "BLI_assert.hh"#include "BLI_function_ref.hh"#include "tree_element.hh"Go to the source code of this file.
Namespaces | |
| namespace | blender |
| BMesh Iterators. | |
| namespace | blender::ed |
| namespace | blender::ed::outliner |
| namespace | blender::ed::outliner::detail |
Enumerations | |
| enum class | blender::ed::outliner::StripAddOp : int8_t { blender::ed::outliner::Noop = 0 , blender::ed::outliner::Add , blender::ed::outliner::None } |
Functions | |
| template<typename ElementType, typename... Args> | |
| ID * | blender::ed::outliner::detail::element_owner_id (Args &...args) |
| template<typename ElementType, typename... Args> | |
| const void * | blender::ed::outliner::detail::element_persistent_ptr (const TreeElementAddParams ¶ms, Args &...args) |
Establish and manage Outliner trees for different display modes.
Each Outliner display mode (e.g View Layer, Scenes, Blender File) is implemented as a tree-display class with the #AbstractTreeDisplay interface.
Their main responsibility is building the Outliner tree for a display mode. For that, they implement the #build_tree() function, which based on Blender data (#TreeSourceData), builds a custom tree of whatever data it wants to visualize. Further, they can implement display mode dependent queries and general operations using the #AbstractTreeDisplay abstraction as common interface.
Outliners keep the current tree-display object alive until the next full tree rebuild to keep access to it.
Definition in file tree_display.hh.