You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Octoprint with MMUs, the print files normally have appendices to discern them from single color code. In case of the Mosaic Palette series, this is .mcf, so the files created are named printfile.mcf.gcode.
As of now, ArcWelder will put its appendix directly in front of .gcode, which makes the generated files invalid for multicolour printing. I'm aware that it is possible to prepend a string. When sorting alphabetically, this comes with its downsides. Also, I think that the appendix is the proper or consistent way to identify the file's origin.
Could you expose the string that ArcWelder uses as appendix and make it editable? That way users can set their needed value like ".mcf.gcode" or ".mmu.gcode".
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi @FormerLurker
When using Octoprint with MMUs, the print files normally have appendices to discern them from single color code. In case of the Mosaic Palette series, this is .mcf, so the files created are named printfile.mcf.gcode.
As of now, ArcWelder will put its appendix directly in front of .gcode, which makes the generated files invalid for multicolour printing. I'm aware that it is possible to prepend a string. When sorting alphabetically, this comes with its downsides. Also, I think that the appendix is the proper or consistent way to identify the file's origin.
Could you expose the string that ArcWelder uses as appendix and make it editable? That way users can set their needed value like ".mcf.gcode" or ".mmu.gcode".
Beta Was this translation helpful? Give feedback.
All reactions