Implementation: since nodes can be reused, transform info cannot be stored in node; thus either a separate tree structure should be present or transform can be re-calculated each time node is re-selected. The latter seems to be a better choice, at least for now.
(same applies to timeline editors)
Implementation: since nodes can be reused, transform info cannot be stored in node; thus either a separate tree structure should be present or transform can be re-calculated each time node is re-selected. The latter seems to be a better choice, at least for now.
To be implemented properly, we'll need to have a common way to reference node position (universal analogue of QModelIndex), which could then be used for renderers, editors etc. See caryoscelus/rainynite-core#56
To be implemented properly, we'll need to have a common way to reference node position (universal analogue of QModelIndex), which could then be used for renderers, editors etc. See https://notabug.org/caryoscelus/rainynite-core/issues/56
caryoscelus
(same applies to timeline editors)
Implementation: since nodes can be reused, transform info cannot be stored in node; thus either a separate tree structure should be present or transform can be re-calculated each time node is re-selected. The latter seems to be a better choice, at least for now.
To be implemented properly, we'll need to have a common way to reference node position (universal analogue of QModelIndex), which could then be used for renderers, editors etc. See caryoscelus/rainynite-core#56