<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Checking if running as command-line (QCoreApplication) or GUI]]></title><description><![CDATA[<p dir="auto">Is it correct to write:</p>
<pre><code>if (qApp)
{
     // Do gui stuff
}
else
{
    // Do command line stuff
}
</code></pre>
<p dir="auto">Thanks, David</p>
]]></description><link>https://forum.qt.io/topic/165244/checking-if-running-as-command-line-qcoreapplication-or-gui</link><generator>RSS for Node</generator><lastBuildDate>Sun, 22 Nov 2026 18:59:25 GMT</lastBuildDate><atom:link href="https://forum.qt.io/topic/165244.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 06 Nov 2026 11:01:50 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Tue, 10 Nov 2026 10:04:15 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/jonb">@<bdi>JonB</bdi></a> I'm up to my **** in stuff so don't really feel I want to spend the time doing that investigation.</p>
<p dir="auto">It would be informative for sure, but I have to prioritise ...</p>
]]></description><link>https://forum.qt.io/post/840863</link><guid isPermaLink="true">https://forum.qt.io/post/840863</guid><dc:creator><![CDATA[Perdrix]]></dc:creator><pubDate>Tue, 10 Nov 2026 10:04:15 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Tue, 10 Nov 2026 09:46:15 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/perdrix">@<bdi>Perdrix</bdi></a> said in <a href="/post/840860">Checking if running as command-line (QCoreApplication) or GUI</a>:</p>
<blockquote>
<p dir="auto">As far as I (the OP) am concerned this issue is closed. Build for GUI, build separate code for CL, have common base class for issuing messages and subclass for either GUI or CL as needed.</p>
</blockquote>
<p dir="auto">And I asked you whether you had actually tried building/linking your code, with the <code>qApp</code> module, at least under Windows if that is what you use, to see whether it is truly "command line", e.g. does it do redirection like <code>echo abc | yourexecutable &gt; file</code>?  Maybe you don't care, maybe you're not under Windows, whatever: I have said what I can, i leave it to you now.</p>
]]></description><link>https://forum.qt.io/post/840862</link><guid isPermaLink="true">https://forum.qt.io/post/840862</guid><dc:creator><![CDATA[JonB]]></dc:creator><pubDate>Tue, 10 Nov 2026 09:46:15 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Tue, 10 Nov 2026 09:41:16 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/jonb">@<bdi>JonB</bdi></a></p>
<p dir="auto">There's also the difference between the nowadays common "headless" mode for GUI apps and console applications.<br />
Every console app can be considered "headless", but not every headless-capable app is console only... some just don't show any toplevel window, but are still built as a <code>WIN32</code> executable target while running in the background (or as SysTray app process).<br />
So yeah, I think one executable for both worlds is pretty hard to build and maintain [<code>main</code>tain pun not intended :)) ]<br />
-&gt; Speaking of entry points <code>WinMain()</code> vs. <code>main()</code>, console io redirection, window handling etc.</p>
<p dir="auto">There were quite some discussions, but also can't find them right now :))</p>
]]></description><link>https://forum.qt.io/post/840861</link><guid isPermaLink="true">https://forum.qt.io/post/840861</guid><dc:creator><![CDATA[Pl45m4]]></dc:creator><pubDate>Tue, 10 Nov 2026 09:41:16 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Tue, 10 Nov 2026 09:30:41 GMT]]></title><description><![CDATA[<p dir="auto">As far as I (the OP) am concerned this issue is closed. Build for GUI, build separate code for CL, have common base class for issuing messages and subclass for either GUI or CL as needed.</p>
<p dir="auto">D.</p>
]]></description><link>https://forum.qt.io/post/840860</link><guid isPermaLink="true">https://forum.qt.io/post/840860</guid><dc:creator><![CDATA[Perdrix]]></dc:creator><pubDate>Tue, 10 Nov 2026 09:30:41 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Tue, 10 Nov 2026 09:16:07 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/pl45m4">@<bdi>Pl45m4</bdi></a><br />
I entirely agree.  And the conclusion you seem to have come to there is indeed that things either do not quite work or they are at best tricky if you try to make a <code>windows</code>-linked executable behave as a "proper" command-line executable at runtime.</p>
<p dir="auto">Also I cannot spot it but I believe we had another topic discussing this at length recently/a while back and coming to the conclusion that you need a "wrapper" command -line executable to launch the underlying GUI versus command line code executables if you want a single program "entry point".  It may have been your topic but I have a feeling it was a more recent one.</p>
]]></description><link>https://forum.qt.io/post/840857</link><guid isPermaLink="true">https://forum.qt.io/post/840857</guid><dc:creator><![CDATA[JonB]]></dc:creator><pubDate>Tue, 10 Nov 2026 09:16:07 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Tue, 10 Nov 2026 09:10:38 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/jonb">@<bdi>JonB</bdi></a></p>
<p dir="auto">I also referenced it in my topic (<a href="https://forum.qt.io/topic/156995/hybrid-qt-gui-console-cmake-application-on-windows">here</a>) already, where I was playing with hybrid app approaches, because I had the idea of making one app binary in total that would work in CLI and GUI mode.<br />
But it turned out, that you have to add quite some platform specific code (directing IO from/to the console, etc...) to make it look smooth without any bugs and "blinking console windows" in the background.<br />
So I went for a launcher (3-way targets). One GUI binary, one CLI binary and one launcher for convenience where you can select (manually or by arg to make it default -&gt; <code>myAppLauncher.exe -gui</code>)  the mode you want to run. Then it starts the right program.</p>
]]></description><link>https://forum.qt.io/post/840856</link><guid isPermaLink="true">https://forum.qt.io/post/840856</guid><dc:creator><![CDATA[Pl45m4]]></dc:creator><pubDate>Tue, 10 Nov 2026 09:10:38 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Tue, 10 Nov 2026 09:04:56 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/simonschroeder">@<bdi>SimonSchroeder</bdi></a> said in <a href="/post/840853">Checking if running as command-line (QCoreApplication) or GUI</a>:</p>
<blockquote>
<p dir="auto">If I remember correctly, there are ways to reattach the console for a GUI application. I have found some old code of mine like this:</p>
</blockquote>
<p dir="auto">No!  You use <a href="https://learn.microsoft.com/en-us/windows/console/allocconsole" target="_blank" rel="noopener noreferrer nofollow ugc">AllocConsole()</a> which</p>
<blockquote>
<p dir="auto">Allocates a <strong>new</strong> [my bold] console for the calling process.</p>
</blockquote>
<p dir="auto">which does <em>not</em> access the Command Prompt/console from which you invoke it ("reattach the console"), nor can it be used in pipe sequences or with redirection etc.  It is simply a Windows/GUI executable which happens to open its own console for some purpose.</p>
<p dir="auto">VS ships <code>devenv.exe</code> as a <code>windows</code> executable and a <em>completely separate executable</em>, <code>devenv.com</code> as a <code>console</code> one.  Which is precisely what I have been saying/suggesting all along: you need a separate executable, linked as <code>console</code> not <code>windows</code>, for a proper "command line" executable.  And I am <em>suggesting</em> that if code you link with has <code>#include &lt;QApplication&gt;  if (qApp) ...</code> it will <em>have to</em> be <code>windows</code> and therefore not a proper command line, regardless of whether it creates a <code>QApplication</code> or a <code>QCoreApplication</code> at <em>runtime</em>.  Which somebody (perhaps the OP?) who is interested and has Qt for Windows might just like to test....</p>
]]></description><link>https://forum.qt.io/post/840855</link><guid isPermaLink="true">https://forum.qt.io/post/840855</guid><dc:creator><![CDATA[JonB]]></dc:creator><pubDate>Tue, 10 Nov 2026 09:04:56 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Tue, 10 Nov 2026 07:42:48 GMT]]></title><description><![CDATA[<p dir="auto">If I remember correctly, there are ways to reattach the console for a GUI application. I have found some old code of mine like this:</p>
<pre><code>void openConsole()
{
    AllocConsole();
    std::freopen( "CON", "w", stdout );
    std::freopen( "CON", "w", stderr );
    std::freopen( "CON", "r", stdin );
}
</code></pre>
<p dir="auto">This function is called if the GUI application is started in non-GUI mode.</p>
<p dir="auto">However, my solution for an app that works both as command line and GUI application on Windows is to compile two separate binaries. The GUI is the .exe file and the command line version is the .com file (command file). On the command line a .com file is preferred to a .exe file if you just type in the file name without the suffix. Also, I tend to make the non-GUI version the default because the GUI .exe is usually started through a shortcut and the shortcut can be set to always provide a command line paramter <code>-gui</code>. Depending on the flags, both .exe and .com can start the other program if the other mode is requested explicitly. BTW, I learned this behavior von Visual Studio: They ship both a devenv.exe (the regular Visual Studio GUI application) and a <a href="http://devenv.com" target="_blank" rel="noopener noreferrer nofollow ugc">devenv.com</a> (to be used by build tools).</p>
]]></description><link>https://forum.qt.io/post/840853</link><guid isPermaLink="true">https://forum.qt.io/post/840853</guid><dc:creator><![CDATA[SimonSchroeder]]></dc:creator><pubDate>Tue, 10 Nov 2026 07:42:48 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Mon, 09 Nov 2026 17:08:36 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/pl45m4">@<bdi>Pl45m4</bdi></a><br />
Has anyone tried this, especially under Windows, to see what kind of "non-GUI version" you get?  My understanding/suspicion is it will be a <code>windows</code> application (even if it opens no windows/widgets) which does not use/cannot access the console from which it is run, does not have open stdin/out/err and so on?  Based on how MSVC non-Qt applications work.</p>
]]></description><link>https://forum.qt.io/post/840850</link><guid isPermaLink="true">https://forum.qt.io/post/840850</guid><dc:creator><![CDATA[JonB]]></dc:creator><pubDate>Mon, 09 Nov 2026 17:08:36 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Mon, 09 Nov 2026 16:11:25 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/perdrix">@<bdi>Perdrix</bdi></a></p>
<p dir="auto">What about this:</p>
<pre><code>QCoreApplication* createApplication(int &amp;argc, char *argv[])
{
    for (int i = 1; i &lt; argc; ++i) {
        if (!qstrcmp(argv[i], "-no-gui"))
            return new QCoreApplication(argc, argv);
    }
    return new QApplication(argc, argv);
}

int main(int argc, char* argv[])
{
    QScopedPointer&lt;QCoreApplication&gt; app(createApplication(argc, argv));

    if (qobject_cast&lt;QApplication *&gt;(app.data())) {
       // start GUI version...
    } else {
       // start non-GUI version...
    }

    return app-&gt;exec();
}
</code></pre>
<p dir="auto">(from: <a href="https://doc.qt.io/qt-6/qapplication.html#details" target="_blank" rel="noopener noreferrer nofollow ugc">https://doc.qt.io/qt-6/qapplication.html#details</a>)</p>
]]></description><link>https://forum.qt.io/post/840847</link><guid isPermaLink="true">https://forum.qt.io/post/840847</guid><dc:creator><![CDATA[Pl45m4]]></dc:creator><pubDate>Mon, 09 Nov 2026 16:11:25 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Sun, 08 Nov 2026 12:23:02 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/perdrix">@<bdi>Perdrix</bdi></a> So you <em>can</em> do your "use a message box for GUI and cout for command line" if you wish.  Just saying.</p>
]]></description><link>https://forum.qt.io/post/840839</link><guid isPermaLink="true">https://forum.qt.io/post/840839</guid><dc:creator><![CDATA[JonB]]></dc:creator><pubDate>Sun, 08 Nov 2026 12:23:02 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Sun, 08 Nov 2026 10:44:29 GMT]]></title><description><![CDATA[<p dir="auto">Indeed so.</p>
]]></description><link>https://forum.qt.io/post/840838</link><guid isPermaLink="true">https://forum.qt.io/post/840838</guid><dc:creator><![CDATA[Perdrix]]></dc:creator><pubDate>Sun, 08 Nov 2026 10:44:29 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Sun, 08 Nov 2026 10:35:59 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/perdrix">@<bdi>Perdrix</bdi></a><br />
This is the sort of thing I was trying to discuss with you once you start trying to use <code>qApp</code> from a command-line executable.</p>
<blockquote>
<p dir="auto">I wanted to use a message box for GUI and cout for command line, but of course the command line code isn't going to be linked with the libraries necessary to use QMessageBox.</p>
</blockquote>
<p dir="auto">You implement this requirement via pointers-to-functions or subclassing-virtual-methods.  It's a common paradigm.  So that your code calls something like <code>utilty.alert("Message")</code> and that ends up calling either the GUI or the command-line implementation depending what function <code>alert()</code> pointer/virtual resolves to as set in construction/start-up.   That keeps the command-line from needing to include/link with anything GUI.</p>
]]></description><link>https://forum.qt.io/post/840837</link><guid isPermaLink="true">https://forum.qt.io/post/840837</guid><dc:creator><![CDATA[JonB]]></dc:creator><pubDate>Sun, 08 Nov 2026 10:35:59 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Sun, 08 Nov 2026 10:14:17 GMT]]></title><description><![CDATA[<p dir="auto">After further experiments this seems to be a non-starter.  I wanted to use a message box for GUI and cout for command line, but of course the command line code isn't going to be linked with the libraries necessary to use QMessageBox.</p>
<p dir="auto">Hey ho! Compile time checks ...</p>
]]></description><link>https://forum.qt.io/post/840836</link><guid isPermaLink="true">https://forum.qt.io/post/840836</guid><dc:creator><![CDATA[Perdrix]]></dc:creator><pubDate>Sun, 08 Nov 2026 10:14:17 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Sat, 07 Nov 2026 09:37:28 GMT]]></title><description><![CDATA[<p dir="auto">I still think the wording is open to my interpretation, however I have now defined my own convenience macro:</p>
<pre><code>//
// Define a convenience macro for checking if we're using a Qt GUI or command line application
// 
#define qtGUI (dynamic_cast&lt;QApplication *&gt;(QCoreApplication::instance()))
</code></pre>
]]></description><link>https://forum.qt.io/post/840823</link><guid isPermaLink="true">https://forum.qt.io/post/840823</guid><dc:creator><![CDATA[Perdrix]]></dc:creator><pubDate>Sat, 07 Nov 2026 09:37:28 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Sat, 07 Nov 2026 09:32:23 GMT]]></title><description><![CDATA[<p dir="auto">"only valid" = undefined if the precondition is not met.</p>
<p dir="auto">/edit:<br />
valid pointer - a pointer to an object which is not yet deleted and has the correct class<br />
invalid / not valid pointer - a pointer to an object which was already deleted or has an incorrect class<br />
nullptr - a pointer to null</p>
]]></description><link>https://forum.qt.io/post/840822</link><guid isPermaLink="true">https://forum.qt.io/post/840822</guid><dc:creator><![CDATA[Christian Ehrlicher]]></dc:creator><pubDate>Sat, 07 Nov 2026 09:32:23 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Sat, 07 Nov 2026 09:23:42 GMT]]></title><description><![CDATA[<p dir="auto">The docs say nothing about undefined.</p>
]]></description><link>https://forum.qt.io/post/840821</link><guid isPermaLink="true">https://forum.qt.io/post/840821</guid><dc:creator><![CDATA[Perdrix]]></dc:creator><pubDate>Sat, 07 Nov 2026 09:23:42 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Sat, 07 Nov 2026 09:23:23 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/perdrix">@<bdi>Perdrix</bdi></a> said in <a href="/post/840819">Checking if running as command-line (QCoreApplication) or GUI</a>:</p>
<blockquote>
<p dir="auto">Which clearly said to me that it would be null if the application object is just a QCoreApplication...</p>
</blockquote>
<p dir="auto">undefined and a nullptr are two completely different things in c++ - the docs are very clear here.<br />
<a href="https://en.cppreference.com/cpp/language/ub" target="_blank" rel="noopener noreferrer nofollow ugc">https://en.cppreference.com/cpp/language/ub</a></p>
]]></description><link>https://forum.qt.io/post/840820</link><guid isPermaLink="true">https://forum.qt.io/post/840820</guid><dc:creator><![CDATA[Christian Ehrlicher]]></dc:creator><pubDate>Sat, 07 Nov 2026 09:23:23 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Sat, 07 Nov 2026 09:17:38 GMT]]></title><description><![CDATA[<p dir="auto">Which clearly said to me that it would be null if the application object is just a QCoreApplication...</p>
<p dir="auto">So the docs really could be clearer (state that is it using a static_cast&lt;&gt;), or change the code to use a dynamic_cast&lt;&gt;!</p>
]]></description><link>https://forum.qt.io/post/840819</link><guid isPermaLink="true">https://forum.qt.io/post/840819</guid><dc:creator><![CDATA[Perdrix]]></dc:creator><pubDate>Sat, 07 Nov 2026 09:17:38 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Sat, 07 Nov 2026 09:14:58 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/perdrix">@<bdi>Perdrix</bdi></a> said in <a href="/post/840817">Checking if running as command-line (QCoreApplication) or GUI</a>:</p>
<blockquote>
<pre><code> from the documentation I had expected the macro to use a dynamic_cast&lt;&gt;
</code></pre>
</blockquote>
<p dir="auto">Why? It's clearly stated:</p>
<p dir="auto">"so only valid when the unique application object is a QApplication."</p>
]]></description><link>https://forum.qt.io/post/840818</link><guid isPermaLink="true">https://forum.qt.io/post/840818</guid><dc:creator><![CDATA[Christian Ehrlicher]]></dc:creator><pubDate>Sat, 07 Nov 2026 09:14:58 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Sat, 07 Nov 2026 09:12:38 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/christian-ehrlicher">@<bdi>Christian-Ehrlicher</bdi></a> Well that's quite a surprise - from the documentation I had expected the macro to use a dynamic_cast&lt;&gt;</p>
]]></description><link>https://forum.qt.io/post/840817</link><guid isPermaLink="true">https://forum.qt.io/post/840817</guid><dc:creator><![CDATA[Perdrix]]></dc:creator><pubDate>Sat, 07 Nov 2026 09:12:38 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Sat, 07 Nov 2026 09:01:14 GMT]]></title><description><![CDATA[<p dir="auto">As you can see here: <a href="https://doc.qt.io/qt-6/qapplication.html#qApp" target="_blank" rel="noopener noreferrer nofollow ugc">https://doc.qt.io/qt-6/qapplication.html#qApp</a> - qApp is not valid (undefined) when no QApplication instance exixst. When you simply look at the definition you will see what is happening:</p>
<pre><code>#define qApp (static_cast&lt;QApplication *&gt;(QCoreApplication::instance()))
</code></pre>
<p dir="auto">So no, it will not work and you will have to do it by yourself by calling dynamic_cast&lt;&gt; on the QCoreApplication::instance()</p>
]]></description><link>https://forum.qt.io/post/840814</link><guid isPermaLink="true">https://forum.qt.io/post/840814</guid><dc:creator><![CDATA[Christian Ehrlicher]]></dc:creator><pubDate>Sat, 07 Nov 2026 09:01:14 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Sat, 07 Nov 2026 08:41:41 GMT]]></title><description><![CDATA[<p dir="auto">They are completely independent executables each with their own main()</p>
]]></description><link>https://forum.qt.io/post/840812</link><guid isPermaLink="true">https://forum.qt.io/post/840812</guid><dc:creator><![CDATA[Perdrix]]></dc:creator><pubDate>Sat, 07 Nov 2026 08:41:41 GMT</pubDate></item><item><title><![CDATA[Reply to Checking if running as command-line (QCoreApplication) or GUI on Fri, 06 Nov 2026 19:05:19 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/perdrix">@<bdi>Perdrix</bdi></a> said in <a href="/post/840800">Checking if running as command-line (QCoreApplication) or GUI</a>:</p>
<blockquote>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/jonb">@<bdi>JonB</bdi></a> I build a GUI application which instantiates a QApplication in its main(), and a completely different piece of code is used for the command line application which creates a QCoreApplication.</p>
<p dir="auto">So I think that qApp will work in that case?</p>
</blockquote>
<p dir="auto">Hi,</p>
<p dir="auto">Something is not clear: are you starting both the CLI and the GUI from the same main function ?</p>
]]></description><link>https://forum.qt.io/post/840803</link><guid isPermaLink="true">https://forum.qt.io/post/840803</guid><dc:creator><![CDATA[SGaist]]></dc:creator><pubDate>Fri, 06 Nov 2026 19:05:19 GMT</pubDate></item></channel></rss>