Open tyeth opened 2 years ago
Hey @tyeth I like those ideas. I'm planning a major update to the extension for v0.8.0 and working towards a 1.0 release that takes more advantage of the machine type choice and possibly even uses a comment at the beginning of the file to dictate to the extension what type of machine tool the code is for.
This issue has been automatically marked as stale because it has not had recent activity.
Suggest a Feature you'd like to see
I wish that my 3d printing gcode files would load in treeview happily. I don't think it serves much purpose, so maybe it could just be disabled instead in 3d printing mode.
The files I use are silly sizes (line count) and include a comment that is a base64 encoded image (64kb) so also silly line length. I wondered while reading the closed issue #23 if it couldn't be more gracefully handled if the file contains Layer markers as comments. If that was the case then the tree could collapse the commands under sections based on layer number.
Additional context It's worth noting that octoprint (or maybe one of its plugins) has a couple of regular expressions to match the majority of slicers / gcode flavours regarding layer comments.
Sample file header (from Luban i.e. Cura) and first few lines of skirt / layer zero: