Hi Ron , conversational programming it not just for a few simple projects. It is a modern programming interface that is used widely in the machine tool world. Pretty much the wave of the present and future. Best to get on board the train NOW. You have to think beyond a few newbies trying to figure Gcode programming out(;-)
To make it a best seller you will have to cater to both the beginner as well as the seasoned pro.
If you want tool tables to be SIMPLE you have to treat them that way. Just display the entire tool table and leave it up to the programmer on how best to implement them. I just loaded up the entire 255 entries as a test, looks fine from here.
I don't have problems using the tools tables they can be a handy tool. BUT just like using an ATC you just have to make sure they are loaded correctly(;-)
The empty dia trick is used a lot by people that use the tables as a programming TOOL.
So if you can write the summary to the Gcode, why not give the option to send it to a printer?
?
""It is an interesting thought to create a separate file with just the wizard input data. """ NOW YOU ARE THINKING, that is the summary data you need to be able to print(;-). Tool data, feeds,speeds,ETC,anything that can be a reference to someone that has NEVER seen the project before having to run it.(;-) We used to get handed jobs all the time that we personally had never run before. THe summary allowed us to verify the setup BEFORE running the code.
Each project we do that is not CAM generated we have to hand write all the important data that will stay with the project file for life. THat simple idea will save tons of work over the years.
The trick here is to give access to ALL the handy tools of conversational programming for the pro yet keep it simple in context so it does not LOOK overwhelming to the beginner.
The new interface DOES look and work WELL, Good Job. Please remember I am not picking on you, just trying to help you along and help test things when I can.
(;-) TP