Gscreen - a GTK / Glade / Python based screen

More
13 years 8 months ago #29593 by tjamscad
Replied by tjamscad on topic Gscreen - a GTK / Glade / Python based screen

cmorley wrote: Yes! and I sent it to you.

Chris M


Chris,

I like it, I like it

On the System tab can you add unlocked or locked? I left the system tab but didnt know if it was unlocked.

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

More
13 years 8 months ago #29599 by andypugh
Replied by andypugh on topic Gscreen - a GTK / Glade / Python based screen

tjamscad wrote: On the System tab can you add unlocked or locked? I left the system tab but didnt know if it was unlocked.

<hint>
The point of GScreen is that it is meant to be an interface that is easily customisable by the end-user
</hint>

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

More
13 years 8 months ago #29612 by cmorley
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
Well this process of customizing for industrial was meant to exerciser the process of user changes so I could make sure Gscreen could handle them.

It was exactly what was needed - I have a pretty good idea how to program Gscreen so it is very flexible.

The big changes of industrial seem to have started to die down and now it's starting to be personal choices rather then 'this is wayis tons better'

Between Industrial and Norbert's Gmoccapy we have some good functionality and infrastructure. I'm happy.

Soon it will get to the point where yes if you want _that_ change you'll have to do it on your copy.
But we are a long way from any 2.6 release so there is still plenty of room for changes.

Yes I agree a lock / unlock would be helpful

Chris M

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

More
13 years 8 months ago #29614 by cmorley
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
Now it needs industrial machinists testing.

Anyone using any of Gscreen's different skins please give feedback of what you like and don't like. or what you need that missing.

at the moment I know that tool setting to a common point is missing, I'm just not sure how best to do it.
AXIS uses touch-off and you pre-select whether its for origin setting or tool setting.
I would like something more obvious.
I could have the tool setting buttons show up when the tool table is showing ....

Chris M

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

More
13 years 8 months ago #29615 by cmorley
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
How does every one feel about losing the entry widget and just having the numerical keyboard pop up every time you need to set something?

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

More
13 years 8 months ago #29616 by karlkec
Replied by karlkec on topic Gscreen - a GTK / Glade / Python based screen

cmorley wrote: at the moment I know that tool setting to a common point is missing, I'm just not sure how best to do it.
AXIS uses touch-off and you pre-select whether its for origin setting or tool setting.
I would like something more obvious.
I could have the tool setting buttons show up when the tool table is showing ....
Chris M

I think having it on the tool table page would work well. Include the ability to change tools from there too (tool index button). Could even highlight the row in the tool table matrix for the currently-loaded tool. When a tool is touched off the values in the tool table matrix should update. My thinking is that the tool table page would have everything necessary to set up all the tools in the changer.

Karl

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

Time to create page: 0.225 seconds
Powered by Kunena Forum