Gscreen - a GTK / Glade / Python based screen

there is a problem with the preferences in "industrial" does not update when you give in mm or inch units, you must click on the button mm / inch to assume the change, whereas if you change GScreen perfect.

Chris thought it was some error of mine, LinuxCNC compile again, and nothing tried it on my laptop and got it.

I will review what the gmoccapy, norbert to see if I can do something, a question, I have to cancel or annul the method used by "GUI industry" or the two can work without any problem?

thanks

Jorge Viloria
Colombia

Halo Jorge,

I have 4 lines in [DISPLAY] for DISPLAY = in my INI,

one for gscreen, one for industrial one for axis and one for gmoccapy.
I have every time3 of them commented out, so linuxcnc knows what GUI to start.

I had no problems jet, switching like this the GUI. I do this, because if I do find a bug or strange behavior, I check first with all GUI's to see from where the error may come.

But you can not include both handler files for one GUI, you may copy code from gmoccapy_handler.py to gscreen_handler.py, adapt it to your needs, but from then on you must take by your own about bugs and errors and you may have to do the changes again after an update.

Norbert

hello Chris.

I thought it was a problem in my. INI file or something in my custom industrial_handler.py but delete everything. LinuxCNC compile again, I go to settings such as industry and has the same problem that does not update the units, I have to change it with the button mm / inch which is in the lower right, to see the units in mm.

I was reviewing your file gmoccapy, but this goes above me, is out of my level. I'm reading books and trying to understand the logic of programming but I'm still not even novice at this.

thanks

Hola Norbert, te escribo en español, porque en mi ingles es muy malo,

Pense que era algun problema en mi .INI, o algo en mi archivo industrial_handler.py personalizado, pero borre todo. compile nuevamente linuxcnc, voy a las configuracion de ejemplo, y industrial tiene el mismo problema que no actualiza las unidades, me toca cambiarlo con el boton mm/inch que esta en la parte inferior derecha, para poder ver las unidades en mm.

Estuve revisando tu archivo gmoccapy, pero todo esto me pasa por encima, esta fuera de mi nivel. estoy leyendo libros y tratando de entender la logica de programacion pero aun no soy nisiquiera novato en esto.

Gracias

Jorge Viloria

Hola Jorge,

esto no es un problema tuyo, sino uno de Chris.
En industrial no adapta las unidades correctamente.

Disculpa que no quiero cambiar el code de Chris, porque no se que influencias esto podría tener a otras partes de gscreen.

Tendrás que esperar a que Chris lo corrige.

Saludos de Norbert

To all others:

this is not a problem of Jorge, but one of Chris.
In industrial_glade he does not check for the units at the begining.

Apologize, that I won't mess around in Chris code, because I do not know what influence this may have to other code of gscreen.

He will have to wait till chris is back.

Norbert

Regards,

I made ​​to adapt the incremental jog buttons. the jog rate with slider

I have a problem when I press the arrow keys (up, down, left right) also begins the slider up or down according to the direction of the keys

I thought then vbox1 containing JOG_INCREMENT buttons and jog slider rate, apply the set_sensitive (False) when pressing any of the keys


I tried this:

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
if self.data.key_even_up = 1:
self.widgets.vbox1.set_sensitive(False)
if self.data.key_even_up = 0:
self.widgets.vbox1.set_sensitive(True)

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
if self.data.key_even_dwn = 1:
self.widgets.vbox1.set_sensitive(False)
if self.data.key_even_dwn = 0:
self.widgets.vbox1.set_sensitive(True)

elif keyname == "Left":
self.gscreen.do_key_jog(2,0,signal)
if self.data.key_even_left = 1:
self.widgets.vbox1.set_sensitive(False)
if self.data.key_even_left = 0:
self.widgets.vbox1.set_sensitive(True)

elif keyname == "Right":
self.gscreen.do_key_jog(2,1,signal)
if self.data.key_even_right = 1:
self.widgets.vbox1.set_sensitive(False)
if self.data.key_even_riht = 0:
self.widgets.vbox1.set_sensitive(True)

works well for up and down, left and right but it does not tell me key.data_event_left, not defined

I tried several things but I was unable to do, please if anyone knows I appreciate

Jorge Viloria

I'm having a hard time understanding you here.
So you made a custom screen with a jog rate slider?
and the slider is responding to the jogging keys?
This is a problem with the keybinding continuing past the jogging code.
You must return True to stop this from happening, but you must also allow the keybinding through if you want MDI or Gcode editting.

As for the error about key.data_event_left that is because gscreen has not defined it.
Up and down code is different from left right code.
This is because the keybinding stuff is new and experimental.

I am now back home so hopefully can spend some time fixing these problems.

Chris M

Chris,

Chris not forget industrial error does not update mode mm

is what is happening, I have placed a slider for jog-rate and responds to the arrow keys (up, down, left, right) I make an accident almost without realizing I reach the maximum speed. I do not understand the solution?

thanks,

Jorge Viloria

As far as I understood, Jorge want to add sliders to industrial and they should work like they do in gmoccapy. I looked at the code, but industrial is handling the thinks quiet different to gmoccapy, so I decided no to change the code.

The problem of key handling, moving the sliders is solved in gmoccapy, In 0.9.1 there is still a problem, that you will not be able to change parameters in the tool editor, when you are in manual mode. There are two solutions:

- Wait aprox. two days, I got 0.9.2 on the roll witch solved this and then it will support also lathes!

- change line 427 in gmoccapy_handler from:to
Norbert

ok I think the key binding issue is fixed.
I also changed the jogging keys around, I think it makes sense.

up/down is the Z left/right is X and page up/down is Y
I changed the direction of Z jogging.

still working on the metric problem.

Chris M

keybinndings probably going to change again as i seem to have it different then the other linuxcnc GUIs...