In a recent thread, a Python script was offered as a simple way to troubleshoot settings.
However, the 1st option used the built-in Python Evaluation gramplet. Which is only available in debug mode.
The 2nd option was to use a SuperTool script. But that is an add-on that isn’t in repositories searched by the old Plugin Manager or new Addon Manager. And the print output is routed to the Terminal/Console. (Which isn’t necessarily active. Kari @kku is open to suggestions about the stdout output of SuperTool. ) (The Capture output feature was added to SuperTool v1.4.7 to display this info.)
Even if I could figure out how to use Python Shell addon gramplet (not likely), the print output for the gramplet also goes to the Console.
What would be the preferred approach? Mirror the output and pop open a window for that stream? Use the log and leverage the StatusBar indicator?
I have already implemented “print output capture” in Supertool (print output will be displayed in the Supertool UI). Still missing are the documentation and upload to Github. So this is my approach to this problem
ti 9. heinäk. 2024 klo 19.58 Brian McCullough via The Gramps Project (Discourse Forum & Mailing List) (notifications@gramps.discoursemail.com) kirjoitti:
Hopefully in a few days. But unfortunately I found an unexpected problem and I don’t yet know how to fix it.
ke 10. heinäk. 2024 klo 16.57 Brian McCullough via The Gramps Project (Discourse Forum & Mailing List) (notifications@gramps.discoursemail.com) kirjoitti:
By the bye, I really like your idea to open the SuperTool script Note from within the GUI. The current 3-line windows (for Initialization statements and Statements executed) can induce a bit of claustrophobia. And although the Python Evaluation gramplet has 9 lines, I really prefer SuperTool’s script saving and help features.
ke 10. heinäk. 2024 klo 16.57 Brian McCullough via The Gramps Project (Discourse Forum & Mailing List) (notifications@gramps.discoursemail.com) kirjoitti:
