Raspberry Pi 4

Hakan wrote: Andy was that on raspbian RPi4 or on Intel buster? It seems to me the two are not exactly the same.

RPi4. I am working abroad this week, but I brought the Pi with me, so will have a check tonight.

I think I figured out what you did. You replaced rsvg in lathehandler.py?
So it is more LatheMacro than gladevcp.
Slowly understanding all this.

I haven't tested lathehandler.py.

I would not be surprised to find that it doesn't work, but it is probably an easy fix using gobject introspection. Most other things seem to be.

Hakan wrote: I think I figured out what you did. You replaced rsvg in lathehandler.py?

I feel to be homing in on a solution for the lathe macros, but it isn't all the way there. I think we might need to change all of GladeVCP.

If you


Then in a standalone Python session you can
Unfortunately once you are using gi (gobject introspection) it seems that you are not allowed to not use it elsewhere, so if you edit lathehandler.py to use the above, you get:

import error: When using gi.repository you must not import static modules like "gobject". Please change all occurrences of "import gobject" to "from gi.repository import GObject". See: bugzilla.gnome.org/show_bug.cgi?id=709183

andypugh wrote:

Hakan wrote: I think I figured out what you did. You replaced rsvg in lathehandler.py?

I feel to be homing in on a solution for the lathe macros, but it isn't all the way there. I think we might need to change all of GladeVCP.

If you

Code:

sudo apt-get install gir1.2-rsvg-2.0

Then in a standalone Python session you can

Code:

from gi.repository import Rsvg as rsvg

Unfortunately once you are using gi (gobject introspection) it seems that you are not allowed to not use it elsewhere, so if you edit lathehandler.py to use the above, you get:

import error: When using gi.repository you must not import static modules like "gobject". Please change all occurrences of "import gobject" to "from gi.repository import GObject". See: bugzilla.gnome.org/show_bug.cgi?id=709183

I realize I may be tarred and feathered for the suggestion, but isn't this as good a time as any to switch to working in python-3.7 for any python stuff you have to re-write? From the comments on the python list, python-2.7 is on very limited life support and gasping for air. Only a month or so left. I wish I could help, but python has never yielded to any fixes I've tried such as trying to find a solution for camview going dead just when you've jogged to the second way point to record or fix a workpiece miss-alignment.

I would think so too. python never was my tool I am afraid.

But there are long term options and short term.

Short term, it would be good if thís could be made going in some way. buster is knocking on the door.

Long term, I see you are working on Qt stuff and what not. It may take its time but a clear way forward would be really nice to have.

... I'll try your suggestion tomorrow, andy.