GraphiteEditor / GraphiteEditor/Graphite
Edge case where moving layers between groups changes the location, rotation or scale on the canvas
- Vorherrschende Sprache
- Rust
- Sterne
- 27.2k
- Forks
- 1.3k
- Ø Merge
- 20 Std. 5 Min.
- Gemergte PRs (30 T.)
- 57
Beschreibung
Recently I've spent more time working in Graphite and I want to make a point about one of the current design decisions.
Individual layers have their transforms set relative to parent node transforms. When such layer is moved outside of the parent into a different location in the nodegraph it changes its position on the canvas. It is really frustrating to work around this mechanic, and I believe many people will have similar opinion, especially those that come from other 2D apps.
Two solutions that might work here:
- make every layer have its transforms as absolute values relative to canvas origin (0,0)
- recalculate transforms when the layer is moved into a different place in the nodegraph so it's location, rotation and scale does not change
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
No file or test is named. Start by tracing how layer transforms are stored relative to parent nodes and how moving a layer between nodegraph groups is handled. Done means moving a layer preserves its canvas location, rotation, and scale.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- rust
- Bereich
- computer-graphics
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100