Create "Active” file?

[tonejaco]

Seems like the first task is to move all the unused gcodes to another directory effectively removing them from the list. Might be nice to be able to access them in a separate tab for reference. Just moving them to a different directory is an easy way to disable them as they may need to be reactivated at some point in the future.

[parachvte]

I want to keep the resources/_gcode in sync with the original repo (regularly).
And overwrite key/values in resources/_gcode_overwrite.

A script in Rakefile needs to watch file changes and re-generate _gcode for us.

Maybe add a key "show" or something to change the visibility, and use labels to distinguish whether the G-code is for original Marlin, Snapmaker or both.

[tonejaco]

Maybe there's a way for the script to "omit" adding the gcode files that are in an "inactive" file to the sm-sidebar. Better still because there are probably more files needing omitting then the file is for "active" gcode files. You could have a separate tab in the navbar to show all or show inactive ones?

[tonejaco]

Changed name to better reflect the issue.
I think it will be much easier to change active/inactive status in one file rather than have to edit in multiple locations, i.e. the individual files. This might also set up a mechanism for displaying specific sets of G/M codes like if you want to see just the commands relative to leveling, laser, CNC, etc.

[parachvte]

This might also set up a mechanism for displaying specific sets of G/M codes like if you want to see just the commands relative to leveling, laser, CNC, etc.

Great idea!

[tonejaco]

I've created an Active-SM file and an Active-ALL file to start off and I'll play with it on my fork. They are just lists of the file names in the gcode directory.
Need to figure out how to switch between the different Active files. That way the gcode folder doesn't have to change, just the sm-side nav contents.
I was also thinking that it would be nice if the sm-side nave section could just be it's own separate file and didn't need to be included in every gcode file. Maybe that's not possible or feasible? That would make it easier to switch between different Active menu lists.