Gscreen - a GTK / Glade / Python based screen

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

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?

Chris,

just make the frame a fixed size, than it will not jump any more, may be you take a look on gmoccapy, I realized it that way.

Norbert

Chris,

On the restart at line I would prefer to just enter a line number. the UP and Down button works but If I want to start at line 1000 that is alot of button taps.

I noticed the updated screen shot of the DTG and Homing marks. Is that still being worked on or has it been pushed?

It is a sample and has not been pushed - is that all right looking?

I am working on the restart entry widget - I just noticed you can't enter a line number.
i will have it pop up with the last run line.

Chris M

cmorley wrote:

It is a sample and has not been pushed - is that all right looking?

I am working on the restart entry widget - I just noticed you can't enter a line number.
i will have it pop up with the last run line.

Chris M

Yes that looks fine. I wonder how messy it gets with more than three axis's? The most our mills are running is 5 but I know we have a 8 or 9 axis tool grinder that stuarts want to put LinuxCNC on.

hello all
i am using gscreen lathe config.
its perfect
but
tooloffset error
i am adding z axis value
the popup error msg come
BAD CHARACTER Y USED
what can i do

Hallo,

I just checked the behavior with the newest push.
I can not reproduce the error you mentioned.

Do you have the latest version?
Can you explain exactly what you are doing?

Norbert

i am using
LINUXCNC - 2.6.0-pre0-3876-g3bf98ee
i am still facing a z axis tool offset problem

Please descripe exactly the way to reproduce the error, step by step.