E3 follow-ups: hidden layers outside ProcessEditor, clipboard edge cases, layer order, rotate handle
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- react, three.js, typescript
Research direction
Start by reading the E3 editing UX work in packages/editor-2.5d-react and inspect how ProcessEditor, EditorLayer, IsoCanvas, and ProcessSceneView handle visibility and clipboard events. The issue lists several distinct follow-ups but does not select one or define expected behavior, so clarify scope and acceptance criteria before making changes.
Written by the indexing model from the issue text.
Description
Follow-ups noted while landing lane E3 (editing UX) in packages/editor-2.5d-react:
- Layer visibility only applies where
ProcessEditor/EditorLayerrender the scene (edit and run mode). Other consumers (IsoCanvas,ProcessSceneViewused directly, viewers) draw hidden layers; they can filter with the exportedvisibleObjects(scene). Decide whetherSceneGraphshould filter itself. - Connector ends anchored to a part on a hidden layer resolve to nothing (the line disappears with the part).
- The system clipboard is written only by keyboard copy / cut (native
copyevent); a hosteditorRef.dispatch({ type: 'copy' })fills the editor clipboard only, so a later Cmd+V may paste older system-clipboard parts. - Layer reordering (drag rows) and per-layer draw order are not implemented;
zstays the draw-order control. - On-canvas rotate handle (today:
[/], inspector buttons, quarter turns only).
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 11h 21m
- Merged PRs (30d)
- 41
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 hyperdrive-technology/holodeck
-
area:ci review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
hyperdrive-technology/holodeck#208 ·
Maintainers usually reply within 1 day
-
area:holodeck review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
hyperdrive-technology/holodeck#207 ·
Maintainers usually reply within 1 day
-
area:holodeck review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
hyperdrive-technology/holodeck#206 ·
Maintainers usually reply within 1 day
-
area:holodeck review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
hyperdrive-technology/holodeck#205 ·
Maintainers usually reply within 1 day
-
area:holodeck review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hyperdrive-technology/holodeck#201 · 1 comment ·
Maintainers usually reply within 1 day
All issues in hyperdrive-technology/holodeck
Similar issues
-
area:agent-view area:tui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
anthropics/claude-code#104558 ·
Maintainers usually reply within 1 day
-
updater
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
UniversityOfHelsinkiCS/oodikone#5141 ·
-
maintanance
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
inmanta/web-console#7606 ·
Maintainers usually reply within 1 day
-
bug skills
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
equinor/fusion-framework#5846 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100