Move tool: center, plane and free handles, modifiers and middle-button moves
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- computer-graphics, desktop
Research direction
The payload names no source files, so start from the Move tool code and the Rust desktop editor it lives in, and read the linked Autodesk Move Tool documentation alongside the pinned Maya reference in #5. The .project-docs/mcp.md file and its coverage inventory are named in the acceptance criteria and must change in the same change. Done means the unsupported handles and modifiers are disabled with a visible reason, the implemented operations are covered by Editor protocol tests, and a native screenshot has been reviewed.
Written by the indexing model from the issue text.
Description
Problem
World-axis Move draws only the three axis arrows.
Current behavior
Plan for the landing Move slice: center/free/plane/middle-button moves and modifiers remain visibly unsupported; a modifier during a drag cancels it. Docs: https://help.autodesk.com/cloudhelp/2026/ENU/Maya-Basics/files/GUID-9BCE8B23-6DA6-4C7F-B897-7E25D6E8A865.htm (Move Tool).
Expected behavior
Plane and center handles, middle-button repositioning and modifier behavior once verified against the reference.
Acceptance criteria
- Unsupported handles are never drawn or accepted until implemented.
- 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 51m
- Merged PRs (30d)
- 84
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/viewport effort/s impact/internal priority/p3 severity/low triaged type/chore urgency/eventually
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cristim/AztecCraft#186 ·
Maintainers usually reply within 1 day
-
area/infra effort/s impact/internal priority/p3 severity/low triaged type/chore urgency/eventually
Difficulty 1/5 Under an hour Newbie friendliness 94/100
cristim/AztecCraft#181 · 1 comment ·
Maintainers usually reply within 1 day
-
area/modeling effort/s impact/many priority/p3 severity/low triaged type/bug urgency/this-quarter
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cristim/AztecCraft#176 ·
Maintainers usually reply within 1 day
-
area/modeling effort/m impact/many priority/p3 severity/low triaged type/bug urgency/this-quarter
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
cristim/AztecCraft#175 ·
Maintainers usually reply within 1 day
-
area/ui-parity effort/s impact/many priority/p3 severity/low triaged type/bug urgency/this-quarter
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cristim/AztecCraft#172 · 1 comment ·
Maintainers usually reply within 1 day
All issues in cristim/AztecCraft
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 3 days
-
[BUG] Filename sequence expansion (`+`) panics on numeric values exceeding `i32::MAX`Possibly taken @muntasir-396 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
CCExtractor/ccextractor#2402 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100