pyngcgui
27 Dec 2013 07:26 #42049
by cmorley
Warning developer talk
Fullscreen with dialogs (the pop up keyboard is a dialog) is very difficult to get right.
It's the way GTK handles fullscreen and dialogs.
The dialog must have a reference to the main window, which I don't think is possible when the window is embedded.
The Gcode save-as dialog shows a similar problem (the menu panels show) which I can't fix (at least so far)
I should look at the PYNCGGUI's code for the dialog - maybe if it references a container that is embedded.....hmm
It would be better if PYNCGGUI was a widget, then
a) we wouldn't need the pop up window, (could use Gmoccapy's on screen keyboard)
b) if we did, we could pop one from the main window and send the commands to PYNCGUI.
Another possible fix is to have one of the program check to see if the dialog is hidden and re - realize it.
never looked at the details of that.
So unless I'm missing something I think (at the moment) your stuck with maximum screen if you wish to use the pop up keyboard.
Chris M
Fullscreen with dialogs (the pop up keyboard is a dialog) is very difficult to get right.
It's the way GTK handles fullscreen and dialogs.
The dialog must have a reference to the main window, which I don't think is possible when the window is embedded.
The Gcode save-as dialog shows a similar problem (the menu panels show) which I can't fix (at least so far)
I should look at the PYNCGGUI's code for the dialog - maybe if it references a container that is embedded.....hmm
It would be better if PYNCGGUI was a widget, then
a) we wouldn't need the pop up window, (could use Gmoccapy's on screen keyboard)
b) if we did, we could pop one from the main window and send the commands to PYNCGUI.
Another possible fix is to have one of the program check to see if the dialog is hidden and re - realize it.
never looked at the details of that.
So unless I'm missing something I think (at the moment) your stuck with maximum screen if you wish to use the pop up keyboard.
Chris M
Please Log in or Create an account to join the conversation.
28 Dec 2013 04:21 #42077
by newbynobi
Hallo Chris,
I think there is an easy solution: I use my "notification" for error reporting and even in fullscreen, the "window" stays in front!
My notification is a popup window! So why not put the dialogs that give problems in popup windows?
notification is not jet a glade widget! But the code can be found under:
It should be easy to fit the keyboard to the popup window.
Norbert
I think there is an easy solution: I use my "notification" for error reporting and even in fullscreen, the "window" stays in front!
My notification is a popup window! So why not put the dialogs that give problems in popup windows?
notification is not jet a glade widget! But the code can be found under:
/linuxcnc-dev/share/gscreen/skins/gmoccapy/python/notification.py
It should be easy to fit the keyboard to the popup window.
Norbert
Please Log in or Create an account to join the conversation.
20 Mar 2014 19:24 #45011
by mariusl
Regards
Marius
www.bluearccnc.com
Hi Dewey
I have noticed that since Norbert went solo with Gmoccapy your pyngcgui examples have disappeared from the sim directories. Is there a way for this to be fixed or do you want it to be removed?
I have noticed that since Norbert went solo with Gmoccapy your pyngcgui examples have disappeared from the sim directories. Is there a way for this to be fixed or do you want it to be removed?
Regards
Marius
www.bluearccnc.com
Please Log in or Create an account to join the conversation.
Time to create page: 0.136 seconds