GraphiteEditor/Graphite

Edge case where moving layers between groups changes the location, rotation or scale on the canvas

Open

#3,195 建立於 2025年9月19日

在 GitHub 查看
 (12 留言) (0 反應) (0 負責人)Rust (25,662 star) (1,176 fork)batch import
Good First Issue

描述

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

貢獻者指南

技術棧
rust
領域
frontend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Node graph basicsTransform math
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
Investigate how layer transforms are currently stored relative to parent nodes in the node graph. The issue proposes two solutions: either store transforms as absolute values relative to the canvas origin, or recalculate transforms when a layer is reparented so its visual properties remain unchanged. Examine the existing code in the graph engine and transform handling (likely in files like `graphite/src/../node graph.rs` or similar) to determine the feasibility and impact of each approach. Review the discussion in the 12 comments for additional insights from maintainers.