When the limit switches are active at startup and im starting the machine without overwriting the limits, then the whole GUI freezes and crashes. Normally i should get a warning when trying to activate the machine, this is like axis act. My machine isn't connected at the moment for testing the camera and new GUI stuff, thats why linuxCNC thinks my machine is at limit. But i think gmoccapy shouldn't act like this anyways.. I'll attach a screenshot later and the terminal text.
so next problem with the handler code is the widget argument:
Code:
TypeError: on_Cam_active_toggled() takes exactly 3 arguments (2 given)
when i only call
Code:
def on_Cam_active_toggled(self, state):
print 'Button 1 toggled. state: ', state
if state:
self.mdi_1.emit('activate')
else:
self.mdi_2.emit('activate')
the button "works", but when toggled first time it prints the same state as it gets untoggled
Code:
Button 1 toggled. state: <gtk.ToggleButton object at 0x8de55a4 (GtkToggleButton at 0x85da990)>
Traceback (most recent call last):
File "./myui.py", line 9, in on_Cam_active_toggled
self.mdi_1.emit('activate')
AttributeError: 'NoneType' object has no attribute 'emit'
Button 1 toggled. state: <gtk.ToggleButton object at 0x8de55a4 (GtkToggleButton at 0x85da990)>
Traceback (most recent call last):
File "./myui.py", line 9, in on_Cam_active_toggled
self.mdi_1.emit('activate')
AttributeError: 'NoneType' object has no attribute 'emit'
and another question: should it really be self.mdi_1.emit('activate') or the signal name of mdi command: self.mdi_1.emit('on_mdi_camon_activate')
I'll try to understand the Gtk.ToggleButton, at the moment its really hard for me to understand all these Gtk/ Python stuff, ive never used python before
