Gscreen - a GTK / Glade / Python based screen

tjamscad wrote: What is on your list while looking at the tool table?

More than 56 tools is the main thing. (and a complete change to what happens under the hood, away from users)
Also more than one tool in any pocket, and more than one pocket for any tool.

But don't hold your breath, it's a big change in the code.

andypugh wrote:

cmorley wrote: 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.

I said I was going to look at the tool table, and that is part of that.
I haven't even started yet, though.

That would be great Andy.
The wear offsets has been a sore spot for the pros for awhile.
I _really_ don't want to fake something that could potentially crash the machine.

tjamscad wrote: Chris,

Just for encouragement I downloaded Mach3 and ran it in demo mode. I think it has more features that are part of its base that LinuxCNC doesn't have yet. However the interface and I tried several made it cumbersome to use. Great work with gscreen!

Well you guys can thank yourselves too!
Feed back from everyone drives the changes.

Chris M

karlkec wrote:

cmorley wrote: Yes I have already pushed them, last week I think

Chris,

Thanks for doing this. It now works great on my simulator. I'll try it on the mill later in the week.

A couple more very minor things:
1. When selecting jog increments, continuous is below the smallest increment. My preference would be at the other end of the list -- above the largest increment.
2. If an axis moves such that another digit is needed in the DRO display, it seems the width of the axis select buttons and width of the <Absolute> and <Relative> columns change to balance things horizontally. This works nicely unless the axis is sitting at a transition point. For instance, if it's at 10.0000, servo and encoder uncertainty can make it jump back and forth between 9.9999 and 10.0000. The constant changing in width of the axis select buttons and the <Relative> and <Absolute> columns is a bit annoying. Could these columns be made fixed width yet allow room for the largest expected DRO values?

Thanks.

Karl

1) I wonder if having Gscreen look for 'continuous' in the INI file, under INCREMENT=. Then you could put it anywhere you want....
2) Yes. That would be annoying. There are a few things like that. I will try to look at that specifically.

Chris M

cmorley wrote:

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

Norbert:

This is fixed and pushed. the tool editor was parsing the comments trying to convert them to floats
Thanks for pointing it out.
I tried your tool change button on the tooleditor page - very slick!
( I thought you might do it if I didn't get to it - good work!)

I'm almost ready to add Gmoccapy to master - I sent some questions to you, in a PM

Chris M

cmorley wrote: 1) I wonder if having Gscreen look for 'continuous' in the INI file, under INCREMENT=. Then you could put it anywhere you want....
Chris M

That would work fine. Thanks.

Karl