So I've spent the past few days ironing out some bugs in my existing code, and finally hunted down a bug that has been annoying me.
I've attached the latest build, which I think should work if you copy it to the KMotion/Release folder (I'm still using 4.35b, and the default file to open is hardcoded to that version, but the required setting file should be created in the current Release folder.
At the moment, the very basics work.
Layout is largely similar to KMotionCNC for now, with the main exception being everything is done via tabs.
You can config the interpreter for 3axis.
You can open GCode files, but not save any changes made in the viewer.
You can set the interpreter up in either Inch or MM (Master Units box on the config/trajectory planner page)
All settings/tools/offsets are stored to the default KMCconfig2.xml file, which should be created the first time any settings/tools/offsets are saved. This file can be changed, although I've just realised I've not added the required code so the latest config to be loaded is saved, so even if you create a new config file (you'll need to copy the default one manually for now), when you reopen KMoCNC it'll open the default file.
And having just tested that, I've realised I've not fully quashed that bug that was annoying me, so if you use the radio buttons to change between G20/21 or run an MDI, the g-code viewer will jump to line 2, and you'll need to click the restart button to reset to line 1
The viewer tab will possibly produce something viewable if your sample file sizes are big enough, but getting it working is well down my list of things I'd like to add, as I really need a clear run to try and learn about the C# drawing/graphics options.
The Tool Setting tab also does nothing, it was just thrown together a couple months ago so I could think about how it would work.
My next steps are to quash that &£"*£$*£ bug that's now annoying me more, then think about layout.
My goal is to have this touchscreen friendly, but I'm still quite undecided about offset/tool page layouts. The existing page layouts were just a lazy way to implement the mechanics, but it is all done in XAML so changes should be fairly easy.
For the main screen, I'm thinking more off a proper machine control type layout, with lots of buttons.
If anybody has any suggestions/ideas for the layout, I'd be interested to hear them.
I also have a couple ideas brewing for removing a lot of the need for manually created C programs, whereby you set everything via the app, and the app generates the required C program(s).
I don't expect anybody to spend much time testing this version, as it is very barebones just now, but if people could at least copy it to their Release folder, and at least let me know it runs, I'd be grateful.