Gscreen - a GTK / Glade / Python based screen

More
13 years 6 months ago #32286 by cmorley
Tjamscad

No I haven't pushed it yet.
Is having the keyboard on that side ok? or should the regular vertical gscreen buttons be on the right of the keyboard?

Chris M

Please Log in or Create an account to join the conversation.

More
13 years 6 months ago #32291 by LAIR82
I will post some pics tomorrow.

As for the keyboard, I can definitely see the value, if going for a total touchscreen intergface. Would there be a way though to, in the preference tab, make it selectable as to wether or not it is used. We are doing all of our builds using $10 rubber USB keyboards. They are waterproof, and are easy for the guys to use.
We are only using 15" touchscreens (we found quite a few at dirt cheap prices on Ebay) so I'm thinking it would make it really cramped on our display having Onboard on all the time.


Rick

Please Log in or Create an account to join the conversation.

More
13 years 6 months ago #32292 by cmorley
Rick

Are you using default or industrial?

I think I'll add embedded Onboard to industrial but yes I'll see to making it selectable.

As for key bindings I'm not sure if I should have a page for selecting bindings or just hard code them but allow one to override the code with the handler file.
I'm not sure the page selection adaptable enough...
I'll probably hard code some first andd see how well that works.

Chris M

Please Log in or Create an account to join the conversation.

More
13 years 6 months ago #32293 by LAIR82
We are using industrial.

I think hard code would be fine. Our guys just like the arrow jog and using i and shift-i to change jog increments.

Rick

Please Log in or Create an account to join the conversation.

More
13 years 6 months ago - 13 years 6 months ago #32298 by newbynobi
Hallo Chris,

can you make the Key Bindings dynamically?
I meen a INI File like so:
Code:
[KEY_BINDINGS_WINDOW_1] close = <ALT><F4> jog-x-plus = <X> jog-x-mins = <SHIFT><X> select-x = <0> select-y = <1> [KEY_BINDINGS_DIALOG] OK = <ENTER>
and so on, so it is editable from the user, allowing more individualism.

Regards Norbert
Last edit: 13 years 6 months ago by newbynobi.

Please Log in or Create an account to join the conversation.

More
13 years 6 months ago #32299 by cmorley
Not sure if this is workable.
The reason is keybindings call methods.
Your methods (Gmoccapy) could be different from my methods.
It could cause errors or un wanted movement

Well I guess I could add a method to parse the INI and add them to a lookup table then it would be up to the screen to us that to call methods.

I pushed a experimental key binding sample.

escape = estop
i = increments up
shift i = incremennts down

up down -jog axis 0
left right - jog axis 1
page up page down - jog axis 2

One problem that came up is key repeating.
When using incremental jogging if I don't trap the key repeat then the increments repeat.
I trapped axis 0 but not the axis 1 or 2.
carefully try each way and see what you think.
This may or may not work with Gmoccapy

Chris M

Please Log in or Create an account to join the conversation.

Time to create page: 0.110 seconds
Powered by Kunena Forum