That screen is 100% my own manual coding, actually.  I can’t quite get chatgpt to write gui code that works.

It only appears to work with standard lua and machine controls.

I had to change the screen layout to fit 16:9 but didn’t want to lose all the new real estate so i had to redo alot of it.  If you edit the xml file instead of use the screen editor gui it is alot faster and easier to organize.  I can share my screen with you if you like but it is super custom to my machine build

I've uploaded my update versions to google drive:

Changes made:
1.  Added a check in the M6 macro to make sure spindle is off before the draw bar release.
2.  Hard coded my rack positions into my M6 macro - Since this is very custom, I don't see the need to make use of .csv files.  Can just as well edit the script.
3.  Implemented to tool table pocket field.
4.  Updated the screen script to use be able to update the loaded tools.    Sort of a work around implementation - Not optimized at all, but not needed to be perfect.

Cool.

I have a tab and script that populates a screen with the current tools loaded in each slot (editable), their descriptions, an editable ‘notes’ section, the offset and a ‘clear offset’ button which sets the offset to 999.999 to trigger a re-measure.

One of the downsides of being 30 miles away from your cnc is that it is easier to fiddle with software than it is with the hardware. Thus things get prettier than that they need to be.

I’m still looking for a way to get the tool table to launch in a tab because the current pop up window is super tough to deal with using a touch screen. (It is basically impossible to drag windows around to see things).

If I may recommend - Use the tool table only as a backend system.  Write your own edit window - Like your doing now - Lets say you want to edit tool 13 -  You type it in, load the info from the tool table, edit the info.  save.   

I like your reset button..   

Good idea for the tool table. 

I will have my new friend chatGPT write a script to load/sync the tls tool library from Mach to the CSV-based tool crib that is used for Gwizard and post it here for folks to use for themselves.  The code it writes is often "too clever for its own good" and uses really complicated methods when something super simple would work instead.  It should work great for something like this though.

I think this is why it has a hard time with the GUI scripting.  I think that not all of the wx controls have been implemented in Mach, and there's no way for chatGPT to know which are implemented.  It would be really nice to have it build the tables for you.  I end up manually cut and pasting (lots of find and replace) the XML to get the screens I want.

Speaking of, here is the setc for my tool carousel tab.  The scripts for populating the entries are also in there.

I've also included a screenshot of how it looks like. 

Apparently I can't attach a setc file,

Here is the file as txt....