<?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[Custom QQuickPaintedItem looks bad on Raspberry Pi]]></title><description><![CDATA[<p dir="auto">Hello all,<br />
I wrote a QtQml-based application for a Raspberry Pi 2B+ earlier this year, with plenty of help from these forums :) It's a data recorder for sampling electric values.</p>
<p dir="auto">I'm expanding its capabilities, and have run into a problem.  It can now support over 240 separate values.  Originally I used a custom QQuickPaintedItem, and put in a Flickable so users could scroll through the values.  When I run the new version with 240 values, the text becomes blurry, like it's been resized.</p>
<p dir="auto">I have some screenshots that show what I mean: <a href="https://imgur.com/a/w1LWQ" target="_blank" rel="noopener noreferrer nofollow ugc">https://imgur.com/a/w1LWQ</a></p>
<p dir="auto">My QQuickPaintedItem draws onto a QImage.  It appears that when the QImage's height is greater than 2048 pixels, it gets blurry/resized.  I wonder if this is related to the Pi's maximum texture size of 2048?</p>
<p dir="auto">Can anyone point me in the right direction for making my images not look like a blurry mess?</p>
]]></description><link>https://forum.qt.io/topic/83954/custom-qquickpainteditem-looks-bad-on-raspberry-pi</link><generator>RSS for Node</generator><lastBuildDate>Sat, 24 Oct 2026 02:17:37 GMT</lastBuildDate><atom:link href="https://forum.qt.io/topic/83954.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 06 Oct 2017 21:51:03 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Custom QQuickPaintedItem looks bad on Raspberry Pi on Tue, 10 Oct 2017 21:20:07 GMT]]></title><description><![CDATA[<p dir="auto">Sorry i´m just using the QImage generated by poppler. I have no control about the generator.</p>
]]></description><link>https://forum.qt.io/post/420003</link><guid isPermaLink="true">https://forum.qt.io/post/420003</guid><dc:creator><![CDATA[sneubert]]></dc:creator><pubDate>Tue, 10 Oct 2017 21:20:07 GMT</pubDate></item><item><title><![CDATA[Reply to Custom QQuickPaintedItem looks bad on Raspberry Pi on Tue, 10 Oct 2017 14:09:48 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/sneubert">@<bdi>sneubert</bdi></a> Wow that's pretty big.  Do you have any other tips for getting good quality? Like maybe the format used for QImage?</p>
]]></description><link>https://forum.qt.io/post/419940</link><guid isPermaLink="true">https://forum.qt.io/post/419940</guid><dc:creator><![CDATA[StoatPatronus]]></dc:creator><pubDate>Tue, 10 Oct 2017 14:09:48 GMT</pubDate></item><item><title><![CDATA[Reply to Custom QQuickPaintedItem looks bad on Raspberry Pi on Tue, 10 Oct 2017 04:25:56 GMT]]></title><description><![CDATA[<p dir="auto">I rendered pdf DIN A4 pages with 600 dpi via poppler</p>
]]></description><link>https://forum.qt.io/post/419767</link><guid isPermaLink="true">https://forum.qt.io/post/419767</guid><dc:creator><![CDATA[sneubert]]></dc:creator><pubDate>Tue, 10 Oct 2017 04:25:56 GMT</pubDate></item><item><title><![CDATA[Reply to Custom QQuickPaintedItem looks bad on Raspberry Pi on Mon, 09 Oct 2017 17:43:22 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/sneubert">@<bdi>sneubert</bdi></a> How big were your images?  I tried setting the GPU memory to 256M, but it didn't make any difference.</p>
]]></description><link>https://forum.qt.io/post/419720</link><guid isPermaLink="true">https://forum.qt.io/post/419720</guid><dc:creator><![CDATA[StoatPatronus]]></dc:creator><pubDate>Mon, 09 Oct 2017 17:43:22 GMT</pubDate></item><item><title><![CDATA[Reply to Custom QQuickPaintedItem looks bad on Raspberry Pi on Mon, 09 Oct 2017 07:13:42 GMT]]></title><description><![CDATA[<p dir="auto">Just a guess, but I also had some issues displaying  QQuickPaintedItem with<br />
large images and it turned out, that the memory split was at a low value.<br />
After changing it to e.g. 256 M, the Images got displayed correctly.</p>
]]></description><link>https://forum.qt.io/post/419530</link><guid isPermaLink="true">https://forum.qt.io/post/419530</guid><dc:creator><![CDATA[sneubert]]></dc:creator><pubDate>Mon, 09 Oct 2017 07:13:42 GMT</pubDate></item><item><title><![CDATA[Reply to Custom QQuickPaintedItem looks bad on Raspberry Pi on Sun, 08 Oct 2017 01:44:30 GMT]]></title><description><![CDATA[<p dir="auto">I had considered a listview, and cannot recall now why I decided against using it.  I will investigate it again.</p>
]]></description><link>https://forum.qt.io/post/419376</link><guid isPermaLink="true">https://forum.qt.io/post/419376</guid><dc:creator><![CDATA[StoatPatronus]]></dc:creator><pubDate>Sun, 08 Oct 2017 01:44:30 GMT</pubDate></item><item><title><![CDATA[Reply to Custom QQuickPaintedItem looks bad on Raspberry Pi on Fri, 06 Oct 2017 22:05:37 GMT]]></title><description><![CDATA[<p dir="auto">Hi! Not sure what causes it, but your texture-size guess sounds reasonable. For the solution: Wouldn't it be easier anyway to replace the huge image with a listview?</p>
]]></description><link>https://forum.qt.io/post/419261</link><guid isPermaLink="true">https://forum.qt.io/post/419261</guid><dc:creator><![CDATA[[[global:former-user]]]]></dc:creator><pubDate>Fri, 06 Oct 2017 22:05:37 GMT</pubDate></item></channel></rss>