Gscreen - a GTK / Glade / Python based screen
09 Jun 2013 23:07 #35463
by jlviloria
Replied by jlviloria on topic Gscreen - a GTK / Glade / Python based screen
It is because that when you select the option run-from-line, is selected 0, and type in the required line erases the 0, must pass on any of GScreen skin as it is the same widget.
We always delete zero, although we had not noticed the error, we configure it by typing "enter" run a program, and so far no errors. clarified that always delete the zero. but default it is selected.
jorge
We always delete zero, although we had not noticed the error, we configure it by typing "enter" run a program, and so far no errors. clarified that always delete the zero. but default it is selected.
jorge
Please Log in or Create an account to join the conversation.
09 Jun 2013 23:10 #35464
by newbynobi
Replied by newbynobi on topic Gscreen - a GTK / Glade / Python based screen
it does not matter what interface you use, it will happen on gscreen and industrial and gmoccapy too, because all of them use the same widget.
Norbert
Norbert
Please Log in or Create an account to join the conversation.
10 Jun 2013 00:04 #35465
by cmorley
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
Just pushed the fix for this.
please check for any problems ( though I tested what i could think of)
Thanks
Chris M
please check for any problems ( though I tested what i could think of)
Thanks
Chris M
Please Log in or Create an account to join the conversation.
10 Jun 2013 01:41 - 10 Jun 2013 01:42 #35468
by newbynobi
Replied by newbynobi on topic Gscreen - a GTK / Glade / Python based screen
Halo Chris,
I added the following code to gmoccapy_handler.py
if I do enter the tool edit page, I call the code and get the tool in spindle marked, ready for editing.
I do beleave, it would be fine to add this to the widget itself as set_tool(self,toolnumber), what do you think?
Norbert
I added the following code to gmoccapy_handler.py
def _set_tool(self):
liststore = self.widgets.tooledit1.model
def match_tool(model, path, iter, pathlist):
if model.get_value(iter, 1) == self.data.tool_in_spindle:
pathlist.append(path)
return False # keep the foreach going
pathlist = []
liststore.foreach(match_tool, pathlist)
# foreach works in a depth first fashion
if len(pathlist) == 1:
liststore.set_value(liststore.get_iter(pathlist[0]),0,1)if I do enter the tool edit page, I call the code and get the tool in spindle marked, ready for editing.
I do beleave, it would be fine to add this to the widget itself as set_tool(self,toolnumber), what do you think?
Norbert
Last edit: 10 Jun 2013 01:42 by newbynobi.
Please Log in or Create an account to join the conversation.
10 Jun 2013 01:47 #35470
by newbynobi
Replied by newbynobi on topic Gscreen - a GTK / Glade / Python based screen
Halo Chris,
I just checked your patch.
I could not find any more errors or strange behavior.
Norbert
I just checked your patch.
I could not find any more errors or strange behavior.
Norbert
Please Log in or Create an account to join the conversation.
10 Jun 2013 02:23 #35471
by cmorley
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
Thanks for testing Norbert.
Ok yes I added set_selected_tool(toolnumber) to the tooledit_widget
It also highlights the line.
Hope that's what you wanted.
Chris M
Ok yes I added set_selected_tool(toolnumber) to the tooledit_widget
It also highlights the line.
Hope that's what you wanted.
Chris M
Please Log in or Create an account to join the conversation.
10 Jun 2013 02:26 #35472
by LAIR82
Replied by LAIR82 on topic Gscreen - a GTK / Glade / Python based screen
Is this regarding the tool offset patch??
Rick
Rick
Please Log in or Create an account to join the conversation.
10 Jun 2013 02:31 #35473
by cmorley
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
No. This is just about displaying tool information.
Norbert use the tooledit page to allow selecting of tool changes.
It's a neat deal.
Tool offset patch is a much deeper animal to do properly and is on going work.
It require me to learn much more about the depths of linuxcnc and that has bogged me down - never mind life in general
Chris M
Norbert use the tooledit page to allow selecting of tool changes.
It's a neat deal.
Tool offset patch is a much deeper animal to do properly and is on going work.
It require me to learn much more about the depths of linuxcnc and that has bogged me down - never mind life in general
Chris M
Please Log in or Create an account to join the conversation.
10 Jun 2013 03:25 #35475
by LAIR82
Replied by LAIR82 on topic Gscreen - a GTK / Glade / Python based screen
I see,
I start getting a little lost with the handler file talk.
Anyway, things looking good so far.
Did you change it so if we do a tool call of Txx it will call the tool and not the wear offset? I finally was able to update my first Gscreen build on friday and noticed that a tool call with no wear offset actually changed the tool and didn't give me an error.
I start getting a little lost with the handler file talk.
Anyway, things looking good so far.
Did you change it so if we do a tool call of Txx it will call the tool and not the wear offset? I finally was able to update my first Gscreen build on friday and noticed that a tool call with no wear offset actually changed the tool and didn't give me an error.
Please Log in or Create an account to join the conversation.
15 Jun 2013 04:39 #35650
by LAIR82
Replied by LAIR82 on topic Gscreen - a GTK / Glade / Python based screen
Can you use Gscreen in V2.5.2 ?
Rick
Rick
Please Log in or Create an account to join the conversation.
Time to create page: 0.282 seconds