8000 Apply the device's axis config when jogging by lagnat · Pull Request #439 · inkcut/inkcut · GitHub
[go: up one dir, main page]

Skip to content

Apply the device's axis config when jogging - #439

Open
lagnat wants to merge 1 commit into
inkcut:masterfrom
lagnat:fix/jog-axis-config
Open

lagnat wants to merge 1 commit into
inkcut:masterfrom
lagnat:fix/jog-axis-config

Conversation

@lagnat
@lagnat lagnat commented Oct 10, 2026
Copy link
Copy Markdown
Contributor

Jobs are mapped with the device's scale and swap_xy before being sent, but Device.move passes coordinates straight through, so the joystick follows the machine's raw axes. On a device with swapped axes the left and right arrows drive the media in and out instead of moving across it, so the same config means different things depending on whether you're cutting or jogging.

Maps each jog step into the device's axes first, in the order Job.create uses: mirror, then swap.

This is the identity for a device with no mirror or swap set, so nothing changes for configurations that work today. Done in the joystick rather than Device.move because job paths arrive already mapped.

Jobs are mapped with the device's scale and swap_xy before being sent,
but Device.move passes coordinates straight to the protocol, so the
joystick moves along the machine's raw axes instead. On a device whose
axes are swapped, such as a Silhouette Cameo, the left and right arrows
drive the media in and out rather than moving across it, and the same
device config ends up meaning two different things depending on whether
you are cutting or jogging.

Map each jog step from the direction the user sees into the device's
axes before moving, in the order Job.create uses: mirror, then swap.

The mapping is the identity for a device with no mirror or swap set, so
nothing changes for configurations that behave correctly today. This is
done in the joystick rather than Device.move because job paths arrive
already mapped and would otherwise be transformed twice.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@frmdstryr
Copy link
Copy Markdown
Collaborator

Needs rebased

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0