#13 Canvas editors: apply transformations

Cerrada
aberta %!s(int64=7) %!d(string=hai) anos por caryoscelus · 1 comentarios

(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.

(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
Accede para unirte á conversa.
Cargando...
Cancelar
Gardar
Aínda non existe contido.