Re: [Interest] Support for Visual Studio 2017

On quarta-feira, 22 de fevereiro de 2017 22:38:09 PST NoRulez wrote: > Hello, > > since visual studio 2017 will be released on march 7th, which Qt version > will support it? Qt 5.8.0, unless Microsoft broke something after the last RC. > Are there any pre-builts for it? Not yet. That will

[Interest] Support for Visual Studio 2017

Hello, since visual studio 2017 will be released on march 7th, which Qt version will support it? Are there any pre-builts for it? Thanks in advance Regards ___ Interest mailing list Interest@qt-project.org

Re: [Interest] Creating a QVariant of QList<QObject*> knowing only the class name

Den 2017-02-23 kl. 00:26, skrev Ch'Gans: On 23 February 2017 at 05:42, Thiago Macieira wrote: On quarta-feira, 22 de fevereiro de 2017 02:40:37 PST Ch'Gans wrote: [...] Tanks for all your inputs, but I'm still puzzled, I can't believe this is not achievable in a

Re: [Interest] Creating a QVariant of QList<QObject*> knowing only the class name

On 23 February 2017 at 05:42, Thiago Macieira wrote: > On quarta-feira, 22 de fevereiro de 2017 02:40:37 PST Ch'Gans wrote: >> > If you're going to call the QVariant constructor with a pointer, you MUST >> > pass a pointer to the correct, concrete object. Forget that it

Re: [Interest] Creating a QVariant of QList<QObject*> knowing only the class name

On 23 February 2017 at 05:42, Thiago Macieira wrote: > On quarta-feira, 22 de fevereiro de 2017 02:40:37 PST Ch'Gans wrote: [...] >> Tanks for all your inputs, but I'm still puzzled, I can't believe this >> is not achievable in a generic way... > > It is achievable. I'm

Re: [Interest] QObject::connect returns true, but the connection does not work

On quarta-feira, 22 de fevereiro de 2017 12:08:52 PST Alexander Dyagilev wrote: > I think it would be a good idea to mention about this in the > QSharedPointer docs That doesn't apply to QSP only. ALL types that you pass via QueuedConnection must be declared and registered. That's actually

Re: [Interest] Send POST request with QOAuth2AuthorizationCodeFlow

Thanks again. Yes, it works. Now I can get refresh_token. But it seems refreshAccessToken -request doesn’t contains client_id and client_secret parameters that are required to refreshing an access token (at least with Google login) … and setModifyParametersFunction is available in

Re: [Interest] QObject::connect returns true, but the connection does not work

On 23 February 2017 at 09:31, Ch'Gans wrote: > On 23 February 2017 at 09:08, Alexander Dyagilev wrote: >> I think it would be a good idea to mention about this in the QSharedPointer >> docs >From QMetaType documentation: Declare new types with

Re: [Interest] QObject::connect returns true, but the connection does not work

On 23 February 2017 at 09:08, Alexander Dyagilev wrote: > I think it would be a good idea to mention about this in the QSharedPointer > docs > > > > On 2/22/2017 11:07 PM, Alexander Dyagilev wrote: >> >> I googled; ok, it's a QSharedPointer. >> >> >>

Re: [Interest] QObject::connect returns true, but the connection does not work

I think it would be a good idea to mention about this in the QSharedPointer docs On 2/22/2017 11:07 PM, Alexander Dyagilev wrote: I googled; ok, it's a QSharedPointer. https://forum.qt.io/topic/6148/qsharedpointer-userdatatype-as-signal-slot-parameters/5 Works fine now. I.e: "I

Re: [Interest] QObject::connect returns true, but the connection does not work

I googled; ok, it's a QSharedPointer. https://forum.qt.io/topic/6148/qsharedpointer-userdatatype-as-signal-slot-parameters/5 Works fine now. I.e: "I think you need to register them. Make a typedef for QSharedPointer, and use both Q_DECLARE_METATYPE as well as qRegisterMetaType() to register

Re: [Interest] QObject::connect returns true, but the connection does not work

On quarta-feira, 22 de fevereiro de 2017 11:33:01 PST Alexander Dyagilev wrote: > Why? Because there's a problem elsewhere in your code. Are you sure the receiver object wasn't deleted? > emit is called; slot is NOT called. > > I use QSharedPointer in slot/signal. > > MyDataType is a struct

Re: [Interest] QObject::connect returns true, but the connection does not work

> Sent: Wednesday, February 22, 2017 at 2:33 PM > From: "Alexander Dyagilev" > To: "interest@qt-project.org" > Subject: [Interest] QObject::connect returns true, but the connection does > not work > > Why? > > emit is called; slot is NOT called.

[Interest] QObject::connect returns true, but the connection does not work

Why? emit is called; slot is NOT called. I use QSharedPointer in slot/signal. MyDataType is a struct declared as metatype. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Creating a QVariant of QList<QObject*> knowing only the class name

On quarta-feira, 22 de fevereiro de 2017 02:40:37 PST Ch'Gans wrote: > > If you're going to call the QVariant constructor with a pointer, you MUST > > pass a pointer to the correct, concrete object. Forget that it was a > > template: just > Well that's my problem, i cannot instanciate and assign

Re: [Interest] [cfe-dev] The QtReslot Clang plugin

On Thursday, 16 February 2017 19:26:48 CET Laszlo Nagy via cfe-dev wrote: > Hey all, > > would it make sense to add these tools to the External Clang Examples > page? Which is a > file in the `docs` directory of the Clang repo. +1.

Re: [Interest] Should Q_INVOKABLE functions be marked as such in the documentation ?

Done : https://bugreports.qt.io/browse/QTBUG-59083 2017-02-22 13:08 GMT+01:00 Bo Thorsen : > Den 22-02-2017 kl. 11:13 skrev Pierre-Yves Siret: > >> Hello, >> >> Reading the doc, there is no indication that a function is Q_INVOKABLE. >> It can sometimes be useful to know what

Re: [Interest] Should Q_INVOKABLE functions be marked as such in the documentation ?

Den 22-02-2017 kl. 11:13 skrev Pierre-Yves Siret: Hello, Reading the doc, there is no indication that a function is Q_INVOKABLE. It can sometimes be useful to know what functions of a Qt C++ class (not specifically designed for QML) can be called from QML in addition to the slots. The only way

Re: [Interest] Send POST request with QOAuth2AuthorizationCodeFlow

On Wednesday, February 22, 2017 10:19:06 AM Juhani Matilainen wrote: > Another question: Google login requires ’access_type=offline’ parameter in > authorization request to get refresh token. Which function should be used to > set it? You can use QAbstractOAuth::setModifyParametersFunction to

[Interest] Should Q_INVOKABLE functions be marked as such in the documentation ?

Hello, Reading the doc, there is no indication that a function is Q_INVOKABLE. It can sometimes be useful to know what functions of a Qt C++ class (not specifically designed for QML) can be called from QML in addition to the slots. The only way I know to do that is to read the source of the

Re: [Interest] Qt5.8 qt3d examples not working

On Tue, 21 Feb 2017 10:41:04 +0100 "Lukáš Sedláček" wrote: > Hello, > > I have just got my Raspberry Pi3 (using raspbian lite without pixel - > only linuxfb/eglfs) and I am having problems to run Qt3d examples > (which will be very useful to for me). I cross compiled

Re: [Interest] Send POST request with QOAuth2AuthorizationCodeFlow

Thank you. Unfortunately I couldn’t get it to work with multipart post request. Do you have an example? But I found that I can successfully use it in the old way: QAbstractOAuth::networkAccessManager::post() Another question: Google login requires ’access_type=offline’ parameter in