On 2023-07-11 01:34 BiT dev <python@altfeld-im.de> wrote:
Possible work-around: --------------------
Proposed by @buhtz:
Spawn a sub process with above example code and check for the SIGABRT signal (or perhaps an expected return code or output).
Impact: - Lower Performance (GUI startup time, diagnostics creation, systray icon creation)
Don't we use this approach only when using "--diagnostics"? Or are there other scenarios where we need this? If it is only "--diganostics" I would say "low" performance is not a big deal. To be sure using the same environment as "backintime-qt" we could parse the start-script. Another dirty hack. Or we modify the start script that way that it optionally use a commandline argument "$1" instead of app.py. By default that script would start the qt frontend (via qt/app.py). But if the name of another py-script is givin via argument this is used instead. It gets dirtier. ;)