Gscreen - a GTK / Glade / Python based screen

jlviloria wrote:

Cmorley,

hello sorry you bother.

GScreen trying to get, I see you did the ToolEdit in glade. copy your files (tooledit.widget.py and tooledit.gtk.glade) in /sim/axis and try to embed on screen AXIS, but I get an error. I gave the path to my file. TBL.

But it has not been unsuccessful. is that I have no knowledge of programming, if I ask your help,



In advance thank you very much for your attention.

jorge

LAIR82 wrote:

cmorley wrote:

The preference file is located in your home directory (most likely your name)
It's hidden so you must select 'show hidden files' in the browser.

If you are using Industrial the the glade file and handler file will need to be in your config folder. (copied from the sim/gscreen_custom folder)

If you are using default Gscreen the you must copy Gscreens glade file and make a handler file.

I use gedit to edit python. and you use GLADE editor to change the GLADE file.
You must run glade from a terminal after entering . scripts/rip-evironment

GLADE editing takes some time to get quick at.
I hope this helps/

Hello Chris,

Its been a madhouse at our shop, I've had a machining center down since monday with a bad servo, so I haven't been able to play my gscreen machine at all this week. Hopefully by monday I can let you know how the keybindings work. Actually, could you give me an example of what the line would look like to change a binding, I want to change the left/right jog buttons to be axis 2 instead of 1.

I see my preferences file now. So I need to be in the /scripts/rip-environment directory then run glade from the command line. Making sense so far. What would the command be for starting glade?

Thanks

Rick

def initialize_keybindings()
        self.widgets.window1.connect('key_press_event', self.on_key_event,1)
        self.widgets.window1.connect('key_release_event', self.on_key_event,0)

def on_key_event(self,widget, event,signal):
        keyname = gtk.gdk.keyval_name(event.keyval)
        print "Key %s (%d) was pressed" % (keyname, event.keyval),signal
        if event.state & gtk.gdk.CONTROL_MASK:
            print "Control was being held down"
        if event.state & gtk.gdk.MOD1_MASK:
            print "Alt was being held down"
        if event.state & gtk.gdk.SHIFT_MASK:
            print "Shift was being held down"

        if keyname == "Up":
            if self.data.key_event_up == signal: return
            self.gscreen.do_key_jog(0,0,signal)
            self.data.key_event_up = signal
        elif keyname == "Down":
            if self.data.key_event_dwn == signal: return
            self.gscreen.do_key_jog(0,1,signal)
            self.data.key_event_dwn = signal
        elif keyname == "Left":
            self.gscreen.do_key_jog(2,0,signal)
        elif keyname == "Right":
            self.gscreen.do_key_jog(2,1,signal)
        elif keyname == "Page_Up":
            self.gscreendo_key_jog(1,0,signal)
        elif keyname == "Page_Down":
            self.gscreendo_key_jog(1,1,signal)
        elif keyname in ("I","i") :
            if signal: return
            if event.state & gtk.gdk.SHIFT_MASK:
                self.gscreen.set_jog_increments(index_dir = -1)
            else:
                self.gscreen.set_jog_increments(index_dir = 1)

I wonder if this is because you are trying to use data.estopped before the periodic is turned on?

you could check the task state directly through

self.gscreen.emc_status.emcstat.poll()
estop = self.gscreen.emc_status.task_state == self.gscreen.emc_status..emc.STATE_ESTOP

Hope I got that code right...
There may be other ways - I just don't have time to check sorry.

self.gscreen.status.emcstat.poll()
estop = self.gscreen.status.emcstat.task_state == self.gscreen.status.emc.STATE_ESTOP

newbynobi wrote:

I wonder if this is because you are trying to use data.estopped before the periodic is turned on?

you could check the task state directly through

self.gscreen.emc_status.emcstat.poll()
estop = self.gscreen.emc_status.task_state == self.gscreen.emc_status..emc.STATE_ESTOP

Hope I got that code right...
There may be other ways - I just don't have time to check sorry.

Hallo Chris,

I found ot that it must be:

self.gscreen.status.emcstat.poll()
estop = self.gscreen.status.emcstat.task_state == self.gscreen.status.emc.STATE_ESTOP

to get the correct value.

But I am asking myself, when will periodic begin to run?
I checked the state of self.data.estopped now on_window1.realize() and do get the wrong value. If I get it directly with the code you gave me, I get the correct value.

Should this be corrected in the feature? By running the first periodic from gscreen bevor starting the gui?

Norbert

Norbert