Please make G-code editor user selectable

[A_Camera]

Personally I like the G-code editor included in Mach4. It is free and is usable even if Mach4 is not used, no installation needed, just to copy gcedit.exe anywhere you want and associate all the files you want to associate with it. It is great in my opinion, and I would like to default to be changed to this, so that when I click on "EDIT FILE" button gcedit starts and opens the file.

[Derek]

I second this.

My work flow is: Open editor in UCCNC, Get mad, close screen editor and open file in notepad++.

[A_Camera]

Yes the built in G-code editor is pretty poor, and in my opinion pointless. It would have been better to have an option to select whatever you prefer, in my case that would be gcedit.

[ger21]

I hate the Mach4 g-code editor.
But I rarely edit my g-code at the machine.
To each his own.

[A_Camera]

Gerry, my point is not that it MUST have the gcedit, but that it should offer a flexibility. I guess that's not very important if you never edit G-code, but honestly, the way Mach3 solved this is much better. There is no G-code editor built in, uses Notepad by default and just change that to link to something else if you want to, whatever you prefer. I think in software like UCCNC, it is better to spend effort in functions specific to the UCCNC or milling or macro programming than simple G-code editors. Users should decide what to use for that simple task.

[A_Camera]

No, I disagree. What it needs is a simple option. OK to have an internal G-code editor, but in my opinion that's wasted effort which should be spend on important functionality. Personally I don't need a G-code debugger. I would more welcome a macro debugger.

[ger21]

in my opinion that's wasted effort .

Well, since they already created it, it would be wasted to abandon it. They probably shouldn't have bothered in the first place.

And I wasn't arguing against it. If I had the option, I'd probably just set it to Notepad, which simply does what I'd need it to do.

[A_Camera]

I don't mind if there is a built in editor, but most people don't write G-code directly and rarely debug G-code. I still think that effort concentration should be on the actual machining software and the interfaces, not on G-code editor. In any case, an OPTION to select your preferred editor tool is very easy to implement.

[Robertspark]

I read and edit it... me, I'd like notepad ++ haha... why reinvent the wheel...?

If they have a gcode editor with syntax / code checking, great... but it will need to be maintained in the future with new codes as they get edited.... suggestion make it use a txt file as the dictionary, with CSV or something for the syntax... that way anyone can add to it

[cncdrive]

What about writting a macro which starts a process with wait, of the software you guys want to use as editing.
The filename loaded is available in a DRO, so if a code editor accepts the filename as parameter to load on startup (like notepad does) then it is possible
to first get the file path and name information and then start the editor as process with passing the filename as parameter/command line argument in a format the editor requires it.
And then if started that way then the process will wait for exit.
If the editor gives different exit codes based on if the gcode file text was changed then it is easy to decide if the user changed the text and then the file can be simply reloaded by the macro.
Or if it does not give exit code about the text change then before starting the editor process first load the file into a string or string array and when the editor process closes then read the file again the same way and compare the 2 strings or string arrays. If they are not the same then reload the file with the macro.

I just liked to describe the way how a g-code editor could be called from macro and let you see that it is possible to code to use a different editor in a macro.