Gscreen - a GTK / Glade / Python based screen

I got it up and running and it came up full screen but my mouse pointer disappeared... I can see buttons getting pressed when I guess where the mouse might be. Is Gscreen for touch screens?

John

Gscreen was made with touch screens in mind but works fine with a mouse.
On the second menu page there is a button to show/hide the mouse. (just like TOUCHY)
Not sure why it defaulted to hide but....

I am doinf some docs on the wiki but they are not finished yet...
I am interested in your comments. Gscreen is obviously still developing

Chris M

I'd include some instructions on how to get it loaded somewhere up front... a screen shot of the preferences page would be nice. I assume you plan on incorporating the Gscreen docs into your branch at some time. For folks who want to modify some path to getting there would be helpful. I see you reused some of the Touchy python files. I wish they were documented in some other language than programmer...

John

yes I will add more pics to the wiki docs.
when they are closer to finished and stable I will add them to the formal docs - I made need some pointers from you

By 'folks who want to modify' do you mean modify gscreen?
Were you thinking of something specific ?
There is much work to do to the code to clean it up.
I program organically and messily

I intend to comment the files to help someone figure out what does what - at the moment I'm figuring out what does what !

Chris

Yes, modify and perhaps follow your path and create a new screen based on the python support files Chris created for Touchy.

Well now that you asked I've been thinking about a plasma GUI that displays the cut path and width and length as big as the plotting screen allows but no relation to physical position. The reason for this is you jog to the start point and press start and use G92 to set that point to X0 Y0. With Axis your constantly zooming in and out and panning to find your back plot. And other plasma related items...

Just reading emc_interface.py it seems to be the connection file to the control part of linuxcnc... it would be interesting to find out what the minimum frame work was to connect to linuxcnc is.

John

Another thing I noticed in Touchy is Chris used a dictionary to connect the signals up. I have found that using the Gtk builder connect_signals to be easier and less typing.

gnipsel.com/glade/python01.html

John