Gscreen - a GTK / Glade / Python based screen
23 Feb 2013 04:46 #30460
by tjamscad
Replied by tjamscad on topic Gscreen - a GTK / Glade / Python based screen
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.
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.
Please Log in or Create an account to join the conversation.
23 Feb 2013 04:50 #30461
by newbynobi
Replied by newbynobi on topic Gscreen - a GTK / Glade / Python based screen
Halo Chris,
can you include in tooledit widget an function like so:
I would need this to select the tool to change within the tooledit widget.
Regards Norbert
can you include in tooledit widget an function like so:
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
Please Log in or Create an account to join the conversation.
23 Feb 2013 05:17 #30462
by tjamscad
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.
Replied by tjamscad on topic Gscreen - a GTK / Glade / Python based screen
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.
Please Log in or Create an account to join the conversation.
24 Feb 2013 01:59 #30489
by cmorley
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
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...
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...
Please Log in or Create an account to join the conversation.
24 Feb 2013 02:02 #30490
by cmorley
Yes but not till Monday probably.
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
Halo Chris,
can you include in tooledit widget an function like so:
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.
Please Log in or Create an account to join the conversation.
24 Feb 2013 06:28 - 24 Feb 2013 06:51 #30504
by newbynobi
Replied by newbynobi on topic Gscreen - a GTK / Glade / Python based screen
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
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
Last edit: 24 Feb 2013 06:51 by newbynobi.
Please Log in or Create an account to join the conversation.
24 Feb 2013 08:14 #30505
by newbynobi
Replied by newbynobi on topic Gscreen - a GTK / Glade / Python based screen
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
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
Please Log in or Create an account to join the conversation.
24 Feb 2013 08:36 #30507
by newbynobi
Replied by newbynobi on topic Gscreen - a GTK / Glade / Python based screen
Hallo Chris,
why there are 4 digits on tool_edit_widget, even idf I am working in metric units?
Norbert
why there are 4 digits on tool_edit_widget, even idf I am working in metric units?
Norbert
Please Log in or Create an account to join the conversation.
24 Feb 2013 14:36 - 24 Feb 2013 14:36 #30513
by cmorley
Because at the moment the tooleditor widget doesn't convert units. and it's hard coded for 4 digits.
Chris M
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
Hallo Chris,
why there are 4 digits on tool_edit_widget, even idf I am working in metric units?
Norbert
Because at the moment the tooleditor widget doesn't convert units. and it's hard coded for 4 digits.
Chris M
Last edit: 24 Feb 2013 14:36 by cmorley.
Please Log in or Create an account to join the conversation.
25 Feb 2013 21:43 - 26 Feb 2013 06:40 #30561
by tjamscad
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?
2. Set override is not always needed on screen?
3. There some type of signal showing when each axis is homed?
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.
5. When an alarm situation happens running a program the program goes back to the start?
6. Can there be a wear offset column added to the tool edit page?
7. Can there be a diameter comp column added to the tool edit page?
8. Can touch to scroll through menus and programs like on I-phone?
9. When editing a program can the line you are editing be highlighted?
10. Can there be a conformation screen for the program restart, this helps to avoid errors?
11. Could the scroll bars be bigger for better use with fingers?
12. Can the button borders be thicker to have more definition between buttons?
13. Can you remove the text "Select Buttons" from the right column of buttons.
14. Why is the mm/in button on the screen if it is set in preferences?
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?
17. How can I get the Machine on , machine off button Indicators back?
Replied by tjamscad on topic Gscreen - a GTK / Glade / Python based screen
Chris,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...
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?
2. Set override is not always needed on screen?
3. There some type of signal showing when each axis is homed?
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.
5. When an alarm situation happens running a program the program goes back to the start?
6. Can there be a wear offset column added to the tool edit page?
7. Can there be a diameter comp column added to the tool edit page?
8. Can touch to scroll through menus and programs like on I-phone?
9. When editing a program can the line you are editing be highlighted?
10. Can there be a conformation screen for the program restart, this helps to avoid errors?
11. Could the scroll bars be bigger for better use with fingers?
12. Can the button borders be thicker to have more definition between buttons?
13. Can you remove the text "Select Buttons" from the right column of buttons.
14. Why is the mm/in button on the screen if it is set in preferences?
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?
17. How can I get the Machine on , machine off button Indicators back?
Last edit: 26 Feb 2013 06:40 by tjamscad.
Please Log in or Create an account to join the conversation.
Time to create page: 0.383 seconds