Yeah, I knew Qt5 was going to take Qt in a direction that was not going to be a
good one. We've got too many projects and not enough people to support them.
Yes, QML is cool but it shouldn't be done at the expense of things like Udp
Sockets. Support the existing market.
Adding to that Qt5 barely works*... I don't know when people will get back to
supporting core features.
*By barely works, nothing I try to do aside from Rectangles works. GPS doesn't
work, 3D doesn't work, Again they are re-doing the QML rendering mainloop. It's
not working equivalently on all platforms yet.
Qt4 forever! The thing I liked about Qt4 is it all just works, consistently and
well.
________________________________
From: Guido Seifert <warg...@gmx.de>
To: interest@qt-project.org
Sent: Wednesday, September 11, 2013 11:09 AM
Subject: Re: [Interest] QUdpSocket broken?
> All QUdpSocket tests are currently being ignored. They have been ignored for
> the past 2 years. In other words, we have no idea whether QUdpSocket has ever
> worked for Qt 5.
Wow, this is hardly believable. This time it isn't about multicast. It is the
normal send/receive between two QUdpSockets. I cannot believe that such a
severe bug gets unnoticed for such a long time. Not working multicast...
perhaps. But being unable to receive data via udp at all? This should break
more than on project. I would have expected some more bug reports.
Guido
_______________________________________________
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
