Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

MCP pointer_hit ignores the active Rotate/Scale tool; Pick Range follow-ups from #298

Aperta
  • Qualcosa non va?
#299 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
backend-api-design, desktop, documentation, testing

Direzione di ricerca

Start in src/app/features/move_tool.rs and trace how pointer_hit selects handles; compare it with the active tool’s native hover and press hit_test paths. Add an Editor protocol test for each tool and a diagonal scale tie probe, then pin the disabled-handle tie order. Update row 14 in .project-docs/development.md and the known-issues wording; done when all five follow-ups are covered by the tests and text.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area/mcp area/viewport effort/s impact/few priority/p2 severity/medium triaged type/bug urgency/this-quarter

Follow-ups from the claude-fleet and CodeRabbit reviews of #298 (Refs #295, Pick Range 8 px).

  1. Bug: MCP pointer_hit always reports Move axes. The inspection's pointer_hit (MoveViewportInspection, src/app/features/move_tool.rs) is computed from the Move handles even when Rotate or Scale is the active tool, so an MCP client hovering a Rotate ring or a Scale box gets a Move axis (or nothing) instead of the handle the native hover highlights. Expected: pointer_hit reports the active tool's handle, using the same hit_test as the native hover and press, with an Editor protocol test per tool.
  2. Unpinned nearest_disabled tie order. When two disabled handles are equidistant, the later one in iteration order wins. No test pins this; pin it (or define it) with a test.
  3. Row 14 quote drops a sentence. The constants table row 14 (.project-docs/development.md) quotes Line pick size without its second sentence ("The pick size should be the same as line size, so you can identify which handle will be picked by the size of the ring."). Quote it in full.
  4. known-issues wording (CodeRabbit). Disabled handles consume a click with the "unsupported" status only when no enabled handle wins the overlap. At some oblique Scale-plane corners an enabled axis is within 8 px, so the axis takes the click. Qualify the sentence.
  5. A real diagonal tie probe (CodeRabbit). scale_picks_x_on_the_diagonal_and_the_dead_zone_corner_stays_empty probes (7.5, 7.5), where only X is eligible because the Y shaft runs toward negative screen Y in the front view. Add a probe between the X and Y shafts, e.g. (7.5, -7.5), so the tie-break rule decides the result, plus (8.5, -8.5) as the outside probe.
Lingua principale
Rust
Stelle
4
Fork
2
Merge medio
8h 5m
PR unite (30g)
157

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cristim/AztecCraft

Tutte le issue di cristim/AztecCraft

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.