Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado
  • ¿Algo no está bien?
#299 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
rust
Área
backend-api-design, desktop, documentation, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Rust
Estrellas
4
Forks
2
Merge medio
9 h 11 min
PR fusionados (30 d)
181

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cristim/AztecCraft

Todos los issues de cristim/AztecCraft

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.