Tool Box and quick layouts in documented order
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
The issue depends on unfinished work: icon slice B4 waits on the Move tool, and the Maya 2026 doc links are still being collected in slice A. Before starting, check the parity inventory and the pinned Maya reference in #5 to confirm the expected tool order. Done means the Tool Box order and disabled-with-reason states match that reference, with MCP tool schemas and .project-docs/mcp.md updated and a native screenshot reviewed.
Written by the indexing model from the issue text.
Description
Problem
Tool Box ordering and unsupported tools (Lasso, Paint Selection, Last Used) are not in documented order.
Current behavior
Icon slice B4 wiring is planned after Move lands.
Expected behavior
Tool Box in Maya's order with unsupported tools shown disabled, and quick layout buttons. The per-element Autodesk Maya 2026 doc links are being collected in the UI parity inventory (slice A, in progress); add them here when it lands.
Acceptance criteria
- Unimplemented controls stay visibly disabled with a reason; no dummy tools or controls.
- MCP coverage in the same change: implemented operations and relevant state exposed with synchronized tool schemas, real Editor protocol tests (scene token, draft, modal, close and busy guards) and updates to
.project-docs/mcp.mdand its coverage inventory. - Native visual check of the real window (screenshot reviewed), not only headless tests.
- Tests cover malformed, empty, boundary and failure cases; failed operations preserve the baseline.
- No parity claim without comparison against the pinned Maya reference (#5); unverified constants are documented as provisional.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 2
- Avg merge
- 2h 44m
- Merged PRs (30d)
- 59
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 cristim/AztecCraft
-
area/ui-parity type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cristim/AztecCraft#140 ·
Maintainers usually reply within 1 day
-
area/ui-parity good first issue type/docs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cristim/AztecCraft#85 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue type/docs
Difficulty 1/5 Under an hour Newbie friendliness 75/100
cristim/AztecCraft#79 · 1 comment ·
Maintainers usually reply within 1 day
-
area/selection area/viewport type/feature
Difficulty 5/5 Over a week Newbie friendliness 20/100
cristim/AztecCraft#135 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 22/100
cristim/AztecCraft#128 ·
Maintainers usually reply within 1 day
All issues in cristim/AztecCraft
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pop-os/cosmic-comp#2956 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
libp2p/rust-libp2p#6694 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EmbarkStudios/cargo-deny#910 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tursodatabase/turso#10054 ·
Maintainers usually reply within 1 day
-
build: Update rust versionPossibly taken A pull request linked to this issue is open or already merged. Opendependencies
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
ibm-granite-community/granite-cli#229 ·
Maintainers usually reply within 1 day