qtvismach, a axis toolpath

  • MarkoPolo
  • Away
  • Elite Member
  • Elite Member
More
23 May 2025 18:36 #328998 by MarkoPolo
Replied by MarkoPolo on topic qtvismach, a axis toolpath
I have the following code in the hadler vismach file. (a bit more in the file)

STATUS.connect('graphics-gcode-properties',lambda w, d: update_gcode_properties(d))

def update_gcode_properties(props):
    if props != None:
        print ("update update_gcode")
        property_names = {
                'x': "X bounds:",'x_zero_rxy':'X @ Zero Rotation:',
                'y': "Y bounds:",'y_zero_rxy':'Y @ Zero Rotation:',
                'z': "Z bounds:",'z_zero_rxy':'Z @ Zero Rotation:',
                'a': "A bounds:", 'b': "B bounds:",
            }


Based on graphics-gcode-properties I draw a block of processed material.

This code works, but only when I run it as a built-in qtdragon panel. I want to run the panel as a standalone window.
Currently, to make everything work for me, I run the panel twice, as a standalone window and as a built-in panel. I want to get rid of the built-in panel and run it only as a standalone window.

How do I modify the handler file so that it works as a standalone window?

It seems to me that "STATUS.connect" does not work in standalone vismach

Marek
Attachments:

Please Log in or Create an account to join the conversation.

More
24 May 2025 01:29 #329029 by cmorley
Replied by cmorley on topic qtvismach, a axis toolpath
This is a limitation of python/linuxcnc.
The properties signal is produced in the qt_graphics widget.
The receiving widget must be in the same python instance as the qt_graphics widget.
A stand alone panel is a different instance of python then the main screen.

You could add a qt_graphics widget to your stand alone panel.
Or possibly could try using ZMQ messages with a customized handlerfile.

Please Log in or Create an account to join the conversation.

Moderators: cmorley
Time to create page: 0.076 seconds
Powered by Kunena Forum