foreachthing
commented
2 years ago This is my workflow: I write the custom G-Code in Notepad++ anyways and there I do have G-Code highlighting. It's easier, faster and better beyond the simple textbox in PS. Also, I can store the files on SVN/Git/Cloud directory. I then copy the G-Code to PS.
But to add to your request:
- [TAB] should insert a TAB (or four spaces) and not tab to the next GUI element.
- A dropdown with the available placeholders (for easier insertion) for the active G-Code section could be provided.
- Make the textboxes taller, or scalable.
- Allow collapsing G-Code sections (i.e. I don't use Tool-Change nor Color-Change ... and these sections could be collapsed to use this estate for taller textboxes).
Is your feature request related to a problem? Please describe.
G-Code itself is quite simple. But syntax highlighting can help to make it easier to skim through. For example, comments might take a lot of space but they aren't important when you look at specific code.
Describe the solution you'd like Add syntax highlighting (possibly optional) to all G-Code editors in the app.
Describe how it would work wxWidgets tookit has wxStyledTextCtrl view that has syntax highlighting functionality.
It is based on Scintilla but apparently it (or, to be exact, its lexer) doesn't have a lexer for G-Code so it would be necessary to implement that too.
Although G-Code isn't necessarily hard to parse and prusa3d should have some sort of it in Prusa-Firmware.
Describe alternatives you've considered Using PS as it is, without syntax highlighting. Which isn't really an alternative
Additional context While we're at it, I'd point out to #5028 since this I made this issue partly because G-Code viewing/editing experience in PS isn't that great, to be honest, and it need some touch from a person who knows a thing or two about UX.