- Posts: 1916
- Thank you received: 0
Gscreen - a GTK / Glade / Python based screen
13 years 3 weeks ago #39531
by newbynobi
Replied by newbynobi on topic Gscreen - a GTK / Glade / Python based screen
Halo Chris,
if you do a rework on that, could you please check also for translation strings, which are not needed?
In some glade files (i.e. tooledit) you just have marked every label as translatable, but why translate "1" or "G54"
Such things make the translatable files unnecessarily large.
IMHO: Also the GSCREEN MESSAGE and GSCREEN ERROR items needn't to be translated, as the are specific errors.
Norbert
if you do a rework on that, could you please check also for translation strings, which are not needed?
In some glade files (i.e. tooledit) you just have marked every label as translatable, but why translate "1" or "G54"
Such things make the translatable files unnecessarily large.
IMHO: Also the GSCREEN MESSAGE and GSCREEN ERROR items needn't to be translated, as the are specific errors.
Norbert
Please Log in to join the conversation.
12 years 10 months ago #41834
by LAIR82
Replied by LAIR82 on topic Gscreen - a GTK / Glade / Python based screen
Hello Chris,
Been a while,
Trying to finish up my third turning center, and was wondering in which file I would go to, to get the left side of the display to fill the window. You have probably told me, and I tried searching with no luck.
Here is what I am talking about,
Thanks
Rick
Been a while,
Trying to finish up my third turning center, and was wondering in which file I would go to, to get the left side of the display to fill the window. You have probably told me, and I tried searching with no luck.
Here is what I am talking about,
Attachment not found
Thanks
Rick
Please Log in to join the conversation.
12 years 10 months ago #41858
by cmorley
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
You must modify the industrial.glade file, with the GLADE editor ( or use a terminal editor is possible)
The widgets:
alignment1
active_gcode_frame
frame6
under the properties heading 'packing' look for 'expand'
change to yes (one or all of them)
now when you hide the keyboard they will expand vertically.
The file can be found either in your config file folder or (if you have pulled in the last month or so) in share/gscreen/skin/industrial
if you change the one in your config file it will never be upgraded, the one in share/ will be over written on updates.
You can copy the one in share/ to your config then when loading that config it will always use the copied one (name it the same).
Hope that helps.
Chris M
The widgets:
alignment1
active_gcode_frame
frame6
under the properties heading 'packing' look for 'expand'
change to yes (one or all of them)
now when you hide the keyboard they will expand vertically.
The file can be found either in your config file folder or (if you have pulled in the last month or so) in share/gscreen/skin/industrial
if you change the one in your config file it will never be upgraded, the one in share/ will be over written on updates.
You can copy the one in share/ to your config then when loading that config it will always use the copied one (name it the same).
Hope that helps.
Chris M
Please Log in to join the conversation.
12 years 10 months ago #42032
by LAIR82
Hello Guys,
What is the proper format for the jog increment line in the INI file, here is mine,
INCREMENTS = 1.000, .1, .01, .001, .0001,
and I have tried numerous flavours of this and still get a fault when trying to change it.
Thanks
Rick
Replied by LAIR82 on topic Gscreen - a GTK / Glade / Python based screen
cmorley wrote:
tjamscad wrote:
cmorley wrote: Can you post the INI file.
I bet you didn't add the jog increment entry to the INI (TOUCY doesn't use it)
As for jogging - did you remember to click the on screen button 'jog' to enable jogging?
Chris M
You are correct once again. No "INCREMENTS" in the ini file.
This should be why on screen jogging didn't work too.
Hello Guys,
What is the proper format for the jog increment line in the INI file, here is mine,
INCREMENTS = 1.000, .1, .01, .001, .0001,
and I have tried numerous flavours of this and still get a fault when trying to change it.
Thanks
Rick
Please Log in to join the conversation.
12 years 10 months ago #42045
by newbynobi
Replied by newbynobi on topic Gscreen - a GTK / Glade / Python based screen
try:
INCREMENTS = 1.000mm 0.1mm 0.01mm 0.001mm 0.0001mm
or:
INCREMENTS = 1.000in 0.1in 0.01in 0.001in 0.0001in
But normally your one should work also.
Norbert
INCREMENTS = 1.000mm 0.1mm 0.01mm 0.001mm 0.0001mm
or:
INCREMENTS = 1.000in 0.1in 0.01in 0.001in 0.0001in
But normally your one should work also.
Norbert
Please Log in to join the conversation.
12 years 10 months ago #42136
by LAIR82
Replied by LAIR82 on topic Gscreen - a GTK / Glade / Python based screen
Chris,
I was able to get my screen redone to my liking. Now I might try and dabble with putting a picture in that same column to take a little bit of the space that was there.
Norbert,
I realized that the increments are working, the machine will jog at whatever is selected, the actual problem is, the selected increment is not displayed on the left side status area in the screen.
Thanks
Rick
I was able to get my screen redone to my liking. Now I might try and dabble with putting a picture in that same column to take a little bit of the space that was there.
Norbert,
I realized that the increments are working, the machine will jog at whatever is selected, the actual problem is, the selected increment is not displayed on the left side status area in the screen.
Thanks
Rick
Please Log in to join the conversation.
12 years 10 months ago #42144
by cmorley
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
Glad your figuring it out.
let me know of anything I can help with and don't forget to post a pic once in a while
Chris M
let me know of anything I can help with and don't forget to post a pic once in a while
Chris M
Please Log in to join the conversation.
12 years 10 months ago #42146
by cmorley
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
I see why the jog increments are not updating - I pushed a fix.
If you are using a custom glade file you will need to update it manually.
the labels for jogs are:
jog_increments
angular_jog_increments
jog_rate
angular_jog_rate
Chris M
If you are using a custom glade file you will need to update it manually.
the labels for jogs are:
jog_increments
angular_jog_increments
jog_rate
angular_jog_rate
Chris M
Please Log in to join the conversation.
12 years 10 months ago #42208
by LAIR82
Replied by LAIR82 on topic Gscreen - a GTK / Glade / Python based screen
I pulled that fix, now the increments work great. Thanks
But now I am back to trying to get the screen filled out again. I went into the glade file and clicked expand on all three boxes you mentioned and I keep getting a fault when trying to start up. I must have clicked/selected something else the other day when I actually got it to work. I will press on tomorrow and see if I can remember what I did.
Guess I need to start actually taking notes down on how I manage to stumble across making things work properly.
Thanks
Rick
But now I am back to trying to get the screen filled out again. I went into the glade file and clicked expand on all three boxes you mentioned and I keep getting a fault when trying to start up. I must have clicked/selected something else the other day when I actually got it to work. I will press on tomorrow and see if I can remember what I did.
Guess I need to start actually taking notes down on how I manage to stumble across making things work properly.
Thanks
Rick
Please Log in to join the conversation.
12 years 9 months ago #42249
by LAIR82
Replied by LAIR82 on topic Gscreen - a GTK / Glade / Python based screen
I honestly cannot figure out what I did to get my screen filled out the other day. Here is a screen shot of the fault I get.
Any pointers/hits?
Thanks
Rick
And Happy New Year!!!!!!!!
Attachment not found
Any pointers/hits?
Thanks
Rick
And Happy New Year!!!!!!!!
Please Log in to join the conversation.
Time to create page: 0.127 seconds
