Re: [Development] A new approach for Qt main()

Em segunda-feira, 12 de dezembro de 2016, às 21:12:31 PST, Morten Sorvig escreveu: > > Can we get a description of what those problems are, for those of us who > > have never developed anything for those OSes, so we're not discussing > > things in the abstract? > > For some background, here’s

Re: [Development] A new approach for Qt main()

> On 10 Dec 2016, at 01:43, Thiago Macieira wrote: > > Em sexta-feira, 9 de dezembro de 2016, às 16:50:29 PST, Matthew Woehlke > escreveu: >> On 2016-12-09 16:23, Thiago Macieira wrote: >>> Em sexta-feira, 9 de dezembro de 2016, às 15:28:13 PST, Matthew Woehlke >>>

Re: [Development] A new approach for Qt main()

> On 9 Dec 2016, at 18:05, Thiago Macieira wrote: > > Em sexta-feira, 9 de dezembro de 2016, às 10:44:24 PST, Lars Knoll escreveu: >> Well, the problem is that the main() entry point is causing huge amounts of >> issues on at least Android and iOS. We’d help those

Re: [Development] A new approach for Qt main()

Hi, Seems this turned into a nice bike shed discussion quickly, so let me use the chance to present my preferred Qt main(). I am totally convinced that this one should rule the Qt world: class BlueBikeShedApplication : public QApplication { Q_OBJECT public: using

Re: [Development] A new approach for Qt main()

On segunda-feira, 12 de dezembro de 2016 16:11:07 PST Edward Welbourne wrote: > I haven't seen an actual reply to that, but these fragments at least > point towards a sketch of the reply: We already have a solution for those cases and that's QAbstractEventDispatcher. -- Thiago Macieira -

Re: [Development] A new approach for Qt main()

On segunda-feira, 12 de dezembro de 2016 11:07:56 PST Benjamin TERRIER wrote: > 2016-12-12 10:56 GMT+01:00 Mark De Wit : > > I have an application based on qt-solutions qtwinmigrate sample. > > > > Because we're integrating Qt into an existing MFC application, we're not > >

Re: [Development] A new approach for Qt main()

Em sexta-feira, 9 de dezembro de 2016, às 10:44:24 PST, Lars Knoll escreveu: > Well, the problem is that the main() entry point is causing huge > amounts of issues on at least Android and iOS. We’d help those > platforms a lot if we didn’t support this kind of entry point (on >

Re: [Development] A new approach for Qt main()

12.12.2016, 13:08, "Benjamin TERRIER" : > 2016-12-12 10:56 GMT+01:00 Mark De Wit : >>  I have an application based on qt-solutions qtwinmigrate sample. >> >>  Because we're integrating Qt into an existing MFC application, we're not >> even running

Re: [Development] A new approach for Qt main()

2016-12-12 10:56 GMT+01:00 Mark De Wit : > I have an application based on qt-solutions qtwinmigrate sample. > > Because we're integrating Qt into an existing MFC application, we're not even > running QApplication exec. The application uses MFC's entry point for > startup

Re: [Development] A new approach for Qt main()

I have an application based on qt-solutions qtwinmigrate sample. Because we're integrating Qt into an existing MFC application, we're not even running QApplication exec. The application uses MFC's entry point for startup and drives the Qt event loop manually as part of the MFC event loop.

Re: [Development] Review needed on new TLS feature "server side signature algorithms"

Hi, I'll review the patch this week (well, somebody will probably do it faster). Best regards, Timur. From: Development on behalf of Lösch, Sebastian Sent:

[Development] Review needed on new TLS feature "server side signature algorithms"

Hello, I would like to contribute a patch to qt's network module to make the signature algorithms on the server side configurable for TLS connections. I am looking for someone with knowledge in TLS to review my patch on gerrit: https://codereview.qt-project.org/#/c/173427/ Thanks in advance for