Warn user of problematic gcode name

I discovered recently that gcode names beginning with “.” (and likely other characters) will slice and export perfectly well, but are invisible to the printer. It’s a small note, but could cause frustration to less tech-savvy users.

Thanks for sharing. That’s actually fascinating tidbit that might have some worthy side-applications. I’m wondering is such a thing could be exploited for other uses. Would mind showing a snippet of code example of what you mean? This could be one of those “Ah-ha” moments. :+1:

This is a throwback to some operating systems like Linux and Unix considering dot prefix files to be hidden.

Many first experience this with .htaccess files on PHP web servers.

This is why the ‘feature’ is often built into base file tables.

Come on @olias, the word is benefit rather than exploit.

:rofl:

Simply naming a file as follows would be an example of files becoming invisible to the printer.

.cube.gcode
.cube.3mf

Whereas the almost identical names without the period prefix would be perfectly visible.

cube.gcode
cube.3mf

Yeah maybe… but doesn’t exploit sound more like we’re getting something for free? And who doesn’t like free? :joy:

1 Like