Welcome to LinuxCNC.org

loboy wrote:
Now we're taking it up a notch! It's GUI's like this that help us all in our designs to look more professional and up to date.

After having started deciphering the tcl myself I'd say revamping is an understatement. This look pretty well like a rip out of the old frames and rewrite.

I especially like how you've colored the buttons to make them functionally grouped along the top. Also moving the gcode preview under the backplot makes good sense as I've rarely seen wide g-code lines. As well it frees up quite a bit of space under the left button pane for growth when the additional axis come online, or adding (e.g.) AUX button for various M-Codes. (I was thinking this very same approach earlier this morning).

My eye was immediately drawn to the E-Stop, and active axis control - again smart use of color to draw attention to modal functions.

My only thoughts would be:
-I would hazard a guess that the bulk of EMC2 users only use up to 4 axis - this is worth a survey. Something I've done is added "A" axis to the end of XYZ line. That way XYZA is packed nicely together on a single line. HOWEVER, I'm not convinced that is the right way to go, as it can leave a mess when other axis come online.
- I do like that way AXIS attempts to organize buttons by functional group in the manual control tab, i.e. 1st axis group; 2nd spindle group; 3rd coolant group. It does follow workflow logic.
- The DRO definitely needs help, I'm interested in what your thoughts are for that.
- The Max Velocity slider is a waste of space. Once it's set for a machine when would someone ever need to change it. This is something that should be in the ini file.
- Tabs - may be a necessary evil. They provide growth, let's say we want to add a full blown tool management capability, a tab would be a nice place to put it.

Overall I'd say it has a trendy "Windows Metro" feel to it.

Jay

I have substantially rewritten the code. A lot of the variables and such were a mess to read, and figuring out the button states is headache. I did a lot of commenting.

As for the Axes, I made sure that when all axes are loaded it creates a nice neat 3x3 square, for XYZ, ABC, UVW, like a telephone keypad. This is easy to control with the gridding. Eventually I will pad out the buttons on the control panel.

Currently, the DRO is implemented weirdly. I still haven't deciphered as to why it was written the way it was. There are a lot of math functions operating on the font and the frame, and there is no simple way of changing one setting. I may just re-write it altogether.

The Button states are strange as well. Instead of being booleans, strings are passed around instead, which I don't like and it gets very confusing. At some point I may change this, but for now it is functional.

I agree that the Max Velocity is a waste of space as well.

I have made the code much more modular, so I can shift frames around the window, deciding on placement and such. Tkinter is not the most friendly, when it comes to gridding out the frames and packing stuff...

Eventually I am going to implement a preferences window for changing colors and such.

Thanks for the input about the Tabs. For me personally, I think if there needs to be expansion, I would rather pop a window instead. The tab coding is difficult to manage and not very friendly. It took me a while to figure out how things were being abstracted by the tabs. Plus the tabs are difficult to style.

I want the look to be more inviting and visually appealing, more like a real modern control panel. I always found myself trying to click these little buttons, but now the workflow is much faster as the buttons are bigger and easier to read. I have to say it is a pleasure to use my machine now. In the future, I may purchase a touch screen, so I sized the buttons accordingly.

I have pulled the MDI out of its tab as well. And I am starting to make that a bit more friendly. However, the History section does a weird rewrite to the window, and it is very distracting. I am still working out the kinks.

I'll post another screenshot soon.

Well I for one applaud what you're accomplishing, adding new life to an old friend.

Between what you're doing and where Chris is taking his I think we're going to see a new breed of GUI's for EMC2, and heaven knows we've been needing them.


Jay

While you are at it, consider splitting the"touch off" button into "Tool table" and "Coordinate set" touch-offs.
The number of times I have forgotten to change the drop-down and touched of the wrong way….

loboy wrote:
Hmm.. just thinking.. separate windows, moveable, but docked when out of the way, interesting. I can see the DRO in one of these.

The max velocity setting is for limiting Rapids during testing of programs.
I was toying with the idea of having the max velocity as a percentage and tie it to feed override when in single block mode.
The Okuma lathe I used was like.