#include "BKE_collection.hh"
#include "BKE_lib_override.hh"
#include "BLI_function_ref.hh"
#include "BLI_listbase_wrapper.hh"
#include "BLI_map.hh"
#include "BLI_utildefines.h"
#include "BLT_translation.hh"
#include "DNA_space_types.h"
#include "RNA_access.hh"
#include "RNA_path.hh"
#include "../outliner_intern.hh"
#include "tree_display.hh"
#include "tree_element_label.hh"
#include "tree_element_overrides.hh"
#include <stdexcept>

Classes
class	blender::ed::outliner::OverrideRNAPathTreeBuilder

Namespaces
namespace	blender

namespace	blender::ed

namespace	blender::ed::outliner

Functions
Base Element
Represents an ID that has overridden properties. The expanding will invoke building of tree elements for the full RNA path of the property.
static void	blender::ed::outliner::iterate_properties_to_display (ID &id, const bool show_system_overrides, FunctionRef< void(TreeElementOverridesData &data)> fn)

Helper to build a hierarchy from an RNA path.
Builds a nice hierarchy representing the nested structs of the override property's RNA path using UI names and icons. For example `animation_visualization_mothion_path.frame_end` becomes: Animation Visualization Motion Paths End Frame Paths are merged so that each RNA sub-path is only represented once in the tree. So there is some finicky path building going on to create a path -> tree-element map. This is more complicated than you'd think it needs to be. Mostly because of RNA collection overrides: A single override may add (and in future remove) multiple collection items. So all operations of the override have to be considered. The order of collection items may matter (e.g. for modifiers), so if collection items are added/removed, we want to show all other collection items too, in the right order. If the override is inside some collection item, the collection item has to be built, but the RNA path iterator doesn't
static BIFIconID	blender::ed::outliner::get_property_icon (PointerRNA &ptr, PropertyRNA &prop)

Classes

Namespaces

Functions