fix(ipc): rotate_component uses absolute angle (matches schema) (#159)
* Fix: IPC rotate_component now uses absolute angle as documented The IPC rotate handler was adding the angle to the current rotation (relative), but the schema documents it as absolute. This caused unexpected behavior where setting angle=0 had no effect on a component already at 180°. Now correctly sets the rotation to the exact angle specified, matching the SWIG backend behavior. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * docs(changelog): add unreleased entry for rotate_component absolute-angle fix --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -6,6 +6,13 @@ All notable changes to the KiCAD MCP Server project are documented here.
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
- **`rotate_component` now treats `angle` as an absolute target rotation**,
|
||||
matching its schema description. Previously the IPC backend added the
|
||||
supplied angle to the current rotation, so two consecutive
|
||||
`rotate_component(angle=90)` calls would rotate the part to 180° instead
|
||||
of leaving it at 90°. Workflows that relied on the additive behavior will
|
||||
need to be updated.
|
||||
|
||||
- **Project-scope `sym-lib-table` is now visible to symbol-discovery tools**:
|
||||
`search_symbols`, `list_symbol_libraries`, `list_library_symbols`, and
|
||||
`get_symbol_info` previously only consulted the global `sym-lib-table`. A
|
||||
|
||||
Reference in New Issue
Block a user