Gscreen - a GTK / Glade / Python based screen

newbynobi wrote:

Hallo Chris,

I just managed this, I had to open gscreen and in preferences disable the aux screen, thats it.
So the preferences are taken in care even if I start from a different config folder.

This can confuse operators!


Regards Norbert

Ok Norbert:

You can specify a preference file path in the INI under the [DISPLAY] heading
PREFERENCE_FILE_PATH=

If it's missing, it will use the default ~/.gscreen_preferences

I also fixed the plot reloading problem
oh and industrial now changes the edit button text

Chris M

Hi Chris,

Spent more time on the mill with gscreen. Some comments:
1. If I'm running a program and press "Set Override", the Position, G Codes Active, and Status areas of the screen become greyed out so itt's harder to see the override being adjusted, and to see the axis positions.
2. When first entering MDI mode and bringing up the Onboard keyboard, could the cursor be automatically placed in the MDI entry field? This entry field is small and hard to select using the touchscreen. I think probably this field should be the active one anytime MDI mode is active.
3, Also, after a block is executed in MDI mode the text remains in the entry field. This requires clearing out the text before entering a new MDI command, which is hard to do with the touchscreen. Could the entry field be cleared after it is executed.
4. Double-touching the spinbox in the upper right using the touchscreen sometimes brings up the numeric entry widget and sometimes not. With the touchscreen it would be nice to always bring it up when the spinbox is double-touched.

I'm starting to work on customizing your industrial screen. I have my own config directory outside the development tree, and have made symlinks to industrial.glade and industrial_haldler.py in the development tree. Can I create a new git branch in the development tree for my changes and rebase to pick up your changes? Or is that asking for trouble later on?
Also, do you know of a way to push my changes to my own git server so I can pull them to my other machines, yet get your gscreen updates too?

Thanks.
Karl

karlkec wrote:

Hi Chris,

Spent more time on the mill with gscreen. Some comments:
1. If I'm running a program and press "Set Override", the Position, G Codes Active, and Status areas of the screen become greyed out so itt's harder to see the override being adjusted, and to see the axis positions.

Ok yes I was being lazy It was easier to make the whole box greyed out then just all the buttons- I can work on that,

2. When first entering MDI mode and bringing up the Onboard keyboard, could the cursor be automatically placed in the MDI entry field? This entry field is small and hard to select using the touchscreen. I think probably this field should be the active one anytime MDI mode is active.

Yes i should be able to set the focus to the MDI entry

3, Also, after a block is executed in MDI mode the text remains in the entry field. This requires clearing out the text before entering a new MDI command, which is hard to do with the touchscreen. Could the entry field be cleared after it is executed.

This is a separate widget that I didn't make but have tinkered with, I can see what I can do

4. Double-touching the spinbox in the upper right using the touchscreen sometimes brings up the numeric entry widget and sometimes not. With the touchscreen it would be nice to always bring it up when the spinbox is double-touched.

You must have the pointer still showing. If you hide the pointer then a single click will bring up the numeric entry widget.
If you show the pointer then a double click brings it up. double clicking with a touch screen, as you have seen, is not 100% reliable.
It's done differently so people with a keyboard can click the spinbox once and then type - it's quicker

I'm starting to work on customizing your industrial screen. I have my own config directory outside the development tree, and have made symlinks to industrial.glade and industrial_haldler.py in the development tree. Can I create a new git branch in the development tree for my changes and rebase to pick up your changes? Or is that asking for trouble later on?
Also, do you know of a way to push my changes to my own git server so I can pull them to my other machines, yet get your gscreen updates too?

Thanks.
Karl

You should create your own local branch based from master.

Make sure your on master:
git checkout master

pull to make sure your current:
git pull

then make your own branch (topic name can be anything)
git branch topic master

If you 'gitk' - you will see your new branch on top
if you 'git branch' you will see your new branch name

Now make your changes to Gscreen's file then commit the changes

if you 'gitk' you will see these commits

If you wish to merge master back in from time to time use:

git merge origin/master

and be prepared to fix conflics.

This is just the very basics. I hesitate to say much more since I wish to tell no lies
You should ask on the maillist where the git experts live!

Please keep us posted on your changes, so they can possibly be incorporated
You should see Norbert's screen - it is so different, based on Mocca's look if you know Mocca.

Now I know why all those Mach guys were bummed when they realized the screen was difficult to change in linuxcnc.
It's kinda fun!

Chris M

cmorley wrote:

The spindle direction buttons 'toogle' either fwd or reverse, so one will always be selected.
In this way when you push start, you will know what way it will turn.



gscreen.py is the Main file.
It has 'helper' files:
mdi.py
preference.py
emc_interface.py
and the stock screen file, gscreen,glade

These are found in /src/emc/usr_intf/gscreen in a compiled run-in-place linuxcnc.

Then there can be 'local' (local as in the users config with the HAL files) custom screen files.
These can be somename_hander,py and/or somename.glade

For instance the industrial screen is defined in these 'local' files. They must be put in every cofig folder that you want industrial in.
This is different from all other linuxcnc screens. There you just change the DISPLAY= name in the INI file and the new screen shows up.
This works with Gscreen too but you will always get the stock screen that way.

Chris M

Thanks Chris, That's alot to take in but in time i'm sure i will get it.

Yes. That would be great.

BigJohnT wrote:

I did something like if speed > 0 then check the at speed... I forget exactly where I did that at.

John

John, will this type of line fix the green indicator at speed 0?

tjamscad wrote:

BigJohnT wrote:

I did something like if speed > 0 then check the at speed... I forget exactly where I did that at.

John

John, will this type of line fix the green indicator at speed 0?

I did something different, setting the on-color black at off time, do to the fact that it was just a HAL_led run from a HAL signal.

but anyways it works - I just haven't pushed it yet.

tjamscad have you tested with your machinists yet?