New Problem

Ok, I did a little more testing. This part is now looking to be related to using Gmoccapy in some way. I am using version 2.3.3.3.

These warning appeared on the terminal when I set my work piece zeros.


The warning occurs when I press the X=?, Y=? or Z=? button at the bottom of the screen. The operation does end up completing with the desired results so I guess this is in the nuisance category of problems.

John

Sorry, I didn't find the time to look at this.

You can solve this by setting "VERSION" to 1.1 in the INI.

Why that is not happening automatically is what I need to fix for everyone else.

islander261 wrote: Andy

Please find attached the .zip file of my configuration. I am using the no_eo_cleanup1.ini file for my present working configuration.

John

I think I have found the problem, the update_ini script does not handle ini-files with #INCLUDE statements.

I need to figure out how to fix that. It isn't looking trivial.

islander261 wrote: Ok, I did a little more testing. This part is now looking to be related to using Gmoccapy in some way. I am using version 2.3.3.3.

Code:

Emit interp-run (<__main__.gmoccapy object at 0x7fb650438b90>, <Dialogs object at 0x7fb650457aa0 (Dialogs at 0x28b7240)>, 'alert') (<__main__.gmoccapy object at 0x7fb650438b90>, <Dialogs object at 0x7fb650457aa0 (Dialogs at 0x28b7240)>, 'alert')

These warning appeared on the terminal when I set my work piece zeros.

The warning occurs when I press the X=?, Y=? or Z=? button at the bottom of the screen. The operation does end up completing with the desired results so I guess this is in the nuisance category of problems.

John

These are not warnings - these look like they are debug messages left in from work Norbert did recently.
unless you find something wrong, you can ignore them.

Chris M

andypugh wrote: I need to figure out how to fix that. It isn't looking trivial.

Actually, it was an easy fix, and has been pushed to Master.