Gscreen - a GTK / Glade / Python based screen

tjamscad wrote: Chris,

Comments from Stuart:

1. I think the 'ignore limits' button should not be on the front page. It should be under another menu or button.

2. What is the function of the 'set override' button? It should probably not be on the first page.

3. Is there some type of signal showing when each axis is homed? That is nice to see.

4. In the field showing machine position I like to see a 'distance to go' for each axis. That can be a preference and maybe be combined with one or more axis position displays.

This seems to be along the same line as what "newbynobi" was pointing out.

I agree 'ignore limits' should only show when jogging mode is active.
'set override' is always shown. it should probably be only shown when the "set up", "MDI" and "program" modes are selected
There is an symboly when the axis is homed but it doesnt shown each axis. Maybe the icon by each axis button would work?
I tried the DTG that is in the preferences but it didnt work for me. It could be something I did wrong.

Ignore limits may be a bit annoying on another page. It resets after a jog move, so if your not off the limit switch you would need to re select it again.
Of course in a proper running machine this should be rare... Maybe hide it till needed?

I could make the read out show something - default Gscreen does.

I didn't add distance to go option in Industrial yet. It would replace relative or absolute (I run out of space to show all three).

I am away this weekend so can't do any work on Gscreenn till Monday night...

newbynobi wrote: Halo Chris,

can you include in tooledit widget an function like so:

Code:

def get_selected_tool(self): liststore = self.model def match_value_cb(model, path, iter, pathlist): if model.get_value(iter, 0) == 1 : pathlist.append(path) return False # keep the foreach going pathlist = [] liststore.foreach(match_value_cb, pathlist) # foreach works in a depth first fashion if len(pathlist) != 1: return None else: return(liststore.get_value(liststore.get_iter(pathlist[0]),1))

I would need this to select the tool to change within the tooledit widget.

Regards Norbert

Yes but not till Monday probably.

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:

I would prefer doing it like so:

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

Norbert

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

Hallo Chris,

why there are 4 digits on tool_edit_widget, even idf I am working in metric units?

Norbert