<?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[Qt Creator Rant]]></title><description><![CDATA[<p dir="auto">Everytime there is some weird thing going on in my code, i know somehow, somewhere along the way Qt Creator fucked up.</p>
<p dir="auto">If anything weird happens the first thing i do is to to delete my whole build folder. Most of the time that solves the problem.</p>
<p dir="auto">Recently I changed my pro file. I wanted to delete CONFIG += console and add CONFIG -= console. Saved it, it said it saved it, i hit build and ... it build too fast. Turns out that it didnt recompile my code, as i see from the creation time. So i had to add a whitespace, then delete it inside an cpp file to make it take my change.</p>
<p dir="auto">Things like these cost me production time. And thats just one example of many.</p>
]]></description><link>https://forum.qt.io/topic/139623/qt-creator-rant</link><generator>RSS for Node</generator><lastBuildDate>Sun, 25 Oct 2026 12:49:25 GMT</lastBuildDate><atom:link href="https://forum.qt.io/topic/139623.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 27 Sep 2022 17:30:35 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Qt Creator Rant on Tue, 27 Sep 2022 18:02:13 GMT]]></title><description><![CDATA[<p dir="auto">After editing anything in the pro file it's often required to re-run qmake manually for any change to be noticed (Build -&gt; Run qmake). This shouldn't work like that of course. It's been reported and claimed to be fixed many many times, but it's still the case and personally I just learned to live with it. I assigned a shortcut to it, so whenever I edit pro file I hit save and rerun qmake shortcuts. It takes one extra keystroke and it became muscle memory for me, so I don't even think about it anymore.</p>
<p dir="auto">But yeah, if you have a repro example report a bug. Maybe one day it'll be fixed for good, but as Christian said complaining here on the forum won't do you any good.</p>
]]></description><link>https://forum.qt.io/post/730389</link><guid isPermaLink="true">https://forum.qt.io/post/730389</guid><dc:creator><![CDATA[Chris Kawa]]></dc:creator><pubDate>Tue, 27 Sep 2022 18:02:13 GMT</pubDate></item><item><title><![CDATA[Reply to Qt Creator Rant on Tue, 27 Sep 2022 17:35:16 GMT]]></title><description><![CDATA[<p dir="auto">Wouldn't it be better to report good <a href="https://bugreports.qt.io/secure/Dashboard.jspa" target="_blank" rel="noopener noreferrer nofollow ugc">bug reports</a> so the issues get fixed instead writing something to a user forum where just with some luck the developers will see your issue?</p>
]]></description><link>https://forum.qt.io/post/730385</link><guid isPermaLink="true">https://forum.qt.io/post/730385</guid><dc:creator><![CDATA[Christian Ehrlicher]]></dc:creator><pubDate>Tue, 27 Sep 2022 17:35:16 GMT</pubDate></item></channel></rss>