Run GladeVCP from halrun

folks looking into running HAL+GladeVCP applications might want to look here for an example:

git.mah.priv.at/gitweb/emc2-dev.git/comm...d8cf6804933b7dfd1f82

- Michael

wd5jwy wrote:

I'm still trying to figure out how to kill the HAL RTOS when closing the Glade panel.

YEA! Michael has solved the riddle... check out his example. What is needed is the halrun waitusr name of GUI. In this example I've named it "winder". After the GUI closes the lines after "waitusr winder" are executed.

John

John:

This is great if I could just get it to work. I'm a bit confused with the component name both you and Michael (in his example) are using.

The loadusr command wants a component name after the -Wn flag. You are using the component name 'winder' and I'm not sure where that name came from. My gladevcp panel uses an extension of .glade instead of .ui. So, I'm not sure what component name to use after the -Wn flag. Do you just create an empty file with the extension .ui and give it a random name?

Here is the loadusr Halcmd I'm currently using:

#Loads gladevcp then python handler file and then creates glade panel
loadusr -Wn gladevcp gladevcp -c gladevcp -u handler.py wd.glade

I've tried using gladevcp as the name after the waitusr command, but that just locks up the terminal. I've attached my .hal file if that helps.

I actually did try playing with the waitusr command last week, but couldn't understand what name it wants as an argument.

The name "winder" that I used and "ui" that Michael used are just names. You could call it "gnipsel" if you like. in the following example gladevcp is the program that is called and I've named it wd5jwy, the gui is wd.glade. The name gladevcp might confuse waitusr because it is a running program I don't know...

This could be written on one line or leave the gladevcp.start_button off of the second line.
John

IT WORKS! You guys are geniuses. I was still having problems getting the Hal components to unload after closing the Glade panel. But, I forgot that I was making a call to sys.exit(1) in my python file under on_window1_destroy, so the normal call to gtk.main_quit() was never executing. Apparently the call to sys.exit(1) was never returning. Which means the waitusr Hal command was never seeing the interface fully closing and releasing the Hal components.

Anyway, as soon as I removed the sys.exit(1) call from the python file, everything works as it should.

def on_window1_destroy(self, widget, data=None):
sys.exit(1)
gtk.main_quit()

Thanks for figuring this out. Linuxcnc is really an amazing software tool to play with.

Hi guys

I have a minor problem with my stand alone gladevcp based UI


Background:

I have developed touch based UI for LinuxCNC.
I'm using version 2.5.0
I have written handler software with python 2.7 and that works well (-ish)

Anyway, my problem is that my glade UI gets loaded twise (as 2 different windows). 1 window works as it should and other just displays form default initialization data and does not do anything...

How can I prevent from loading this ghost window?

My startup command in HAL - file is following:

loadusr -Wn gladevcp gladevcp -d -u ./data/handler.py -c gladevcp ./data/gladevcp

Thanks in advance

-Jyrki-