Can't help you with your problem Ray, but when you get it done I hope you will share it with us.
Sounds like a neat screen.
Thanks,
RC
I will do that. I'm actually looking forward to getting this done. I've always found myself flipping from screen to screen while working, which is a PITA. I'd go from Program Run, to MDI (usually just to do one move), and to Offsets (to do edge-finding, etc.). I've now got touch probes and macros to do all the touch-offs and set DROs (tool length, edge finding in X+/X-/Y+/Y-, and center-finding on circles and pockets). All of that will now be on the one page, along with much larger DROs, G-code and toolpath displays, spindle, coolant and feedrate controls and over-rides, and more. The buttons will all be nice and large, so it should work well with a touch screen. My hope is that this one screen will provide every function I need for 99% of my day-to-day work. I will probably just put this into the 1024.set screenset in place of the standard Program Run screen, so all the functionality on the other screens will still be there when/if needed.
Once you've figured out how to deal with scream4 (which is quirky, to say the least...) actually creating the screen is really not difficult, nor does it take terribly long. The time-consuming part is going to be creating all the many, many necessary bit-mapped graphic elements it is constructed with. This is something I have about zero experience with, so it'll be a learning experience.
Regards,
Ray L.