Gscreen - a GTK / Glade / Python based screen
I really want it to run just like the original live cd from the applications menu. How do I accomplish this?
I create a launcher by right clicking on the desktop and supply the full path to the linuxcnc script int the RIP directory then a space and the full path to my configuration in the command box. Of course this is after doing the normal build process from the src directory of
./autogen.sh
./configure
make
sudo make setuid
John
Please Log in or Create an account to join the conversation.
Edit the shortcuts/menu items so that they point to the linuxcnc script in your linuxcnc-dev/scripts/ directory rather than to the one they currently point to. I am a bit fuzzy on the details, but it will involve right-clicks and property tabs. it can't be that hard, I managed it.I really want it to run just like the original live cd from the applications menu. How do I accomplish this?
I think that when Cradek made the touchy interface he decided that touchscreens were too unreliable and laggy to be used as jogging controls. This is why Touchy requires a physical jogwheel. This is partly because the touchscreen is always userspace and subject to being ignored by the OS, whereas the jogwheel runs in the realtime layer, so is guaranteed to be acted on.Also is anybody working on a touchscreen pendant control? I was hoping that under jogging mode button you would get an onscreen pendant style jogging controller similar to what Mach3 has
Please Log in or Create an account to join the conversation.
I don't know hoe Mach does it but assume a screen with buttons in positions that represent the direction to jog.
Gscreen does it by selecting the axis then pushing the + or - key (while in jogging mode)
I should say this is for rough jogging (jogging at a speed not a position)
Did I mention that Gscreen is under development ?
Please Log in or Create an account to join the conversation.
overrides can be adjusted now.
I haven't done this yet, but at the moment I have decided to drop the 'startup mode' screen and just have manual, MDI and auto.
questions:
what sounds better ? have jogging enabled automatically when in manual mode or having to select 'jog mode' while in manual.
have loading, saving, editiing Gcode in manual or in auto (as it is now) Keep in mind if using NCGgui or wizards they are only available to view in auto mode.
Please Log in or Create an account to join the conversation.
this is in keeping with i think our origional goal , in keeping it uncluttered , and reducing key presses ( or screen touch ) to a minimum .
with regard to file editing , i can see a reason to have editing done in manual mode , but i still feel auto mode overall gives a better result and again keeps it uncluttered .
must admit i am undecided on this one .
Please Log in or Create an account to join the conversation.
Never mind I found it I think.
John
Please Log in or Create an account to join the conversation.
John
Please Log in or Create an account to join the conversation.
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
Please Log in or Create an account to join the conversation.
John
Please Log in or Create an account to join the conversation.
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
Please Log in or Create an account to join the conversation.