A Command step for injecting custom machine code, plus fixes
for SVG import, click positioning, jog soft limits, and Ruida
UDP on Windows
New Features:
- A new built-in "Automation" addon debuts with the Command
step: add your own machine code at any position in a layer's
workflow — one command per line, sent exactly where the step
sits (#449). Handy for pre-positioning the head, toggling air
assist between operations, or sending controller-specific
codes. Lines can use the same variables as macros, the text
is stored with the project, and a warning appears on machines
whose driver does not consume machine code (e.g. Ruida)
- The About dialog gains a GitHub Discussions button
Changes:
- Usage tracking (opt-in) now reports the host OS and one
anonymous machine event per configured machine, carrying its
type (driver, laser type, optical power, bed size, rotary);
each launch counts as its own session, and the consent
prompt was reworded. Machine names and identifiers are
never sent
Bug Fixes:
- SVGs that contain a DOCTYPE declaration, such as those
exported by Affinity Studio, import again (#484)
- Click to Zero and Click Canvas to Move Head round the
clicked position to the machine's precision, so the machine
can hit the requested position exactly; the ruler labels use
a font that fits them (#479, by atkaper)
- ruida-pa was upgraded to 0.21.2, fixing UDP connections
on Windows (#486, by StevenIsaacs)
- Jogs no longer reverse towards the nearest soft limit
when the reported position lies outside the travel range —
previously a single jog could drive an axis into its end
stop, e.g. on a Ruida RDC8445S reporting Z around 3176 mm.
Jogs heading further out of range are now blocked, jogs back
towards the range stop at the far limit, and the soft-limit
warning matches exactly (#488, by medoix)
