Feature discussion: synchronizing layer visibility across views
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading issue #2448 and compare its view-level synchronization proposal with the technology-based approach described here. Investigate requirements for technology-shared layer visibility, visibility groups, and undo behavior. Done means the requirements and preferred architecture are documented well enough to guide a later implementation.
Written by the indexing model from the issue text.
Description
From the discussion in #2448 (a view-level "synchronized layers" button, like "Synchronized views" but for layer visibility).
There, @klayoutmatthias proposed taking this to a feature discussion first, with these starting points:
- synchronizing on technology objects instead of views: a technology keeps a layer properties map with a dynamic bidirectional update path between technology and view, so all layouts sharing one technology stay synchronized; less intrusive than view-level sync and avoids some of its logic issues
- possible synergy with visibility groups, which are currently emulated with tabs: a technology-global visibility state with presets could address several requests at once
- undo: layer visibility in the main undo stack is contentious; candidates are dropping it from undo or giving it a separate stack
The view-level approach from #2448 is one data point, the technology-based scheme the other candidate. Opening this to collect requirements and settle the architecture before any (re)implementation.
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 305
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 11
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from KLayout/klayout
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
KLayout/klayout#2554 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
KLayout/klayout#2412 · 3 comments ·
Maintainers usually reply within 1 day
-
DRC functions not working properly with clip in placePossibly taken @klayoutmatthias claimed this today. Openbug
KLayout/klayout#2553 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
Maintainers usually reply within 1 day
-
Deep DRC can miss violations when a cell has many shapesMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
KLayout/klayout#2546 · 5 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
LaneDibello/Kotor-Patch-Manager#375 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day