Welcome to LinuxCNC.org

eto wrote:
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

eto wrote: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 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.

Gcreen currently allows jogging be screen buttons. Whether that's a good idea still up for debate. ( and depends alot on servo thread speed)
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 ?

I have done some work on the graphics view with touch screens in mind (pan, rotate, etc) or using on screen buttons.
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.

i'd stick with jogging enabled automaticly , i think keeps it clean and uncluttered , with functionality approprate in that particular mode , unless of course it becomes a safety issue , then drop back into specific sequences to enable
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 .

I think I'm up to speed enough on Gtk and Glade to look at Gscreen now LOL. Chris do you maintain a git repository or something on Gscreen?

Never mind I found it I think.

John