Hi Kurt,
I just wanted to make sure the probe controls fit, and they seem to.
Yes, I did want a click to go-to in the numerical display. There are some hardcore Gcode people who may not see the need, as there is the MDI, but I like convenience. There may be other action that can be used to replace repetitive Gcode commands, which beginners don't know anyway.
Perhaps the pointy jogs can be placed in a square button. Although the the button border may confuse they eye. In places placing legends inside arrows seem to improve recognition, and reduce visual clutter.
The Gmoccapy-style incremental indicators that you see everywhere were an excellent design by the designer of Gmoccappy. Once again, this interface is a blend of Axis and Gmoccapy, with some Hazzy, a touch of Craftsman and Touchy--all colored like Blender.
(I've had a cold, and have been struggling to get my CNC going, bickering with someone on the forum, but I want to track down the creator of Gmoccapy and post to him that the design of Gmoccapy has contributed greatly to this design. The thing is: it's really difficult sometimes to wear two hats. As established, there likely is not enough time for me to learn how to program this interface, so, as you said, I am concentrating on the design. The person who did Cmoccapy did both, and that's not easy. To be blunt and to the point: The one thing that Gmoccapy has not done: replace Axis. I had a friend stop by, look at Axis, and tell me that it looks like a Windows 95 program. No...no, that's not a compliment. Still, Axis is very useful and adaptable, and that is why it has endured and been expanded upon.)
Anyway, the incremental indicators have:
- Incremental buttons, that should be settable in the .ini
- A static text legend inner above
- A dynamic readout inner below
- Proportion indicators
The indicators are taken right from Gmoccapy, but add the static legend line.
Once again, the design of this interface:
- From the get-go be for 16x9 aspect ratio widescreen 1920x1080 and above for the future.
- Should be touch-compatible, which means long-presses instead of double-clicks.
- Should be modular with several sections to do different things.
- Should be made with open tools, so other can work on it.
As you might have read, I respect how much effort it will be to program this interface, and so, to the chagrin of others, I've wanted to get it pretty solid before moving forward. I don't see a big paradigm change. I am trying to decide if Pycam should be on the main menu.
One thing that's been a nagging detail for me: switching out some of the separator lines, when certain panels are changed.
"I always wanted to add a 'go-to' functionality in hazzy by typing into the DTG DRO! Do you intend to be able to set the work offsets by typing into the DRO too?"
.... As long as it can be done safely, that would be up to the programmer. Perhaps you can have a sit-down with him : )
Do you know both GTK+ and QT?
I am not asking because I want you to do both, it's just that my heart beats a little faster for GTK+
