<?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[QFileDialog name filter on Linux]]></title><description><![CDATA[<p dir="auto">If I set a name filter for QFileDialog that looks like:</p>
<pre><code>"RAW Files (*.cr2 *.cr3 *.crw *.nef *.mrw *.orf *.raf *.pef *.x3f *.dcr *.kdc *.srf *.arw *.raw *.dng *.ia *.rw2)"
</code></pre>
<p dir="auto">on Windows and macOS I am shown (e.g.) files with extensions of .cr2 and .CR2</p>
<p dir="auto">On Linux Ubuntu 24.04.3 (Noble Numbat)  and Linux Mint (which uses Thunar) I am only shown files with extensions .cr2.<br />
On Lubuntu (which uses PCmanFM-Qt file manager) I am shown files with both .cr2 and .CR2 extensions.</p>
<p dir="auto">Should I expect this level on inconsistency between the different Linux systems?</p>
<p dir="auto">Do I <em>really</em> need to specify (e.g. for .raf files) .raf, .RAF, .Raf, .rAf, .raF, etc. etc.)</p>
<p dir="auto">Thanks, David</p>
]]></description><link>https://forum.qt.io/topic/163593/qfiledialog-name-filter-on-linux</link><generator>RSS for Node</generator><lastBuildDate>Tue, 21 Apr 2026 14:25:39 GMT</lastBuildDate><atom:link href="https://forum.qt.io/topic/163593.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 28 Oct 2025 03:19:26 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to QFileDialog name filter on Linux on Wed, 29 Oct 2025 11:43:46 GMT]]></title><description><![CDATA[<p dir="auto">When the platform plugin provides a native file dialog then it is used, otherwise the Qt one is shown.</p>
]]></description><link>https://forum.qt.io/post/833192</link><guid isPermaLink="true">https://forum.qt.io/post/833192</guid><dc:creator><![CDATA[Christian Ehrlicher]]></dc:creator><pubDate>Wed, 29 Oct 2025 11:43:46 GMT</pubDate></item><item><title><![CDATA[Reply to QFileDialog name filter on Linux on Wed, 29 Oct 2025 11:39:13 GMT]]></title><description><![CDATA[<p dir="auto">Odd I don't request the Qt internal FileDialog explicitly.   I thought that Qt always used the native one unless asked.</p>
<p dir="auto">I'll change the code to always ask for the Qt version.</p>
]]></description><link>https://forum.qt.io/post/833191</link><guid isPermaLink="true">https://forum.qt.io/post/833191</guid><dc:creator><![CDATA[Perdrix]]></dc:creator><pubDate>Wed, 29 Oct 2025 11:39:13 GMT</pubDate></item><item><title><![CDATA[Reply to QFileDialog name filter on Linux on Wed, 29 Oct 2025 11:28:11 GMT]]></title><description><![CDATA[<p dir="auto">The first one is from Qt, the second from your platform aka the native (gtk) one.</p>
]]></description><link>https://forum.qt.io/post/833190</link><guid isPermaLink="true">https://forum.qt.io/post/833190</guid><dc:creator><![CDATA[Christian Ehrlicher]]></dc:creator><pubDate>Wed, 29 Oct 2025 11:28:11 GMT</pubDate></item><item><title><![CDATA[Reply to QFileDialog name filter on Linux on Wed, 29 Oct 2025 11:19:51 GMT]]></title><description><![CDATA[<p dir="auto">Except!  Running on Noble Numbat.</p>
<p dir="auto">DeepSkyStacker 6.1.0 which uses Qt 6.9.2 displays both .cr2 and .CR2 files with that name filter:<br />
<img src="https://ddgobkiprc33d.cloudfront.net/2e124213-8771-4c10-a26a-21f7c377b35e.png" alt="image.png" class=" img-fluid img-markdown" /><br />
whereas Qt 6.1.1 Beta 2 which uses 6.10.0 only displays .cr2 files with that name filter:<br />
<img src="https://ddgobkiprc33d.cloudfront.net/b0e89288-97fe-4bfb-904e-bf07e46d8069.png" alt="image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">So for me, that's a breaking change.</p>
<p dir="auto">I also see that the displayed file dialogue is completely different which is quite surprising.</p>
<p dir="auto">David</p>
]]></description><link>https://forum.qt.io/post/833189</link><guid isPermaLink="true">https://forum.qt.io/post/833189</guid><dc:creator><![CDATA[Perdrix]]></dc:creator><pubDate>Wed, 29 Oct 2025 11:19:51 GMT</pubDate></item><item><title><![CDATA[Reply to QFileDialog name filter on Linux on Tue, 28 Oct 2025 14:00:26 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/jonb">@<bdi>JonB</bdi></a> said in <a href="/post/833166">QFileDialog name filter on Linux</a>:</p>
<blockquote>
<p dir="auto">I do not know about MacOS or Lubuntu</p>
</blockquote>
<p dir="auto">macOS is also case insensitive (well, technically you can format APFS partitions as case sensitive if you really want to, but then all kind of things break).</p>
<p dir="auto">Lubuntu is a Linux distribution running LXQt as the desktop environment (a minor lightweight DE written in Qt). The difference from Ubuntu/Mint is that the latter two automatically use the gtk3 platform theme plugin shipped with Qt, and therefore you get the Gtk file picker dialogs. In Lubuntu, it is possible that you'll get the different native file picker (if there is an alternative theme plugin configured), or the non-native one built-in. Whether non case sensitive filter matching is to be expected or not depends on that.</p>
]]></description><link>https://forum.qt.io/post/833174</link><guid isPermaLink="true">https://forum.qt.io/post/833174</guid><dc:creator><![CDATA[IgKh]]></dc:creator><pubDate>Tue, 28 Oct 2025 14:00:26 GMT</pubDate></item><item><title><![CDATA[Reply to QFileDialog name filter on Linux on Tue, 28 Oct 2025 08:16:35 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/perdrix">@<bdi>Perdrix</bdi></a><br />
Since Linux filing systems are case sensitive I would expect only to be shown files matching the case of the filter.  I do not know about MacOS or Lubuntu.  More to the point under Linux a, say, <code>.tar</code> file should always be spelt as such, so how/why would you start with a <code>.Tar</code> or a <code>.TAR</code> file in the first place?  I would be surprised at that.</p>
<p dir="auto">You do not say whether you are using the native file dialog or the Qt one.  I <em>believe</em> the filtering is handled internally in native dialogs so this is vital to behaviour.  If it is and you are using native then it has nothing to do with Qt and you should be able to examine/replicate the behaviour in any program.</p>
<p dir="auto">If you ensure you are using the Qt file dialog do you get consistent behaviour?</p>
]]></description><link>https://forum.qt.io/post/833166</link><guid isPermaLink="true">https://forum.qt.io/post/833166</guid><dc:creator><![CDATA[JonB]]></dc:creator><pubDate>Tue, 28 Oct 2025 08:16:35 GMT</pubDate></item></channel></rss>