Re: [Interest] Qt 5.13.1
On Tuesday, 27 August 2019 11:21:21 PDT ekke wrote: > any ideas when Qt 5.13.1 will be available ? See https://lists.qt-project.org/pipermail/releasing/2019-August/002671.html and check again the mailing list for the meeting from the 27th. I couldn't join so I don't know if the blocker was fixed. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
[Interest] Qt 5.13.1
Hi, any ideas when Qt 5.13.1 will be available ? thx for infos ekke ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
[Interest] Click and hold on close button
One of my users reported an issue that I think falls into the "nothing can be done about it" category, but wanted to see if anyone had any ideas. On a Windows build of our application, if the user clicks AND HOLDS the mouse on any of the Windows buttons (so the standard Windows Minimize, Maximize, and Close buttons) the application's event loop apparently is blocked until the mouse is released. This happens whether it's the QMainWindow window, or any currently shown dialogs. The same application on Linux does not behave this way - at least on Elementary 5.0, I certainly haven't exhaustively gone through all flavors of Linux. But at least on that version of Linux, the user can click and hold the window close button and the application still updates the UI while the mouse button is pressed. I've attached a sample application below that can be used to test. When you build and launch it, a QLabel blinks between green and "normal", switching palettes every second. On Windows, if you click and hold on any of those 3 buttons, and while holding the mouse, move off the original button so that the release event doesn't happen on the same button, the blinking will cease the entire time you have the button pressed. Do the same thing on Linux and the QLabel keeps blinking happily the entire time. Sean This message has been scanned for malware by Forcepoint. www.forcepoint.com <> ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Q_NAMESPACE is not portable?
And I was taught in middle school that such a "for instance" should have commas before and after: "This is useful, for instance, if the object needs to be exported from a dynamic library." > On Aug 27, 2019, at 12:58 AM, Kai Köhne wrote: > > > >> -Original Message- >> From: Interest On Behalf Of Jason H >> Sent: Monday, August 26, 2019 10:33 PM >> To: Andy >> Cc: Qt Project >> Subject: Re: [Interest] Q_NAMESPACE is not portable? >> >> That's what I was attempting to point out. >> I think "for instance" should be written out in this case, or use an >> established >> abbreviation, or dropped entirely: > > I had the same thought > > https://codereview.qt-project.org/c/qt/qtbase/+/271615 > > Kai > ___ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest -John ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] equivalent of python glob
On Mon, Aug 26, 2019 at 11:59:00PM +, Hamish Moffatt wrote: > I think it's a shame there isn't something simpler built in to C++ or Qt > though. There's std::filesystem::path::append in C++17: https://en.cppreference.com/w/cpp/filesystem/path/append Florian -- https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Q_NAMESPACE is not portable?
> -Original Message- > From: Interest On Behalf Of Jason H > Sent: Monday, August 26, 2019 10:33 PM > To: Andy > Cc: Qt Project > Subject: Re: [Interest] Q_NAMESPACE is not portable? > > That's what I was attempting to point out. > I think "for instance" should be written out in this case, or use an > established > abbreviation, or dropped entirely: I had the same thought https://codereview.qt-project.org/c/qt/qtbase/+/271615 Kai ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
