I’m sure I’ve missed an implication but…
Why does the graphic interface toolkit need to be loaded when using the command line interface to execute a SuperTool script?
I’m sure I’ve missed an implication but…
Why does the graphic interface toolkit need to be loaded when using the command line interface to execute a SuperTool script?
Why does the graphic interface toolkit need to be loaded when using the command line interface to execute a SuperTool script?
Maybe this is question to @kku ? Im not sure that I understand your question correctly, but where did you see that?
graphic interface toolkit need to be loaded when using the command line
It seems that in Ubuntu 22.04 the default Gtk version is 4.0. Therefore Gramps needs to specify the correct version (3.0). But it looks like it doesn’t (always?) do that if run in the command line mode.
looks like here ))
I have no answer )))
As far as I understand this has nothing to do with Supertool. When any tool is invoked from the command line the Gramps code executes this import statement:
from gramps.gui.plug import tool
And this causes Gramps to eventually call for example
from gi.repository import Gtk
So some Gtk code is called also in the command line mode - even when it is not used for anything!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.