GScreen and some understanding gap of hal-widgets
17 Jun 2019 03:43 #137088
by Reinhard
Gerade wollte ich schreiben, dass Deine Fragen eher was für PN sind, aber hier scheint es keine PN zu geben.
Also gut ...
ich lebe in der Märklinstadt und hatte angefangen mir eine selbstentworfene Fräse zu bauen. Dann musste ich meine Werkstatt aufgeben (Haus wurde verkauft) und spiele jetzt mit dem Gedanken, mir eine FM45 oder so zuzulegen.
Ich habe mir ne 5i25 und einige 7i73 zugelegt - ein Bekannter hat mir ein Bitfile erstellt und vom Bohrwerk auf Arbeit weiß ich, dass die Pinole als W-Achse angesprochen wird.
So entstand die Idee für meine Oberfläche. Inspiriert u.a. auch von Heidenhain - bin ein Fan davon
.
Would be nice to use a GTK-Textbuffer like Hal-Actions - as global elements, that can be linked in.
The other option was: add a save button to the edit widget and reload the file in the readonly-widget on leaving edit mode.
But for that I have to learn how to xchange messages between widgets. I want to avoid needless user interactions.
.
.
.
I don't like to spend my time for a panel part, that is shown aside of axis or whatever.
When working on a ui - I want the whole app follow my ideas ...
Qt is the most recent ui system, but is the most instable system too. I never was a friend of Qt.
And together with linuxcnc I was not able to bring the designer to work with hal widgets.
Opposite is true for gscreen. The bad side - it only works with rip-installations.
But ok - if that's the price, I'll go for it. I found docs for pyGtk and some tutorials for glade ...
That's a good starting point.
The bad part: you don't get any meaningful message upon making mistakes.
LinuxCNC shuts down and you have to research why. That's the hard work. So progress will be very very slow - well, at least for me, as I don't know linuxcnc nor python nor gtk nor glade ...
If you don't know any widget system supported by linuxcnc it does not matter, which one to learn. So as glade seems to be the most stable system, its obvious, that more people are interested in glade and gscreen
As I already wrote - I came from mach4, which uses lua as interpreter and wxwindows as widget system. wxwindows has a smart designer too, which creates xml-files and wxlua interprets them.
lua is the fastest interpreter I ever got in touch with. Easy to learn, as lua is almoust C-language.
And wxlua is a lot more stable, than Qt.
May be its easier to create a linuxcnc with wxlua than migrating linuxcnc to python3 ...
Replied by Reinhard on topic GScreen and some understanding gap of hal-widgets
Du darfst mich alles fragendarf ich fragen in welchem kenzeichenbereich du dich befindest
Gerade wollte ich schreiben, dass Deine Fragen eher was für PN sind, aber hier scheint es keine PN zu geben.
Also gut ...
ich lebe in der Märklinstadt und hatte angefangen mir eine selbstentworfene Fräse zu bauen. Dann musste ich meine Werkstatt aufgeben (Haus wurde verkauft) und spiele jetzt mit dem Gedanken, mir eine FM45 oder so zuzulegen.
Ich habe mir ne 5i25 und einige 7i73 zugelegt - ein Bekannter hat mir ein Bitfile erstellt und vom Bohrwerk auf Arbeit weiß ich, dass die Pinole als W-Achse angesprochen wird.
So entstand die Idee für meine Oberfläche. Inspiriert u.a. auch von Heidenhain - bin ein Fan davon
.
no error - just did nothing.sourceview: did it error or just not do anything.
Would be nice to use a GTK-Textbuffer like Hal-Actions - as global elements, that can be linked in.
The other option was: add a save button to the edit widget and reload the file in the readonly-widget on leaving edit mode.
But for that I have to learn how to xchange messages between widgets. I want to avoid needless user interactions.
.
I set the button label to rubbish and the action label to somewhat meaningful - the result was rubbishAction: did you try setting the button label rather then the action label?
.
Thanks for the link. I will dive into it ...Gstat library: linuxcnc.org/docs/devel/html/gui/GStat.html
is what you would use to catch linuxcnc events and act on them.
.
Well, I think, many people may think the way, I did:Gscreen is a project i started a long time ago and was learning how to do things. Only recently has very many people started asking for help with it - it was in the opinion that nobody was interested in it
I don't like to spend my time for a panel part, that is shown aside of axis or whatever.
When working on a ui - I want the whole app follow my ideas ...
Qt is the most recent ui system, but is the most instable system too. I never was a friend of Qt.
And together with linuxcnc I was not able to bring the designer to work with hal widgets.
Opposite is true for gscreen. The bad side - it only works with rip-installations.
But ok - if that's the price, I'll go for it. I found docs for pyGtk and some tutorials for glade ...
That's a good starting point.
The bad part: you don't get any meaningful message upon making mistakes.
LinuxCNC shuts down and you have to research why. That's the hard work. So progress will be very very slow - well, at least for me, as I don't know linuxcnc nor python nor gtk nor glade ...
If you don't know any widget system supported by linuxcnc it does not matter, which one to learn. So as glade seems to be the most stable system, its obvious, that more people are interested in glade and gscreen
As I already wrote - I came from mach4, which uses lua as interpreter and wxwindows as widget system. wxwindows has a smart designer too, which creates xml-files and wxlua interprets them.
lua is the fastest interpreter I ever got in touch with. Easy to learn, as lua is almoust C-language.
And wxlua is a lot more stable, than Qt.
May be its easier to create a linuxcnc with wxlua than migrating linuxcnc to python3 ...
Please Log in or Create an account to join the conversation.
17 Jun 2019 05:50 #137096
by Reinhard
Replied by Reinhard on topic GScreen and some understanding gap of hal-widgets
Ok, so message handling with GSTAT works as described. Thanks!
I was able to handle condensed filename together with entire filename.
But saving edited GCodes by save-action did not work.
... and as I'm not able to access the buffer content - I have to give up
I was able to handle condensed filename together with entire filename.
But saving edited GCodes by save-action did not work.
... and as I'm not able to access the buffer content - I have to give up
Please Log in or Create an account to join the conversation.
17 Jun 2019 06:23 #137099
by cmorley
Great that's a step forward.
Can you explain what you did to try and get save action to save?
My memory of gladevcp is a little hazzy - I didn't think the sourceview was editable as default.
but you can always use the action programmically:
self.widgets.YOUR_action_saveas.emit("activate")
oh and try this:
self.widgets.work_GCodes.set_buffer(self.widgets.edit_GCodes.buf)
Replied by cmorley on topic GScreen and some understanding gap of hal-widgets
Ok, so message handling with GSTAT works as described. Thanks!
I was able to handle condensed filename together with entire filename.
But saving edited GCodes by save-action did not work.
... and as I'm not able to access the buffer content - I have to give up
Great that's a step forward.
Can you explain what you did to try and get save action to save?
My memory of gladevcp is a little hazzy - I didn't think the sourceview was editable as default.
but you can always use the action programmically:
self.widgets.YOUR_action_saveas.emit("activate")
oh and try this:
self.widgets.work_GCodes.set_buffer(self.widgets.edit_GCodes.buf)
Please Log in or Create an account to join the conversation.
17 Jun 2019 06:33 - 17 Jun 2019 06:34 #137101
by Reinhard
Thank you very much!
So I should be able to do the saving on my own ...
Then I activated the "pressed" action in glade designer for that button and added a handler method to my handler class with a print statement - but that did not output any text.
Replied by Reinhard on topic GScreen and some understanding gap of hal-widgets
GREAT! That did the jobself.widgets.work_GCodes.set_buffer(self.widgets.edit_GCodes.buf)
Thank you very much!
So I should be able to do the saving on my own ...
I attached the action to the button, as I did with file open action (which works).Can you explain what you did to try and get save action to save?
Then I activated the "pressed" action in glade designer for that button and added a handler method to my handler class with a print statement - but that did not output any text.
Please Log in or Create an account to join the conversation.
Time to create page: 0.086 seconds