Gscreen - a GTK / Glade / Python based screen

Thank you for all your hard work Chris

tjamscad wrote:

This is the list I have so far from the shop and Stuart.

Thank you for all of your hard work on this project.

1. Ignore limits should hide until a limit has been tripped?

I will look into that.

2. Set override is not always needed on screen?

Most of the time I would say yes it does- You could use it in manual MDI or Auto modes. If you had direct' hardware knob' adjustments
then you wouldn't need them- Guess it depends on your preferences and machine

3. There some type of signal showing when each axis is homed?

I'll look into that - color change is popular or an asterisks

4. In the field showing machine position I like to see a 'distance to go' for each axis? Could you move the graphics screen to where the position is and the position stuff to where the graphics are now. That would make more room for the position information for the DTG and more than 3 axis's. Plus since you have the full graphics button you dont nessarly need a large graphics window.
Perhaps maybe remove the graphics window and make it show like the "display aux screen" under preferencs.

I assume from your discussions that your machinists don't care much about the graphics. I agree it would be much more useful if it could
pre-run the program without moving the machine.Having the graphics pop up as a separate window is not very practical as it covers screen controls.
Having it on a separate monitor would work well, but I bet not a lot of people wish to use two monitors for their machine.
Changing the size of the window is the best compromise. I will have to build some concept screens.

5. When an alarm situation happens running a program the program goes back to the start?

That's a hard one to fix reliably I think. I could keep track of the last line that linuxcnc keeps track of, but I don't think it is terrible accurate. I think the highlight line is not always displaying what actually happenning - I will do research..

6. Can there be a wear offset column added to the tool edit page?

Thats another hard one to fix reliably. I could add this to my widget and fake it to linuxcnc, but it would be easy to write a program to break it, which would not be fun! We need linuxcnc to understand the concept of wear offsets. Nobody I know of is working on that.

7. Can there be a diameter comp column added to the tool edit page?

I am not sure I know exactly what you mean - unless you are referring to wear offsets for diameter - same problem as above.

8. Can touch to scroll through menus and programs like on I-phone?

No the widget toolkit (GTK) does not understand gestures (that's what they call the I phone type finger movements.) I understand they are working on adding this to GTK3 but thats not coming to linuxcnc anytime soon anyways

9. When editing a program can the line you are editing be highlighted?

Probably -I will have to research

10. Can there be a conformation screen for the program restart, this helps to avoid errors?

I ca add this yes.

11. Could the scroll bars be bigger for better use with fingers?

This is controlled by the GTK theme, which can be customised. I have not tried that, and really don't have the time. - maybe someone else will build a nice machine control theme

12. Can the button borders be thicker to have more definition between buttons?

Same - controlled by GTK theme

13. Can you remove the text "Select Buttons" from the right column of buttons.

Yes

14. Why is the mm/in button on the screen if it is set in preferences?

Preference page button is for the way it's displayed when you first start Gscreen each day, the front page one is for at-the -moment choice.

15. On the offset page when you select edit it make the background of the G5X and G92 yellow?

16. The spindle speed background color I cant change from the tan color?

Not sure why - it seems to work fine for me. It may have to do with you using 12.04 (I do not at the moment) I will look at that in time but probably not soon

17. How can I get the Machine on , machine off button Indicators back?

By editing the Glade file and then the handler file. I can probably dig up the samples but if you do that then you have to do that editing each time you update Gscreen - better to wait till you are going to install a version you won't update every second day The changes are pretty easy. Finding a spot for the button is the hardest thing.

The pace of development is going to come to a stop fairly soon (a week or so) as I have a maintenance shutdown at work that will keep me busy. It will resume after that (a couple a weeks)

newbynobi wrote:

Hallo Chris,

could you add another feature to the tooledit_widget?

I would like to hide the buttons (delete ; add, reload and apply).
It is just because it's appearance don't fit with my design.
I will rebuild the buttons in my bottom main button list.

I am beginning to code a part where all bottom and left button can be connected to hardware button,
so all main functions of the GUI can be used without an touch screen, just with hardware button placed on the left side and under the screen.

This is the way it is done in many industrial controls.

At the moment I hide the button like so:

self.btn_tool_delete = self.widgets.tooledit1.wTree.get_object("delete")
self.btn_delete.set_visible(False)

I would prefer doing it like so:

self.widgets.tooledit1.hide_button("delete",True)

Norbert

Norbert
If you want all the buttons disappeared, hide the box they are in, hbuttonbox1
I could create a 'convenience' method to help do this too, if you like.

Chris M

newbynobi wrote:

Hallo Chris,

I think I found a solution for the tool_change problem, switching in Mdi and back in Manual mode.

I made the following:

I declared self.wait_tool_change = False in __init__ (Line 78 in gmoccapy_0.7.04)

When pushing the button to change the tool, I set self.wait_tool_change = True
and switch to MDI mode. (line 968)

and in hal_status_interpreter_idle (line 1134)
I ask:
If self.wait_tool_change == True:
and then I switch back to manual mode

It is sure not the perfect way, but it seems to work.

Norbert

What I have done is similar. I have Gscreen check if it's in manual mode. If it is and if linuxcnc is not in manual mode, it changes it to manual.
I do it in the hal_status_interpreter_idle function too. So far So good...

What I have done is similar. I have Gscreen check if it's in manual mode. If it is and if linuxcnc is not in manual mode, it changes it to manual.
I do it in the hal_status_interpreter_idle function too. So far So good...

But you didn't push the changes jet, didn't you?

Norbert

Hallo Chris,

changing a tool, from tooledit widget, brings an error:

"Tooledit widget float error"

Does this happen, because I use German settings for the decimal separator. "," instead of "."

I make all tool changes now from the widget.
If you push my index_tool button or the change_tool button the tooledit widget get visible and you select the tool you like from the list.
The selected tool is then changed.

Yes, please make the function to hide the buttons.

Norbert

newbynobi wrote:

What I have done is similar. I have Gscreen check if it's in manual mode. If it is and if linuxcnc is not in manual mode, it changes it to manual.
I do it in the hal_status_interpreter_idle function too. So far So good...

But you didn't push the changes jet, didn't you?

Norbert

Yes I have already pushed them, last week I think

pushed your method and the hide_buttonbox:

tooledit.hide_buttonbox(True)

must be done after tooleditor show all()

Let me know if it doesn't work for you.

Chris M

newbynobi wrote:

Hallo Chris,

changing a tool, from tooledit widget, brings an error:

"Tooledit widget float error"

Does this happen, because I use German settings for the decimal separator. "," instead of "."

Norbert

maybe.

tempararily remove the try: exception: and print statements around line 169
then the true error message will show

Chris M

I will check all your comments later, I will be a few days off.

I think mah/master is back at the moment, that is why I haven't got the changes.

Norbert