Re: [Interest] Qt/Mac : what about a (the) Window menu?

[Mitch Curtis]

> -Original Message-
> From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org]
> On Behalf Of Nikos Chantziaras
> Sent: Wednesday, 7 March 2018 2:53 AM
> To: interest@qt-project.org
> Subject: Re: [Interest] Qt/Mac : what about a (the) Window menu?
> 
> On 07/03/18 01:52, René J. V. Bertin wrote:
> > Nikos Chantziaras wrote:
> >> Shows up fine here. Unless I'm misunderstanding something.
> >
> > Indeed, the Assistant and QtCreator have the menu. But take a random
> > 3rd party Qt application (say, QupZilla, or Otter Browser) or just
> > about any KF5 application and it will likely not be so lucky.
> >
> > Qt Assistant rolls its own Window menu (and I guess so does Creator).
> >
> > So let me rephrase: why do only some Qt applications show that menu?
> 
> It might be a QML issue. In Widgets, when using QMainWindow, you get an
> application menu by default. In QML with Qt Quick Controls, it seems this got
> only added in Qt 5.10:
> 
>https://doc.qt.io/qt-5.10/qml-qtquick-controls2-menubar.html

That's a non-native menu bar; this one is native and has been around since 5.8:

https://doc.qt.io/qt-5.10/qml-qt-labs-platform-menubar.html

Coincidentally, I'm happily using it in a Qt Quick desktop application:

http://blog.qt.io/blog/2018/03/06/slate-basic-pixel-art-editor-built-qt-quick/

> In other words, don't use QML for desktop applications if you can avoid it :-/

Nitpick: Qt Quick*

> ___
> 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] Qt/Mac : what about a (the) Window menu?

[Nikos Chantziaras]

On 07/03/18 01:52, René J. V. Bertin wrote:

Nikos Chantziaras wrote:

Shows up fine here. Unless I'm misunderstanding something.


Indeed, the Assistant and QtCreator have the menu. But take a random 3rd party
Qt application (say, QupZilla, or Otter Browser) or just about any KF5
application and it will likely not be so lucky.

Qt Assistant rolls its own Window menu (and I guess so does Creator).

So let me rephrase: why do only some Qt applications show that menu?


It might be a QML issue. In Widgets, when using QMainWindow, you get an 
application menu by default. In QML with Qt Quick Controls, it seems 
this got only added in Qt 5.10:


  https://doc.qt.io/qt-5.10/qml-qtquick-controls2-menubar.html

In other words, don't use QML for desktop applications if you can avoid 
it :-/


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

Re: [Interest] How to render small Images decently on non retina displays with QtQuick?

[Nuno Santos]

Worked like charm! 

Thanks for your prompt reply.

Best!

Nuno

> On 6 Mar 2018, at 23:35, Giuseppe D'Angelo  wrote:
> 
> Il 07/03/2018 00:16, Nuno Santos ha scritto:
>> Does anyone knows which modules we need to have compiled in order to make 
>> svg support work?
>> I depend on a static build of Qt and while I was able to use SVG with the 
>> prebuilt Qt, I couldn’t make use of it using my static build.
>> I realised I was missing qtsvg module but even after including it in the 
>> build it still says "unsupported graphic format”
>> Any ideas?
> 
> You need
> 
> QTPLUGIN += qsvg
> 
> in your .pro. See
> 
>> https://doc.qt.io/qt-5/plugins-howto.html#static-plugins
> 
> 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
> 
> ___
> 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] Qt/Mac : what about a (the) Window menu?

[Hamish Moffatt]

On 07/03/18 10:52, René J. V. Bertin wrote:

Nikos Chantziaras wrote:



Shows up fine here. Unless I'm misunderstanding something.

Indeed, the Assistant and QtCreator have the menu. But take a random 3rd party
Qt application (say, QupZilla, or Otter Browser) or just about any KF5
application and it will likely not be so lucky.

Qt Assistant rolls its own Window menu (and I guess so does Creator).

So let me rephrase: why do only some Qt applications show that menu?


It looks like the standard Windows menu to me in Assistant (Qt 5.8)? We 
get the standard menu in our application too, which is exactly what we want.



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

Re: [Interest] Qt/Mac : what about a (the) Window menu?

[René J . V . Bertin]

Nikos Chantziaras wrote:


> Shows up fine here. Unless I'm misunderstanding something.

Indeed, the Assistant and QtCreator have the menu. But take a random 3rd party 
Qt application (say, QupZilla, or Otter Browser) or just about any KF5 
application and it will likely not be so lucky.

Qt Assistant rolls its own Window menu (and I guess so does Creator).

So let me rephrase: why do only some Qt applications show that menu?

R.

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

Re: [Interest] How to render small Images decently on non retina displays with QtQuick?

[Giuseppe D'Angelo]

Il 07/03/2018 00:16, Nuno Santos ha scritto:
Does anyone knows which modules we need to have compiled in order to 
make svg support work?


I depend on a static build of Qt and while I was able to use SVG with 
the prebuilt Qt, I couldn’t make use of it using my static build.


I realised I was missing qtsvg module but even after including it in the 
build it still says "unsupported graphic format”


Any ideas?


You need

QTPLUGIN += qsvg

in your .pro. See


https://doc.qt.io/qt-5/plugins-howto.html#static-plugins


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: Firma crittografica S/MIME
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How to render small Images decently on non retina displays with QtQuick?

[Nuno Santos]

Does anyone knows which modules we need to have compiled in order to make svg 
support work?

I depend on a static build of Qt and while I was able to use SVG with the 
prebuilt Qt, I couldn’t make use of it using my static build.

I realised I was missing qtsvg module but even after including it in the build 
it still says "unsupported graphic format”

Any ideas?

Thx!

Regards,

Nuno

> On 6 Mar 2018, at 16:55, Nuno Santos  wrote:
> 
> Xavier,
> 
> SVG did the trick 
> 
> I just had to add it to resources and pass it to the image element. 
> 
> Looking great now!! :)
> 
> Thank you all for your help
> 
> Best,
> 
> Nuno
> 
> 
> 
>> On 6 Mar 2018, at 16:50, Xavier Bigand > > wrote:
>> 
>> I think that you just have to link the svg module, if I remember correctly, 
>> then in QML just use it as source of an Image item.
>> The only think is that you have to fix the size of the item as the 
>> sourceSize have no sense here.
>> 
>> 2018-03-06 17:47 GMT+01:00 Nuno Santos > >:
>> I have never used SVG in QtQuick. 
>> 
>> What can be used to render SVG’s in QtQuick?
>> 
>>> On 6 Mar 2018, at 16:45, Xavier Bigand >> > wrote:
>>> 
>>> Hi,
>>> 
>>> If your sample picture is relevant I can suggest you to convert it as SVG 
>>> (vectoring it) or using distance field technique.
>>> 
>>> 2018-03-06 17:06 GMT+01:00 Jason H mailto:jh...@gmx.com>>:
>>> Maybe this has something to do with with mipMapping/smooth? It looks like 
>>> it's not anti-aliasing?
>>>  
>>> Sent: Tuesday, March 06, 2018 at 10:50 AM
>>> From: "Nuno Santos" >> >
>>> To: "Mitch Curtis" mailto:mitch.cur...@qt.io>>
>>> Cc: "Qt Project MailingList" >> >
>>> Subject: Re: [Interest] How to render small Images decently on non retina 
>>> displays with QtQuick?
>>> Mitch,
>>>  
>>> Thanks for your reply. 
>>>  
>>> You are right. I’m not playing all the cards…
>>>  
>>> Original image attached (it is white over transparent so you will not see 
>>> it in the email body. The file is called isotope.png) 
>>>  
>>> The item who renders this is the following:
>>>  
>>> import QtQuick 2.4
>>>  
>>> Item {
>>> id: root
>>> implicitWidth: 100
>>> implicitHeight: 100
>>>  
>>> property real padding: 0
>>> property alias imageSource: icon.source
>>> property color imageColor: controller.settings.foregroundColor
>>>  
>>> Image {
>>> id: icon
>>> anchors.fill: parent
>>> anchors.margins: root.padding
>>> fillMode: Image.PreserveAspectFit
>>> }
>>>  
>>> ColorOverlay {
>>> id: overlay
>>> source: icon
>>> anchors.fill: icon
>>> color: root.imageColor
>>> }
>>> }
>>>  
>>>  
>>> 
>>>  
>>> 
>>>  
>>> On 6 Mar 2018, at 15:41, Mitch Curtis >> > wrote:
>>>  
>>> Can you elaborate on “really bad”, and also share a screenshot?
>>>  
>>> From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org 
>>> ] On Behalf Of 
>>> Nuno Santos
>>> Sent: Tuesday, 6 March 2018 4:27 PM
>>> To: Qt Project MailingList >> >
>>> Subject: [Interest] How to render small Images decently on non retina 
>>> displays with QtQuick?
>>>  
>>> Hi,
>>>  
>>> I have a simple question. 
>>>  
>>> How to render small Images decently on non retina displays with QtQuick?
>>>  
>>> In my apps, I use images for icons and logos. They are all big enough to be 
>>> displayed correctly. 
>>>  
>>> However, on non Retina displays they get really bad! And on retine display 
>>> they appear perfectly. 
>>>  
>>> What is the rule of thumb to use QtQuick Image element on on retina 
>>> displays?
>>>  
>>> Thx!
>>>  
>>> Regards,
>>>  
>>> Nuno
>>> ___ 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 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Xavier
>> 
>> 
>> 
>> 
>> -- 
>> Xavier
> 
> ___
> 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] Qt/Mac : what about a (the) Window menu?

[Nikos Chantziaras]

On 06/03/18 22:31, René J.V. Bertin wrote:

I've wondered before and the question came up in a discussion: why do Qt 
applications not show the window menu that native applications usually have? 
Design decision or is there a technical reason?


Shows up fine here. Unless I'm misunderstanding something.

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

[Interest] Qt/Mac : what about a (the) Window menu?

[René J . V . Bertin]

Hi,

I've wondered before and the question came up in a discussion: why do Qt 
applications not show the window menu that native applications usually have? 
Design decision or is there a technical reason?

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

Re: [Interest] Slot exception being thrown on exit

[Thiago Macieira]

On Tuesday, 6 March 2018 09:30:21 PST Ramakanth Kesireddy wrote:
> Please let me know if there is any way to find out the slot or eventhandler
> throwing exception
> other than running the app in debug mode with backtrace?

Run in the debugger and ask it to stop in any C++ exception thrown (gdb 
command "catch throw").

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center



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

Re: [Interest] Slot exception being thrown on exit

[Jason H]

1. reimplement QApplication::notify() and catch all exceptions there

2. Set a break point  there., examine call stack

 

Sent: Tuesday, March 06, 2018 at 12:30 PM
From: "Ramakanth Kesireddy" 
To: interest@qt-project.org
Subject: [Interest] Slot exception being thrown on exit


Hi,
 

When Qt application is being exited, it throws below error:-

 


Qt has caught an exception thrown from an event handler. Throwing

exceptions from an event handler is not supported in Qt. You must

reimplement QApplication::notify() and catch all exceptions there.


 

Please let me know if there is any way to find out the slot or eventhandler throwing exception

other than running the app in debug mode with backtrace?

 

Thanks and Regards,

RK

___ 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

[Interest] KDE's qqc2-desktop-style

[Jason H]

https://api.kde.org/frameworks/qqc2-desktop-style/html/index.html
So this combines QStyle with QML, so QML can be more widget like. Can this be a 
part of Qt?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Slot exception being thrown on exit

[Ramakanth Kesireddy]

Hi,

When Qt application is being exited, it throws below error:-

Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

Please let me know if there is any way to find out the slot or eventhandler
throwing exception
other than running the app in debug mode with backtrace?

Thanks and Regards,
RK
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How to render small Images decently on non retina displays with QtQuick?

[Nuno Santos]

Xavier,

SVG did the trick 

I just had to add it to resources and pass it to the image element. 

Looking great now!! :)

Thank you all for your help

Best,

Nuno



> On 6 Mar 2018, at 16:50, Xavier Bigand  wrote:
> 
> I think that you just have to link the svg module, if I remember correctly, 
> then in QML just use it as source of an Image item.
> The only think is that you have to fix the size of the item as the sourceSize 
> have no sense here.
> 
> 2018-03-06 17:47 GMT+01:00 Nuno Santos  >:
> I have never used SVG in QtQuick. 
> 
> What can be used to render SVG’s in QtQuick?
> 
>> On 6 Mar 2018, at 16:45, Xavier Bigand > > wrote:
>> 
>> Hi,
>> 
>> If your sample picture is relevant I can suggest you to convert it as SVG 
>> (vectoring it) or using distance field technique.
>> 
>> 2018-03-06 17:06 GMT+01:00 Jason H mailto:jh...@gmx.com>>:
>> Maybe this has something to do with with mipMapping/smooth? It looks like 
>> it's not anti-aliasing?
>>  
>> Sent: Tuesday, March 06, 2018 at 10:50 AM
>> From: "Nuno Santos" > >
>> To: "Mitch Curtis" mailto:mitch.cur...@qt.io>>
>> Cc: "Qt Project MailingList" > >
>> Subject: Re: [Interest] How to render small Images decently on non retina 
>> displays with QtQuick?
>> Mitch,
>>  
>> Thanks for your reply. 
>>  
>> You are right. I’m not playing all the cards…
>>  
>> Original image attached (it is white over transparent so you will not see it 
>> in the email body. The file is called isotope.png) 
>>  
>> The item who renders this is the following:
>>  
>> import QtQuick 2.4
>>  
>> Item {
>> id: root
>> implicitWidth: 100
>> implicitHeight: 100
>>  
>> property real padding: 0
>> property alias imageSource: icon.source
>> property color imageColor: controller.settings.foregroundColor
>>  
>> Image {
>> id: icon
>> anchors.fill: parent
>> anchors.margins: root.padding
>> fillMode: Image.PreserveAspectFit
>> }
>>  
>> ColorOverlay {
>> id: overlay
>> source: icon
>> anchors.fill: icon
>> color: root.imageColor
>> }
>> }
>>  
>>  
>> 
>>  
>> 
>>  
>> On 6 Mar 2018, at 15:41, Mitch Curtis > > wrote:
>>  
>> Can you elaborate on “really bad”, and also share a screenshot?
>>  
>> From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org 
>> ] On Behalf Of 
>> Nuno Santos
>> Sent: Tuesday, 6 March 2018 4:27 PM
>> To: Qt Project MailingList > >
>> Subject: [Interest] How to render small Images decently on non retina 
>> displays with QtQuick?
>>  
>> Hi,
>>  
>> I have a simple question. 
>>  
>> How to render small Images decently on non retina displays with QtQuick?
>>  
>> In my apps, I use images for icons and logos. They are all big enough to be 
>> displayed correctly. 
>>  
>> However, on non Retina displays they get really bad! And on retine display 
>> they appear perfectly. 
>>  
>> What is the rule of thumb to use QtQuick Image element on on retina displays?
>>  
>> Thx!
>>  
>> Regards,
>>  
>> Nuno
>> ___ 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 
>> 
>> 
>> 
>> 
>> 
>> -- 
>> Xavier
> 
> 
> 
> 
> -- 
> Xavier

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

Re: [Interest] How to render small Images decently on non retina displays with QtQuick?

[Xavier Bigand]

The anti-aliasing only works on edges except for the Super Sampling AA.

2018-03-06 17:49 GMT+01:00 Nuno Santos :

> Allan,
>
> I have tried to enable antialiasing to true but it didn’t made any
> difference
>
> :(
>
> > On 6 Mar 2018, at 16:47, Allan Sandfeld Jensen  wrote:
> >
> > On Dienstag, 6. März 2018 17:44:19 CET Allan Sandfeld Jensen wrote:
> >> On Dienstag, 6. März 2018 16:50:23 CET Nuno Santos wrote:
> >>> Mitch,
> >>>
> >>> Thanks for your reply.
> >>>
> >>> You are right. I’m not playing all the cards…
> >>>
> >>> Original image attached (it is white over transparent so you will not
> see
> >>> it in the email body. The file is called isotope.png)
> >>
> >> Looks like you dont have antialiasing enabled. It is a good idea in
> general.
> >> Just add the line "antialiasing : false" to the rendered item.
> >>
> > I meant 'antialiasing: true' of course. Looks like it is indeed  off by
> > default http://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph-
> renderer.html#antialiasing and that will result in terrible scaled images.
> >
> > 'Allan
> >
> >
> > ___
> > 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
>



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

Re: [Interest] How to render small Images decently on non retina displays with QtQuick?

[Xavier Bigand]

I think that you just have to link the svg module, if I remember correctly,
then in QML just use it as source of an Image item.
The only think is that you have to fix the size of the item as the
sourceSize have no sense here.

2018-03-06 17:47 GMT+01:00 Nuno Santos :

> I have never used SVG in QtQuick.
>
> What can be used to render SVG’s in QtQuick?
>
> On 6 Mar 2018, at 16:45, Xavier Bigand  wrote:
>
> Hi,
>
> If your sample picture is relevant I can suggest you to convert it as SVG
> (vectoring it) or using distance field technique.
>
> 2018-03-06 17:06 GMT+01:00 Jason H :
>
>> Maybe this has something to do with with mipMapping/smooth? It looks like
>> it's not anti-aliasing?
>>
>> *Sent:* Tuesday, March 06, 2018 at 10:50 AM
>> *From:* "Nuno Santos" 
>> *To:* "Mitch Curtis" 
>> *Cc:* "Qt Project MailingList" 
>> *Subject:* Re: [Interest] How to render small Images decently on non
>> retina displays with QtQuick?
>> Mitch,
>>
>> Thanks for your reply.
>>
>> You are right. I’m not playing all the cards…
>>
>> Original image attached (it is white over transparent so you will not see
>> it in the email body. The file is called isotope.png)
>>
>> The item who renders this is the following:
>>
>> import QtQuick 2.4
>>
>> Item {
>> id: root
>> implicitWidth: 100
>> implicitHeight: 100
>>
>> property real padding: 0
>> property alias imageSource: icon.source
>> property color imageColor: controller.settings.foregroundColor
>>
>> Image {
>> id: icon
>> anchors.fill: parent
>> anchors.margins: root.padding
>> fillMode: Image.PreserveAspectFit
>> }
>>
>> ColorOverlay {
>> id: overlay
>> source: icon
>> anchors.fill: icon
>> color: root.imageColor
>> }
>> }
>>
>>
>> 
>>
>> 
>>
>>
>> On 6 Mar 2018, at 15:41, Mitch Curtis  wrote:
>>
>> Can you elaborate on “really bad”, and also share a screenshot?
>>
>> *From:* Interest [mailto:interest-bounces+mitch
>> .curtis=qt...@qt-project.org
>> ] *On Behalf Of *Nuno
>> Santos
>> *Sent:* Tuesday, 6 March 2018 4:27 PM
>> *To:* Qt Project MailingList 
>> *Subject:* [Interest] How to render small Images decently on non retina
>> displays with QtQuick?
>>
>> Hi,
>>
>> I have a simple question.
>>
>> *How to render small Images decently on non retina displays with QtQuick?*
>>
>> In my apps, I use images for icons and logos. They are all big enough to
>> be displayed correctly.
>>
>> However, on non Retina displays they get really bad! And on retine
>> display they appear perfectly.
>>
>> What is the rule of thumb to use QtQuick Image element on on retina
>> displays?
>>
>> Thx!
>>
>> Regards,
>>
>> Nuno
>>
>> ___ Interest mailing list
>> Interest@qt-project.org http://lists.qt-project.org/ma
>> ilman/listinfo/interest
>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>>
>>
>
>
> --
> Xavier
>
>
>


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

Re: [Interest] How to render small Images decently on non retina displays with QtQuick?

[Nuno Santos]

Allan,

I have tried to enable antialiasing to true but it didn’t made any difference

:(

> On 6 Mar 2018, at 16:47, Allan Sandfeld Jensen  wrote:
> 
> On Dienstag, 6. März 2018 17:44:19 CET Allan Sandfeld Jensen wrote:
>> On Dienstag, 6. März 2018 16:50:23 CET Nuno Santos wrote:
>>> Mitch,
>>> 
>>> Thanks for your reply.
>>> 
>>> You are right. I’m not playing all the cards…
>>> 
>>> Original image attached (it is white over transparent so you will not see
>>> it in the email body. The file is called isotope.png)
>> 
>> Looks like you dont have antialiasing enabled. It is a good idea in general.
>> Just add the line "antialiasing : false" to the rendered item.
>> 
> I meant 'antialiasing: true' of course. Looks like it is indeed  off by 
> default 
> http://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph-renderer.html#antialiasing
>  and that will result in terrible scaled images.
> 
> 'Allan
> 
> 
> ___
> 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] How to render small Images decently on non retina displays with QtQuick?

[Nuno Santos]

I have never used SVG in QtQuick. 

What can be used to render SVG’s in QtQuick?

> On 6 Mar 2018, at 16:45, Xavier Bigand  wrote:
> 
> Hi,
> 
> If your sample picture is relevant I can suggest you to convert it as SVG 
> (vectoring it) or using distance field technique.
> 
> 2018-03-06 17:06 GMT+01:00 Jason H mailto:jh...@gmx.com>>:
> Maybe this has something to do with with mipMapping/smooth? It looks like 
> it's not anti-aliasing?
>  
> Sent: Tuesday, March 06, 2018 at 10:50 AM
> From: "Nuno Santos"  >
> To: "Mitch Curtis" mailto:mitch.cur...@qt.io>>
> Cc: "Qt Project MailingList"  >
> Subject: Re: [Interest] How to render small Images decently on non retina 
> displays with QtQuick?
> Mitch,
>  
> Thanks for your reply. 
>  
> You are right. I’m not playing all the cards…
>  
> Original image attached (it is white over transparent so you will not see it 
> in the email body. The file is called isotope.png) 
>  
> The item who renders this is the following:
>  
> import QtQuick 2.4
>  
> Item {
> id: root
> implicitWidth: 100
> implicitHeight: 100
>  
> property real padding: 0
> property alias imageSource: icon.source
> property color imageColor: controller.settings.foregroundColor
>  
> Image {
> id: icon
> anchors.fill: parent
> anchors.margins: root.padding
> fillMode: Image.PreserveAspectFit
> }
>  
> ColorOverlay {
> id: overlay
> source: icon
> anchors.fill: icon
> color: root.imageColor
> }
> }
>  
>  
> 
>  
> 
>  
> On 6 Mar 2018, at 15:41, Mitch Curtis  > wrote:
>  
> Can you elaborate on “really bad”, and also share a screenshot?
>  
> From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org 
> ] On Behalf Of 
> Nuno Santos
> Sent: Tuesday, 6 March 2018 4:27 PM
> To: Qt Project MailingList  >
> Subject: [Interest] How to render small Images decently on non retina 
> displays with QtQuick?
>  
> Hi,
>  
> I have a simple question. 
>  
> How to render small Images decently on non retina displays with QtQuick?
>  
> In my apps, I use images for icons and logos. They are all big enough to be 
> displayed correctly. 
>  
> However, on non Retina displays they get really bad! And on retine display 
> they appear perfectly. 
>  
> What is the rule of thumb to use QtQuick Image element on on retina displays?
>  
> Thx!
>  
> Regards,
>  
> Nuno
> ___ 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 
> 
> 
> 
> 
> 
> -- 
> Xavier

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

Re: [Interest] How to render small Images decently on non retina displays with QtQuick?

[Allan Sandfeld Jensen]

On Dienstag, 6. März 2018 17:44:19 CET Allan Sandfeld Jensen wrote:
> On Dienstag, 6. März 2018 16:50:23 CET Nuno Santos wrote:
> > Mitch,
> > 
> > Thanks for your reply.
> > 
> > You are right. I’m not playing all the cards…
> > 
> > Original image attached (it is white over transparent so you will not see
> > it in the email body. The file is called isotope.png)
> 
> Looks like you dont have antialiasing enabled. It is a good idea in general.
> Just add the line "antialiasing : false" to the rendered item.
> 
I meant 'antialiasing: true' of course. Looks like it is indeed  off by 
default 
http://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph-renderer.html#antialiasing
 and that will result in terrible scaled images.

'Allan


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

Re: [Interest] How to render small Images decently on non retina displays with QtQuick?

[Xavier Bigand]

Hi,

If your sample picture is relevant I can suggest you to convert it as SVG
(vectoring it) or using distance field technique.

2018-03-06 17:06 GMT+01:00 Jason H :

> Maybe this has something to do with with mipMapping/smooth? It looks like
> it's not anti-aliasing?
>
> *Sent:* Tuesday, March 06, 2018 at 10:50 AM
> *From:* "Nuno Santos" 
> *To:* "Mitch Curtis" 
> *Cc:* "Qt Project MailingList" 
> *Subject:* Re: [Interest] How to render small Images decently on non
> retina displays with QtQuick?
> Mitch,
>
> Thanks for your reply.
>
> You are right. I’m not playing all the cards…
>
> Original image attached (it is white over transparent so you will not see
> it in the email body. The file is called isotope.png)
>
> The item who renders this is the following:
>
> import QtQuick 2.4
>
> Item {
> id: root
> implicitWidth: 100
> implicitHeight: 100
>
> property real padding: 0
> property alias imageSource: icon.source
> property color imageColor: controller.settings.foregroundColor
>
> Image {
> id: icon
> anchors.fill: parent
> anchors.margins: root.padding
> fillMode: Image.PreserveAspectFit
> }
>
> ColorOverlay {
> id: overlay
> source: icon
> anchors.fill: icon
> color: root.imageColor
> }
> }
>
>
>
>
>
> On 6 Mar 2018, at 15:41, Mitch Curtis  wrote:
>
> Can you elaborate on “really bad”, and also share a screenshot?
>
> *From:* Interest [mailto:interest-bounces+mitch.curtis=qt.io@qt-project.
> org ] *On Behalf Of *Nuno
> Santos
> *Sent:* Tuesday, 6 March 2018 4:27 PM
> *To:* Qt Project MailingList 
> *Subject:* [Interest] How to render small Images decently on non retina
> displays with QtQuick?
>
> Hi,
>
> I have a simple question.
>
> *How to render small Images decently on non retina displays with QtQuick?*
>
> In my apps, I use images for icons and logos. They are all big enough to
> be displayed correctly.
>
> However, on non Retina displays they get really bad! And on retine display
> they appear perfectly.
>
> What is the rule of thumb to use QtQuick Image element on on retina
> displays?
>
> Thx!
>
> Regards,
>
> Nuno
>
> ___ 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
>
>


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

Re: [Interest] How to render small Images decently on non retina displays with QtQuick?

[Allan Sandfeld Jensen]

On Dienstag, 6. März 2018 16:50:23 CET Nuno Santos wrote:
> Mitch,
> 
> Thanks for your reply.
> 
> You are right. I’m not playing all the cards…
> 
> Original image attached (it is white over transparent so you will not see it
> in the email body. The file is called isotope.png)
> 
Looks like you dont have antialiasing enabled. It is a good idea in general. 
Just add the line "antialiasing : false" to the rendered item.

'Allan


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

Re: [Interest] How to render small Images decently on non retina displays with QtQuick?

[Jason H]

Maybe this has something to do with with mipMapping/smooth? It looks like it's not anti-aliasing?

 



Sent: Tuesday, March 06, 2018 at 10:50 AM
From: "Nuno Santos" 
To: "Mitch Curtis" 
Cc: "Qt Project MailingList" 
Subject: Re: [Interest] How to render small Images decently on non retina displays with QtQuick?


Mitch,
 

Thanks for your reply. 

 

You are right. I’m not playing all the cards…

 

Original image attached (it is white over transparent so you will not see it in the email body. The file is called isotope.png) 

 

The item who renders this is the following:

 


import QtQuick 2.4

 

Item {

    id: root

    implicitWidth: 100

    implicitHeight: 100

 

    property real padding: 0

    property alias imageSource: icon.source

    property color imageColor: controller.settings.foregroundColor

 

    Image {

        id: icon

        anchors.fill: parent

        anchors.margins: root.padding

        fillMode: Image.PreserveAspectFit

    }

 

    ColorOverlay {

        id: overlay

        source: icon

        anchors.fill: icon

        color: root.imageColor

    }

}


 

 



 


 

On 6 Mar 2018, at 15:41, Mitch Curtis  wrote:
 



Can you elaborate on “really bad”, and also share a screenshot?

 




From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org] On Behalf Of Nuno Santos
Sent: Tuesday, 6 March 2018 4:27 PM
To: Qt Project MailingList 
Subject: [Interest] How to render small Images decently on non retina displays with QtQuick?



 

Hi,


 



I have a simple question. 



 



How to render small Images decently on non retina displays with QtQuick?



 



In my apps, I use images for icons and logos. They are all big enough to be displayed correctly. 



 



However, on non Retina displays they get really bad! And on retine display they appear perfectly. 



 



What is the rule of thumb to use QtQuick Image element on on retina displays?



 



Thx!



 



Regards,



 



Nuno







___ 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] How to render small Images decently on non retina displays with QtQuick?

[Nuno Santos]

Mitch,

Thanks for your reply. 

You are right. I’m not playing all the cards…

Original image attached (it is white over transparent so you will not see it in 
the email body. The file is called isotope.png) 

The item who renders this is the following:

import QtQuick 2.4

Item {
id: root
implicitWidth: 100
implicitHeight: 100

property real padding: 0
property alias imageSource: icon.source
property color imageColor: controller.settings.foregroundColor

Image {
id: icon
anchors.fill: parent
anchors.margins: root.padding
fillMode: Image.PreserveAspectFit
}

ColorOverlay {
id: overlay
source: icon
anchors.fill: icon
color: root.imageColor
}
}






> On 6 Mar 2018, at 15:41, Mitch Curtis  wrote:
> 
> Can you elaborate on “really bad”, and also share a screenshot?
>  
> From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org 
> ] On Behalf Of 
> Nuno Santos
> Sent: Tuesday, 6 March 2018 4:27 PM
> To: Qt Project MailingList  >
> Subject: [Interest] How to render small Images decently on non retina 
> displays with QtQuick?
>  
> Hi,
>  
> I have a simple question. 
>  
> How to render small Images decently on non retina displays with QtQuick?
>  
> In my apps, I use images for icons and logos. They are all big enough to be 
> displayed correctly. 
>  
> However, on non Retina displays they get really bad! And on retine display 
> they appear perfectly. 
>  
> What is the rule of thumb to use QtQuick Image element on on retina displays?
>  
> Thx!
>  
> Regards,
>  
> Nuno

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

Re: [Interest] How to render small Images decently on non retina displays with QtQuick?

[ekke]

I'm using QtQuickControls2 and Qt::AA_EnableHighDpiScaling
and so all my images are deployed with my app in different solutions

per ex a 24x24px Icon
test.png (24x24) -- for 160 dpi --
t...@2x.png (48x48)
t...@3x.png (72x72)
t...@4x.png (96x96)

and so for all devices with all kind of dpi by magic the Icons and
Images are looking same

if you don't use the HighDpiScaling you can try to check the density and
then scale your Image or deploy your Images/Icons similar to @2x, ...
and select the right one for dpi of actual device running on

ekke

Am 06.03.18 um 16:27 schrieb Nuno Santos:
> Hi,
>
> I have a simple question. 
>
> *How to render small Images decently on non retina displays with QtQuick?*
> *
> *
> In my apps, I use images for icons and logos. They are all big enough
> to be displayed correctly. 
>
> However, on non Retina displays they get really bad! And on retine
> display they appear perfectly. 
>
> What is the rule of thumb to use QtQuick Image element on on retina
> displays?
>
> Thx!
>
> Regards,
>
> Nuno
>
>
> ___
> 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] How to render small Images decently on non retina displays with QtQuick?

[Mitch Curtis]

Can you elaborate on "really bad", and also share a screenshot?

From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org] On 
Behalf Of Nuno Santos
Sent: Tuesday, 6 March 2018 4:27 PM
To: Qt Project MailingList 
Subject: [Interest] How to render small Images decently on non retina displays 
with QtQuick?

Hi,

I have a simple question.

How to render small Images decently on non retina displays with QtQuick?

In my apps, I use images for icons and logos. They are all big enough to be 
displayed correctly.

However, on non Retina displays they get really bad! And on retine display they 
appear perfectly.

What is the rule of thumb to use QtQuick Image element on on retina displays?

Thx!

Regards,

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

[Interest] How to render small Images decently on non retina displays with QtQuick?

[Nuno Santos]

Hi,

I have a simple question. 

How to render small Images decently on non retina displays with QtQuick?

In my apps, I use images for icons and logos. They are all big enough to be 
displayed correctly. 

However, on non Retina displays they get really bad! And on retine display they 
appear perfectly. 

What is the rule of thumb to use QtQuick Image element on on retina displays?

Thx!

Regards,

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

Re: [Interest] Command used by Qt Creator to deploy Apps to iOS devices

[Jeffrey Brendecke]

> On 5. Mar 2018, at 15:26, Jeffrey Brendecke  
> wrote:
> 
> Which command is used by Qt Creator to deploy apps to iOS devices?
> 
> The build logs show everything up through building and signing, but the 
> output goes silent during the deploy phase.

--

I answered my own question by digging around and looking at the Qt Creator 
source:

https://code.qt.io/qt-creator/qt-creator.git 


The code here:
qt-creator/src/tools/iostool/iosdevicemanager.*

Is a C++ variation of the code in ios-deploy, used for PhoneGap:

https://github.com/phonegap/ios-deploy 

It looks like Apple does not want to make the step of creating custom deploy 
tools to an iOS device very easy.___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest