Re: [Interest] QIcon vs QQuickIcon

2022-06-14 Thread Remy Rouvin
What about passing the image in base64 format in the source property ? -Message d'origine- De : Interest De la part de ivan tkachenko Envoyé : mercredi 1 juin 2022 01:08 À : Benjamin TERRIER Cc : Qt Interest Objet : Re: [Interest] QIcon vs QQuickIcon > The standard solution i

Re: [Interest] QIcon vs QQuickIcon

2022-05-31 Thread ivan tkachenko
> The standard solution is to use a QQuickImageProvider. > In C++ you would implement your own QQuickImageProvider which will contain > the QIcons. > In QML then you would use a url like "image://myprovider/icon_id". > Then the QML engine will call your QQuickImageProvider to retrieve the icon > im

Re: [Interest] QIcon vs QQuickIcon

2022-05-31 Thread Benjamin TERRIER
On Sun, 29 May 2022 at 16:31, ivan tkachenko wrote: > Hi, > > I have a problem which sounds like it should be something trivial. > > I got a QIcon icon, aquired from a model by a delegate. How do i use it in > controls with all these icon.name [string], icon.source [url] groupped > properties or

Re: [Interest] QIcon vs QQuickIcon

2022-05-29 Thread EXT Mitch Curtis
As QIcon isn’t a gadget, you will probably need to make model roles for name and source and assign those to the QQuickIcon’s properties instead. From: Interest on behalf of ivan tkachenko Date: Sunday, 29 May 2022 at 22:33 To: interest@qt-project.org Subject: [Interest] QIcon vs QQuickIcon Hi