<?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[How to tame clang issues after upgrading to Qt Creator 7.0.2?]]></title><description><![CDATA[<p dir="auto">I have been using Qt Creator for several years.  Recently I upgraded to the latest version, 7.0.2 and frankly for me it feels like the wheels have fallen off!  I understand clang is doing more with this version by default, but I had enabled it previously without experiencing the issues I have now.</p>
<ol>
<li>My C++ code all seems to be treated like C so I have annoying decorations everywhere in my source telling me keywords like 'class' and 'public' are not valid.</li>
<li>In many many files, my F2 functionality (follow symbol or open header) is broken.</li>
<li>(unrelated to clang) With every file I open I have to choose the encoding before I'm able to edit the file.  If I close that file and reopen I have to choose the encoding all over again.  Why is this?  I don't remember having to do this before.</li>
</ol>
<p dir="auto">If I disable clangd, the above issues go away but I lose the code completion feature that I've been enjoying all these years.</p>
<p dir="auto">One clue I have is that now I can with each editor pane select 'clangd' or 'clangd for &lt;myproject&gt;'.  When I choose 'clangd' I get all the annoying errors about e.g. class and public not being valid keywords.  When I select 'clangd for &lt;myproject&gt;' I seemingly lose my F2 functionality and still get incorrect clang warnings, though not as many.</p>
<p dir="auto">Is there a guide or some suggestions on how to tame these newfound problems?  Overall it feels like a step backwards from the previous version I was using.</p>
<p dir="auto">On a positive note, I really like the extra CMake features with this release!</p>
<p dir="auto">Thanks,<br />
Rich</p>
]]></description><link>https://forum.qt.io/topic/136795/how-to-tame-clang-issues-after-upgrading-to-qt-creator-7-0-2</link><generator>RSS for Node</generator><lastBuildDate>Tue, 05 May 2026 18:16:07 GMT</lastBuildDate><atom:link href="https://forum.qt.io/topic/136795.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 26 May 2022 15:24:11 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to How to tame clang issues after upgrading to Qt Creator 7.0.2? on Thu, 26 May 2022 15:48:24 GMT]]></title><description><![CDATA[<p dir="auto">Also, I see now from this [1] that Qt Creator doesn't try to detect encodings if the file is not UTF-8 encoded.  I'm not sure why this wasn't an issue for me before upgrading to 7.0.2, but I understand why it keeps pestering me now.</p>
<p dir="auto">[1] <a href="https://doc.qt.io/qtcreator/creator-editor-options-text.html" target="_blank" rel="noopener noreferrer nofollow ugc">https://doc.qt.io/qtcreator/creator-editor-options-text.html</a></p>
]]></description><link>https://forum.qt.io/post/715470</link><guid isPermaLink="true">https://forum.qt.io/post/715470</guid><dc:creator><![CDATA[Rich v]]></dc:creator><pubDate>Thu, 26 May 2022 15:48:24 GMT</pubDate></item><item><title><![CDATA[Reply to How to tame clang issues after upgrading to Qt Creator 7.0.2? on Thu, 26 May 2022 15:39:05 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/rich-v">@<bdi>Rich-v</bdi></a><br />
I found the blog related to this release here [1].  I disabled indexing with clangd  and that seems to have made things better for #1 and #2.</p>
<p dir="auto">[1] <a href="https://www.qt.io/blog/qt-creator-7-released" target="_blank" rel="noopener noreferrer nofollow ugc">https://www.qt.io/blog/qt-creator-7-released</a></p>
]]></description><link>https://forum.qt.io/post/715467</link><guid isPermaLink="true">https://forum.qt.io/post/715467</guid><dc:creator><![CDATA[Rich v]]></dc:creator><pubDate>Thu, 26 May 2022 15:39:05 GMT</pubDate></item></channel></rss>