Re: [Interest] QML: Image is blurred when rotated

[Shawn Rutledge]

> On 2021 Jul 29, at 19:45, Alexander Dyagilev  wrote:
> 
> Hello,
> 
> I have an SVG image which is drawn fine.
> 
> But if I rotate it (i.e. change its rotation property to some value) it is 
> drawn blurry.

How blurry?

Image.sourceSize is useful when working with SVG, to render at a specific pixel 
resolution.  But that might not be the problem, if you just mean that pixels 
are pixel-grid-aligned to begin with, and then of course they are not anymore 
when it’s rotated.

You can also try Image.antialiasing.  That may make it more blurry in a good 
way (because blur is better than jaggies: AA means fuzzy edges).

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML: Image is blurred when rotated

[Frank Mertens]

On 29.07.21 19:45, Alexander Dyagilev wrote:
> Hello,
>
> I have an SVG image which is drawn fine.
>
> But if I rotate it (i.e. change its rotation property to some value) it is 
> drawn blurry.
>
> Is this a bug or a normal behavior that can't be avoided?
>

Sure. Try myImage.smooth=false. Of course quality depends also on your GFX 
backend.
Check out QQuickWindow::setSceneGraphBackend().

God speed,
Frank

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML Image size vs sourceSize strange things

[Tor Arne Vestbø]

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 
small test case, thanks!)

Cheers,
Tor Arne

On 27 Mar 2021, at 08:57, Alexander Dyagilev 
mailto:alervd...@gmail.com>> wrote:


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 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 for svgs has accelerated the UI 
loading time from seconds to a snap!!!

I have found this because I was not finding acceptable the time it took to 
resize a window.

I had to replace years of pngs into svgs but in the end it payed off.

You should definitely consider moving to svgs.

Best,

--
Nuno Santos

No dia 27/03/2021, às 03:17, Alexander Dyagilev 
 escreveu:



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 
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 size (not the 
source) it will sample the source for each pixel, not sure about the algorithm 
but you might need an higher source resolution to get a proper image without 
artifact. I would at least take the Screen.devicePixelRatio into the source 
size into account and even add a x2 to ensure proper sampling, but I don’t see 
any real advantage to play with the source size unless you really are consuming 
way too much memory.

This might slow you down if the same image is using different sourceSize:

Note: Changing this property dynamically causes the image source to be 
reloaded, potentially even from the network, if it is not in the disk cache.


On Mar 23, 2021, at 3:31 AM, Alexander Dyagilev 
mailto:alervd...@gmail.com>> wrote:


Hello,

We had a strange problem with blurred images under Retina displays. Left part 
of the image - before, right one - after the fix.



Our QML code was using with to show images:

Image {

anchors.verticalCenter: parent.verticalCenter

sourceSize.width: 25

sourceSize.height: 25

source: preview.url

}



I've tried to multiply sourceSize by Screen.devicePixelRatio - images became 
bigger so they did not fit their places.

Then I've replaced sourceSize.width with just width and the same for height. 
And it works fine now.

My questions is:

1) Is it required to multiply sourceSize by devicePixelRatio? Or is it managed 
automatically? It seems that it is managed automatically for PNG and NOT 
managed for SVG.

2) If it is already managed automatically for PNG (these images preview.url are 
PNGs) then why was it blurred? The original PNG image is of size 64x64 pixels 
under Retina displays.

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Jerome Godbout
Software/Firmare Lead Amotus

C: (581) 777-0050
O: (418) 800-1073 ext.: 114
godbo...@amotus.ca




dimonoff.com   |amotus.ca

We have moved!
1015 Avenue Wilfrid-Pelletier, Québec, QC G1W 0C4, 4e étage

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML Image sourceSize bug (?)

[Giuseppe D'Angelo via Interest]

On 27/03/2021 15:46, Alexander Dyagilev wrote:


If I enable mipmap, it looks much better comparing to original variant,
but still worse comparing to the final one (described in my original
posting).

I can provide you all the screenshots if you want to.


I can only entertain that mipmapping in your case is going to use 
trilinear interpolation (*) between the 32x32 and the 16x16 mip. And, 
for your particular image ("artwork" / "icon"), that is giving you worse 
results than a 27x27 image scaled directly from the source via bilinear 
interpolation.


There's not much to do about this:

* mipmapping allows you to keep a good visual quality if the displayed 
size of the image changes
* sourceSize allows you to get a good scaled-down version and save on 
memory, but will look awful if now you try to make the image bigger again


(*) didn't check the actual code, just assumed a GL_LINEAR_MIPMAP_LINEAR 
setting.



HTH,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts



smime.p7s
Description: S/MIME Cryptographic Signature
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML Image sourceSize bug (?)

[Alexander Dyagilev]

First, thank you for your answers :)

If I enable mipmap, it looks much better comparing to original variant, 
but still worse comparing to the final one (described in my original 
posting).


I can provide you all the screenshots if you want to.


On 3/27/2021 4:35 PM, Giuseppe D'Angelo wrote:

On 27/03/2021 11:56, Alexander Dyagilev wrote:

No.

On 3/27/2021 1:24 PM, Giuseppe D'Angelo via Interest wrote:

On 27/03/2021 04:20, Alexander Dyagilev wrote:

Looks better. Why is it so?


Did you enable mipmapping for the first one? 


Well, does it improve it you enable it?

Thanks,


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML Image sourceSize bug (?)

[Giuseppe D'Angelo via Interest]

On 27/03/2021 11:56, Alexander Dyagilev wrote:

No.

On 3/27/2021 1:24 PM, Giuseppe D'Angelo via Interest wrote:

On 27/03/2021 04:20, Alexander Dyagilev wrote:

Looks better. Why is it so?


Did you enable mipmapping for the first one? 


Well, does it improve it you enable it?

Thanks,

--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts



smime.p7s
Description: S/MIME Cryptographic Signature
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML Image sourceSize bug (?)

[Alexander Dyagilev]

No.

On 3/27/2021 1:24 PM, Giuseppe D'Angelo via Interest wrote:

On 27/03/2021 04:20, Alexander Dyagilev wrote:

Looks better. Why is it so?


Did you enable mipmapping for the first one?

Thanks,


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML Image sourceSize bug (?)

[Giuseppe D'Angelo via Interest]

On 27/03/2021 04:20, Alexander Dyagilev wrote:

Looks better. Why is it so?


Did you enable mipmapping for the first one?

Thanks,

--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts



smime.p7s
Description: S/MIME Cryptographic Signature
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML Image size vs sourceSize strange things

[Alexander Dyagilev]

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 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 for svgs has accelerated 
the UI loading time from seconds to a snap!!!


I have found this because I was not finding acceptable the time it 
took to resize a window.


I had to replace years of pngs into svgs but in the end it payed off.

You should definitely consider moving to svgs.

Best,

--
Nuno Santos

No dia 27/03/2021, às 03:17, Alexander Dyagilev  
escreveu:




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 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 size (not the source) it will 
sample the source for each pixel, not sure about the algorithm but 
you might need an higher source resolution to get a proper image 
without artifact. I would at least take the Screen.devicePixelRatio 
into the source size into account and even add a x2 to ensure proper 
sampling, but I don’t see any real advantage to play with the source 
size unless you really are consuming way too much memory.


This might slow you down if the same image is using different 
sourceSize:


Note: /Changing this property dynamically causes the image source to 
be reloaded, potentially even from the network, if it is not in the 
disk cache./

/
/

On Mar 23, 2021, at 3:31 AM, Alexander Dyagilev 
mailto:alervd...@gmail.com>> wrote:


Hello,

We had a strange problem with blurred images under Retina displays. 
Left part of the image - before, right one - after the fix.




Our QML code was using with to show images:

Image{
anchors.verticalCenter:parent.verticalCenter
sourceSize.width:25
sourceSize.height:25
source:preview.url
}

I've tried to multiply sourceSize by Screen.devicePixelRatio - 
images became bigger so they did not fit their places.


Then I've replaced sourceSize.width with just width and the same 
for height. And it works fine now.


My questions is:

1) Is it required to multiply sourceSize by devicePixelRatio? Or is 
it managed automatically? It seems that it is managed automatically 
for PNG and NOT managed for SVG.


2) If it is already managed automatically for PNG (these images 
preview.url are PNGs) then why was it blurred? The original PNG 
image is of size 64x64 pixels under Retina displays.


___
Interest mailing list
Interest@qt-project.org 
https://lists.qt-project.org/listinfo/interest


Jerome Godbout
Software/Firmare Lead Amotus

C: (581) 777-0050
O: (418) 800-1073 ext.: 114
godbo...@amotus.ca 




dimonoff.com   | amotus.ca 

We have moved!
1015 Avenue Wilfrid-Pelletier, Québec, QC G1W 0C4, 4e étage


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML Image size vs sourceSize strange things

[Nuno Santos]

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 for svgs has accelerated the UI 
loading time from seconds to a snap!!! 

I have found this because I was not finding acceptable the time it took to 
resize a window.

I had to replace years of pngs into svgs but in the end it payed off.

You should definitely consider moving to svgs.

Best,

--
Nuno Santos

> No dia 27/03/2021, às 03:17, Alexander Dyagilev  
> escreveu:
> 
> 
> 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 
>> 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 size (not 
>> the source) it will sample the source for each pixel, not sure about the 
>> algorithm but you might need an higher source resolution to get a proper 
>> image without artifact. I would at least take the Screen.devicePixelRatio 
>> into the source size into account and even add a x2 to ensure proper 
>> sampling, but I don’t see any real advantage to play with the source size 
>> unless you really are consuming way too much memory.
>> 
>> This might slow you down if the same image is using different sourceSize:
>> 
>> Note: Changing this property dynamically causes the image source to be 
>> reloaded, potentially even from the network, if it is not in the disk cache.
>> 
>> 
>>> On Mar 23, 2021, at 3:31 AM, Alexander Dyagilev  wrote:
>>> 
>>> Hello,
>>> 
>>> We had a strange problem with blurred images under Retina displays. Left 
>>> part of the image - before, right one - after the fix.
>>> 
>>> 
>>> 
>>> Our QML code was using with to show images:
>>> 
>>> Image {
>>> anchors.verticalCenter: parent.verticalCenter
>>> sourceSize.width: 25
>>> sourceSize.height: 25
>>> source: preview.url
>>> }
>>> 
>>> I've tried to multiply sourceSize by Screen.devicePixelRatio - images 
>>> became bigger so they did not fit their places. 
>>> 
>>> Then I've replaced sourceSize.width with just width and the same for 
>>> height. And it works fine now. 
>>> 
>>> My questions is:
>>> 
>>> 1) Is it required to multiply sourceSize by devicePixelRatio? Or is it 
>>> managed automatically? It seems that it is managed automatically for PNG 
>>> and NOT managed for SVG. 
>>> 
>>> 2) If it is already managed automatically for PNG (these images preview.url 
>>> are PNGs) then why was it blurred? The original PNG image is of size 64x64 
>>> pixels under Retina displays.
>>> 
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> https://lists.qt-project.org/listinfo/interest
>> 
>> Jerome Godbout
>> Software/Firmare Lead Amotus
>> 
>> C: (581) 777-0050 
>> O: (418) 800-1073 ext.: 114   
>> godbo...@amotus.ca
>> 
>> 
>> 
>> 
>> dimonoff.com   |amotus.ca
>>  
>> We have moved!
>> 1015 Avenue Wilfrid-Pelletier, Québec, QC G1W 0C4, 4e étage
>> 
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML Image size vs sourceSize strange things

[Alexander Dyagilev]

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 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 size (not the source) it will sample the source 
for each pixel, not sure about the algorithm but you might need an 
higher source resolution to get a proper image without artifact. I 
would at least take the Screen.devicePixelRatio into the source size 
into account and even add a x2 to ensure proper sampling, but I don’t 
see any real advantage to play with the source size unless you really 
are consuming way too much memory.


This might slow you down if the same image is using different sourceSize:

Note: /Changing this property dynamically causes the image source to 
be reloaded, potentially even from the network, if it is not in the 
disk cache./

/
/

On Mar 23, 2021, at 3:31 AM, Alexander Dyagilev > wrote:


Hello,

We had a strange problem with blurred images under Retina displays. 
Left part of the image - before, right one - after the fix.




Our QML code was using with to show images:

Image{
anchors.verticalCenter:parent.verticalCenter
sourceSize.width:25
sourceSize.height:25
source:preview.url
}

I've tried to multiply sourceSize by Screen.devicePixelRatio - images 
became bigger so they did not fit their places.


Then I've replaced sourceSize.width with just width and the same for 
height. And it works fine now.


My questions is:

1) Is it required to multiply sourceSize by devicePixelRatio? Or is 
it managed automatically? It seems that it is managed automatically 
for PNG and NOT managed for SVG.


2) If it is already managed automatically for PNG (these images 
preview.url are PNGs) then why was it blurred? The original PNG image 
is of size 64x64 pixels under Retina displays.


___
Interest mailing list
Interest@qt-project.org 
https://lists.qt-project.org/listinfo/interest


Jerome Godbout
Software/Firmare Lead Amotus

C: (581) 777-0050
O: (418) 800-1073 ext.: 114
godbo...@amotus.ca 



dimonoff.com   | amotus.ca 

We have moved!
1015 Avenue Wilfrid-Pelletier, Québec, QC G1W 0C4, 4e étage

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML Image size vs sourceSize strange things

[Jérôme Godbout]

Yes good point, take care those built-in size attributes are optional, might 
not be there into an SVG, you might not want to count on it.

From: Interest  on behalf of Giuseppe D'Angelo 
via Interest 
Date: Tuesday, March 23, 2021 at 10:53 AM
To: interest@qt-project.org 
Subject: Re: [Interest] 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 sense, it’s vectoriel,
> doesn’t have any size, it can scale to any dimension.

This isn't accurate. SVG files have a builtin "wanted" size, which is
IIRC what Qt would use by default:

> https://www.w3.org/TR/SVG11/struct.html#SVGElementWidthAttribute

By explictly setting `sourceSize` you're asking Qt to rasterize the SVG
at a different resolution rather than the wanted one (and downscaling
when rendering).


My 2 c,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML Image size vs sourceSize strange things

[Giuseppe D'Angelo via Interest]

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 to any dimension.


This isn't accurate. SVG files have a builtin "wanted" size, which is 
IIRC what Qt would use by default:



https://www.w3.org/TR/SVG11/struct.html#SVGElementWidthAttribute


By explictly setting `sourceSize` you're asking Qt to rasterize the SVG 
at a different resolution rather than the wanted one (and downscaling 
when rendering).



My 2 c,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts



smime.p7s
Description: Firma crittografica S/MIME
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML Image size vs sourceSize strange things

[Jérôme Godbout]

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 size (not the 
source) it will sample the source for each pixel, not sure about the algorithm 
but you might need an higher source resolution to get a proper image without 
artifact. I would at least take the Screen.devicePixelRatio into the source 
size into account and even add a x2 to ensure proper sampling, but I don’t see 
any real advantage to play with the source size unless you really are consuming 
way too much memory.

This might slow you down if the same image is using different sourceSize:

Note: Changing this property dynamically causes the image source to be 
reloaded, potentially even from the network, if it is not in the disk cache.


On Mar 23, 2021, at 3:31 AM, Alexander Dyagilev 
mailto:alervd...@gmail.com>> wrote:


Hello,

We had a strange problem with blurred images under Retina displays. Left part 
of the image - before, right one - after the fix.



Our QML code was using with to show images:

Image {

anchors.verticalCenter: parent.verticalCenter

sourceSize.width: 25

sourceSize.height: 25

source: preview.url

}



I've tried to multiply sourceSize by Screen.devicePixelRatio - images became 
bigger so they did not fit their places.

Then I've replaced sourceSize.width with just width and the same for height. 
And it works fine now.

My questions is:

1) Is it required to multiply sourceSize by devicePixelRatio? Or is it managed 
automatically? It seems that it is managed automatically for PNG and NOT 
managed for SVG.

2) If it is already managed automatically for PNG (these images preview.url are 
PNGs) then why was it blurred? The original PNG image is of size 64x64 pixels 
under Retina displays.

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Jerome Godbout
Software/Firmare Lead Amotus

C: (581) 777-0050
O: (418) 800-1073 ext.: 114
godbo...@amotus.ca

[cid:image007.png@01D70B66.39FB01C0]

dimonoff.com   |amotus.ca

We have moved!
1015 Avenue Wilfrid-Pelletier, Québec, QC G1W 0C4, 4e étage

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML Image

[Jani Tykka]

Source size was already set as the original image size. When mipmap is set
colors seems to be even more distorted.

On Wed, Mar 16, 2016 at 10:45 PM, Jason H  wrote:

> Since you mention gradients, try setting source size or the mipmap
> properties. I wonder if you're getting some subsampling issue.
>
>
> *Sent:* Wednesday, March 16, 2016 at 8:26 AM
> *From:* "Jani Tykka" 
> *To:* "interest@qt-project.org Interest" 
> *Subject:* [Interest] QML Image
> Hi,
>
> I'm using Qt 5.5.1. When quick2 window renders png-image defined in QML
> Image element it seems that colors are not rendered exactly as defined in
> source png-image. This seems to happen on images which have more
> complicated color fills, like gradients. Is there anything that can be done
> to achieve exact presentation from source image? Any explanation what is
> causing the difference?
>
> Thanks,
> Jani
>
>
> This email is intended solely for the person or entity to which it is
> addressed and may contain confidential and/or privileged information. If
> you are not the intended recipient and have received this email in error,
> please notify BroadSoft, Inc. immediately by replying to this message, and
> destroy all copies of this message, along with any attachment, prior to
> reading, distributing or copying it.
> ___ Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>



-- 
*Jani Tykkä*
Development Manager | BroadSoft, Inc. | +358 44 596 0587 |
jty...@broadsoft.com

-- 


This email is intended solely for the person or entity to which it is 
addressed and may contain confidential and/or privileged information. If 
you are not the intended recipient and have received this email in error, 
please notify BroadSoft, Inc. immediately by replying to this message, and 
destroy all copies of this message, along with any attachment, prior to 
reading, distributing or copying it.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QML Image

[Jani Tykka]

Attached original image + comparison.

On Thu, Mar 17, 2016 at 4:28 PM, Jason H <jh...@gmx.com> wrote:

> A picture would help
>
> *Sent:* Thursday, March 17, 2016 at 1:15 AM
> *From:* "Jani Tykka" <jty...@broadsoft.com>
> *To:* "Jason H" <jh...@gmx.com>
> *Cc:* "interest@qt-project.org Interest" <interest@qt-project.org>
> *Subject:* Re: [Interest] QML Image
> Source size was already set as the original image size. When mipmap is set
> colors seems to be even more distorted.
>
> On Wed, Mar 16, 2016 at 10:45 PM, Jason H <jh...@gmx.com> wrote:
>>
>> Since you mention gradients, try setting source size or the mipmap
>> properties. I wonder if you're getting some subsampling issue.
>>
>>
>> *Sent:* Wednesday, March 16, 2016 at 8:26 AM
>> *From:* "Jani Tykka" <jty...@broadsoft.com>
>> *To:* "interest@qt-project.org Interest" <interest@qt-project.org>
>> *Subject:* [Interest] QML Image
>> Hi,
>>
>> I'm using Qt 5.5.1. When quick2 window renders png-image defined in QML
>> Image element it seems that colors are not rendered exactly as defined in
>> source png-image. This seems to happen on images which have more
>> complicated color fills, like gradients. Is there anything that can be done
>> to achieve exact presentation from source image? Any explanation what is
>> causing the difference?
>>
>> Thanks,
>> Jani
>>
>> This email is intended solely for the person or entity to which it is
>> addressed and may contain confidential and/or privileged information. If
>> you are not the intended recipient and have received this email in error,
>> please notify BroadSoft, Inc. immediately by replying to this message, and
>> destroy all copies of this message, along with any attachment, prior to
>> reading, distributing or copying it.
>> ___ Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>>
>
>
> --
> *Jani Tykkä*
> Development Manager | BroadSoft, Inc. | +358 44 596 0587 |
> jty...@broadsoft.com
>
>
> This email is intended solely for the person or entity to which it is
> addressed and may contain confidential and/or privileged information. If
> you are not the intended recipient and have received this email in error,
> please notify BroadSoft, Inc. immediately by replying to this message, and
> destroy all copies of this message, along with any attachment, prior to
> reading, distributing or copying it.
>



-- 
*Jani Tykkä*
Development Manager | BroadSoft, Inc. | +358 44 596 0587 |
jty...@broadsoft.com

-- 


This email is intended solely for the person or entity to which it is 
addressed and may contain confidential and/or privileged information. If 
you are not the intended recipient and have received this email in error, 
please notify BroadSoft, Inc. immediately by replying to this message, and 
destroy all copies of this message, along with any attachment, prior to 
reading, distributing or copying it.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QML Image

[Jason H]

A picture would help
 

Sent: Thursday, March 17, 2016 at 1:15 AM
From: "Jani Tykka" <jty...@broadsoft.com>
To: "Jason H" <jh...@gmx.com>
Cc: "interest@qt-project.org Interest" <interest@qt-project.org>
Subject: Re: [Interest] QML Image


Source size was already set as the original image size. When mipmap is set colors seems to be even more distorted.

 
On Wed, Mar 16, 2016 at 10:45 PM, Jason H <jh...@gmx.com> wrote:





Since you mention gradients, try setting source size or the mipmap properties. I wonder if you're getting some subsampling issue.

 

 

Sent: Wednesday, March 16, 2016 at 8:26 AM
From: "Jani Tykka" <jty...@broadsoft.com>
To: "interest@qt-project.org Interest" <interest@qt-project.org>
Subject: [Interest] QML Image





Hi,

 
I'm using Qt 5.5.1. When quick2 window renders png-image defined in QML Image element it seems that colors are not rendered exactly as defined in source png-image. This seems to happen on images which have more complicated color fills, like gradients. Is there anything that can be done to achieve exact presentation from source image? Any explanation what is causing the difference?

 

Thanks,

Jani 






 

This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it.
___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest







 

 
--


Jani Tykkä 
Development Manager | BroadSoft, Inc. | +358 44 596 0587 | jty...@broadsoft.com


 



 

This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it.




___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QML Image

[Jason H]

Since you mention gradients, try setting source size or the mipmap properties. I wonder if you're getting some subsampling issue.

 

 

Sent: Wednesday, March 16, 2016 at 8:26 AM
From: "Jani Tykka" 
To: "interest@qt-project.org Interest" 
Subject: [Interest] QML Image



Hi,

 
I'm using Qt 5.5.1. When quick2 window renders png-image defined in QML Image element it seems that colors are not rendered exactly as defined in source png-image. This seems to happen on images which have more complicated color fills, like gradients. Is there anything that can be done to achieve exact presentation from source image? Any explanation what is causing the difference?

 

Thanks,

Jani 

 



 

This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it.
___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest



___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QML Image asyncronous property

[Mark Gaiser]

On Thu, Dec 4, 2014 at 4:27 PM, Harri Pasanen ha...@mpaja.com wrote:
 I'm playing with a GridView where the delegate contains an Image element
 with asyncronous: true property.


 As a result, when my QML file loads, I see a bunch of messages like:


 QObject::startTimer: Timers cannot be started from another thread


 going by in Application Output pane.


 This is with Qt 5.4.0 RC.


 Seems like there some race condition or missing locking going on.

 Now the messages themselves I don't mind, but at the same time
 I'm seeing strange behavior from StackView. I'm not sure at this point
 if the problems are related.


 Does this ring a bell for anyone?


 Harri

Could you file a bug report for that?
It sounds like a bug to me.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QML Image asyncronous property

[Harri Pasanen]

On 05/12/2014 10:58, Mark Gaiser wrote:
 On Thu, Dec 4, 2014 at 4:27 PM, Harri Pasanen ha...@mpaja.com wrote:
 I'm playing with a GridView where the delegate contains an Image element
 with asyncronous: true property.


 As a result, when my QML file loads, I see a bunch of messages like:


 QObject::startTimer: Timers cannot be started from another thread


 going by in Application Output pane.


 This is with Qt 5.4.0 RC.


 Seems like there some race condition or missing locking going on.

 Now the messages themselves I don't mind, but at the same time
 I'm seeing strange behavior from StackView. I'm not sure at this point
 if the problems are related.


 Does this ring a bell for anyone?


 Harri
 Could you file a bug report for that?
 It sounds like a bug to me.

The  message
QObject::startTimer: Timers cannot be started from another thread
seems to be a valid issue, and easy to reproduce.
I'll submit a bug report.

StackView issue I mentioned was unrelated, my own bug.   I was 
accidentally replacing a stack item while a pop transition was 
running.   That caused some obscure error messages from inside the 
StackView.

Harri
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QML Image memory use

[Robin Burchell]

On Wed, May 2, 2012 at 12:53 PM, Harri Pasanen ha...@mpaja.com wrote:
 Does the scaling happen at display time, or at load time?

You probably want to read the documentation for Image::sourceSize.

Image::size is applied after the image has been loaded.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest