MillMage 0.8.00 RC-6 Release Candidate

Rick · August 27, 2025, 6:27pm

The sixth Release Candidate of our new software for CNC users — MillMage — is available for download now!

Continuing the development of MillMage, this release candidate update includes many bug fixes and tweaks.

MillMage-v0.8.00-RC-6 - Change Log

Changes Since MillMage-v0.8.00-RC-5

Bug Fixes

Fail gracefully on DXF SPLINE objects with fit points (#1149)
Fixing logic for the tool length probe warning dialog to appear. (#1092)
Hiding unused values in probe settings, adding missing labels & tooltips in the probe wizard.
SVG ‘s’ command didn’t work for sequences of points (#1160)
Some probe values were not being saved to the config
Fixed bug causing bottom of main window to appear off screen on load.
Fixed issue with Operations Library not staying within saved dock location / creating a third dock row.
Fixed incorrect maximum size limit on MacOS toolbar buttons.
Fixed issue with toolbar icons having edges cut off.
Fixed issue that could cause main window to load on incorrect screen, sometimes many times larger than the screen.
Prevent top level menu keys from conflicting with hotkeys.
Fix to User cancelling GCode generation not actually cancelling.
Fixed crash on convert shape to bitmap if it was unassigned to an operation, show error message and abort instead.
Fixed crash on convert shape to bitmap if it was unassigned to an operation, show error message and abort instead. custom error message for LB vs MM
Ramp angle wasn’t saved/restored, is now also part of tool definition (#1162)
DEV-1881 Font skips around and reverts on Mac (#1147)
Qt6 set a 256mb max image size. No thank you. (#1181)
When pasting a copy of a PathShape, do not create Tabs unless the source cut had Tabs enabled.
MillMage wasn’t framing relative to workpiece origin (#1183)
Fixing the framing including shapes without operations, or with operation output disabled.
Fixed issue causing docks to consume entire window if operating system display scale is changed.
DEV-1445 Ellipse tool ovals are not exporting properly to DXF (#1178)
Stop button didn’t properly reset spindle/laser state to off. (#1174)
Updating the logic & text of the device size mismatch warning. (#1193)
Removing unwanted conversions for velocities. (#1173)
Extraneous Velocity Field Conversion, Revenge of Same (#1197)

Existing Feature Updates

Give stacked buttons a bit of forced extra width to allow side clicking (#1151)
Show a message if the user tries to calibrate axis while rotary mode is on (gantry)
Icons for Material Library functions (#1186)

New Features

DEV-78 Add font management dialog (#1007)
Custom gcode can now have escaped text sequences.
Make G20/G21 modals editable gcode blocks for custom gcode.
Remove mm/s as a device setting option.
Added Drag & Drop to move tools between categories in Tool Library.
Allow the user to save the position as a machine or workpiece coordinate

Miscellaneous

Allow user configuration of Z lift offset for TLO probe routine (#1161)
Remove ability to set Z=0 position

User Interface Updates

Selected shape / item dash length now scaled for screen dpi.
Better message for PDF Import Error to suggest converting to image before import.
Improvement to probe wizard to deal with zero Tool Diameter better.

MikeyH · August 28, 2025, 12:54am

Is there more to this?

Rick · August 29, 2025, 7:34pm

I have asked @goeland86 to provide some context.

goeland86 · August 29, 2025, 7:37pm

Essentially we realized we were letting users tell MillMage that the machine coordinate Z=0 was at the spoilboard level. This would lead to serious screw-ups in things like tool length probing routines, where when we don’t know what the length of the bit is, we try to go up at the top (or near) of the machine’s Z axis, to not hit anything sideways while re-measuring the tool length offset.

I hope that clarifies why?

If you have a router where G53 Z0 is the spoilboard, please do let us know, because that’d be a first, and also seriously odd from our perspective.

jeyeager · August 29, 2025, 11:20pm

Ooh. I was looking for this. I didn’t see how to do that in the documentation. Any detail on how that works?

MikeyH · August 30, 2025, 1:53am

Yeah, I had a conversation with someone about that. That is not how I learned it with the big machines.

goeland86 · September 3, 2025, 9:16am

If you look in the custom gcode tab, you’ll see you can select the escape character.
By default it’s the ^ You can change it, and whatever is in placed between those characters will be passed in verbatim.

So if you had a header that was something like

$H
G0 X0 Y-500 ; move to front for easy access to the spindle
^IF [something something]; THEN
G0 [X]{x} [Y]{y}
ENDIF
^

Essentially the gcode that will be sent will be exactly as you see it, minus the ^ before IF and after ENDIF.

jeyeager · September 9, 2025, 10:40pm

Looks like it’s still trying to validate whatever is between the square brackets. I can save it, but it doesn’t end up in the gcode.

goeland86 · September 10, 2025, 4:55am

OK I’ll double check with your macro, I thought I tested this fully but apparently there’s an edge case I missed.

goeland86 · September 11, 2025, 1:31pm

Ok yeah, it looks like something went sideways when several features were touching something in that part of the code.

Typical case of “too many cooks in the kitchen”. It should be fixed in the next RC.

system · October 11, 2025, 1:32pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.