 |
|
|
|
Stores a collection of edit reasons associated with scene objects. More...
#include <journal.h>
Public Member Functions | |
| EsfJournal & | Add (const SdfPath &path, EsfEditReason editReason) |
| Adds or updates a new entry in the journal. | |
| void | Merge (const EsfJournal &other) |
Merges the entries from the other EsfJournal into this one. | |
| bool | operator== (const EsfJournal &other) const |
| bool | operator!= (const EsfJournal &other) const |
Iteration API | |
These types and methods allow EsfJournal to be used in range-based for-loops. | |
| using | value_type = _HashMap::value_type |
| using | iterator = _HashMap::iterator |
| using | const_iterator = _HashMap::const_iterator |
| iterator | begin () & |
| iterator | end () & |
| const_iterator | begin () const & |
| const_iterator | end () const & |
| const_iterator | cbegin () const & |
| const_iterator | cend () const & |
Stores a collection of edit reasons associated with scene objects.
Exec compilation uses an EsfJournal to log all scene queries performed while compiling a node or forming connections in the exec network. An instance of EsfJournal is passed to public methods of scene adapter interfaces (e.g. EsfPrimInterface::GetParent), and those methods add entries to the journal.
Given the scene adapter method calls made to produce a node in the network, the resulting journal contains all scene changes that would trigger uncompilation of that node. Likewise, when the exec compiler uses the scene adapter to identify the connections flowing into a node in the exec network, the resulting journal contains all scene changes that would trigger uncompilation of those connections.
| using const_iterator = _HashMap::const_iterator |
| using iterator = _HashMap::iterator |
|
inline |
|
inline |
Merges the entries from the other EsfJournal into this one.
If this journal and other have entries for the same path, then the merged entry contains the union of both reasons.
|
inline |
|
inline |
1.9.6