The icons provided from the system also go through a similar process of
choosing the right size for what you request. If you request something specific
by setting the sourceSize you will affect this, so please just set
widht/heigth, as that should work. (If it doesn’t please file a bug with a
OK, thank you. We do use SVGs (but sometimes also PNGs).
However, these PNGs I was talking about in the original posting are
files icons from system. I can't replace them with SVGs. :)
On 3/27/2021 9:51 AM, Nuno Santos wrote:
I had the same problem with blurry images on retina displays. I
I had the same problem with blurry images on retina displays. I ended up
creating a image component that inside was by default setting source size for
twice the width and height of the item size to have good results on iOS screens.
However..
I have recently found that replacing the pngs
This all is not about my question in any matter. I do not care about SVG
at all. And SVG are not used in this example.
Please learn to read question before answering
On 3/23/2021 4:16 PM, Jérôme Godbout wrote:
Do you really need to same memory by reducing the source size? I think
you
] QML Image size vs sourceSize strange things
Il 23/03/21 14:16, Jérôme Godbout ha scritto:
> Do you really need to same memory by reducing the source size? I think
> you should left the source size alone and sample the image from the full
> source. Source size for SVG doesn’t make any se
Il 23/03/21 14:16, Jérôme Godbout ha scritto:
Do you really need to same memory by reducing the source size? I think
you should left the source size alone and sample the image from the full
source. Source size for SVG doesn’t make any sense, it’s vectoriel,
doesn’t have any size, it can scale
Do you really need to same memory by reducing the source size? I think you
should left the source size alone and sample the image from the full source.
Source size for SVG doesn’t make any sense, it’s vectoriel, doesn’t have any
size, it can scale to any dimension. When playing with the image
