Re: [Interest] Qt online installer error (Mac)
Thanks to all, that fixed the issue! On Fri, Dec 15, 2023 at 7:36 AM Sze Howe Koh wrote: > On Thu, 14 Dec 2023 at 21:35, Calogero Mauceri > wrote: > > > > Thanks Henry, > > > > do I have control on which mirror to use? > > Yes: > https://wiki.qt.io/Online_Installer_4.x#Selecting_a_mirror_for_opensource > > > > -- > > Calogero Mauceri > > Software Engineer > > > > Applied Coherent Technology Corporation (ACT) > > www.actgate.com > > Regards, > Sze-Howe > -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt online installer error (Mac)
trying to download the source files from https://ftp.fau.de/qtproject/archive/qt/6.6/6.6.1/single/qt-everywhere-src-6.6.1.tar.xz gives a ERR_TIMED_OUT error On Thu, Dec 14, 2023 at 2:32 PM Calogero Mauceri wrote: > Thanks Henry, > > do I have control on which mirror to use? > > On Thu, Dec 14, 2023 at 2:23 PM Henry Skoglund wrote: > >> >> >> On 2023-12-14 14:13, Calogero Mauceri wrote: >> >> Hi all, >> >> I'm trying to install latest Qt 6 release for Mac through qt online >> installer but I get the following error message >> >> Cannot download archive >> http://download.qt.io/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z: >> Socket operation timed out >> >> >> Any clues on how to fix this? >> >> Thanks, >> >> Calogero >> >> -- >> Calogero Mauceri >> Software Engineer >> >> Applied Coherent Technology Corporation (ACT) >> www.actgate.com >> >> >> Hi, maybe a bad/down mirror, mine works, using wget to find the url: >> >> wget >> http://download.qt.io/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z >> --2023-12-14 14:17:17-- >> http://download.qt.io/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z >> Resolving download.qt.io (download.qt.io)... 77.86.162.2 >> Connecting to download.qt.io (download.qt.io)|77.86.162.2|:80... >> connected. >> HTTP request sent, awaiting response... 301 Moved Permanently >> Location: >> https://download.qt.io/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z >> [following] >> --2023-12-14 14:17:18-- >> https://download.qt.io/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z >> Connecting to download.qt.io (download.qt.io)|77.86.162.2|:443... >> connected. >> HTTP request sent, awaiting response... 302 Found >> Location: >> https://ftp.acc.umu.se/mirror/qt.io/qtproject/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z >> [following] >> --2023-12-14 14:17:18-- >> https://ftp.acc.umu.se/mirror/qt.io/qtproject/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z >> Resolving ftp.acc.umu.se (ftp.acc.umu.se)... 194.71.11.165, >> 194.71.11.173, 194.71.11.163 >> Connecting to ftp.acc.umu.se (ftp.acc.umu.se)|194.71.11.165|:443... >> connected. >> HTTP request sent, awaiting response... 302 Found >> Location: >> https://chuangtzu.ftp.acc.umu.se/mirror/qt.io/qtproject/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z >> [following] >> --2023-12-14 14:17:18-- >> https://chuangtzu.ftp.acc.umu.se/mirror/qt.io/qtproject/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z >> Resolving chuangtzu.ftp.acc.umu.se (chuangtzu.ftp.acc.umu.se)... >> 194.71.11.167 >> Connecting to chuangtzu.ftp.acc.umu.se >> (chuangtzu.ftp.acc.umu.se)|194.71.11.167|:443... >> connected. >> HTTP request sent, awaiting response... 200 OK >> Length: 11001956 (10M) [application/x-7z-compressed] >> Saving to: >> ‘4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z.1’ >> >> 4.6.1-0-202308231236tqtc-installer-f >> 100%[>] >> 10,49M 41,8MB/sin 0,3s >> >> 2023-12-14 14:17:18 (41,8 MB/s) - >> ‘4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z.1’ >> saved [11001956/11001956] >> >> So try this URL: >> >> http
Re: [Interest] Qt online installer error (Mac)
Thanks Henry, do I have control on which mirror to use? On Thu, Dec 14, 2023 at 2:23 PM Henry Skoglund wrote: > > > On 2023-12-14 14:13, Calogero Mauceri wrote: > > Hi all, > > I'm trying to install latest Qt 6 release for Mac through qt online > installer but I get the following error message > > Cannot download archive > http://download.qt.io/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z: > Socket operation timed out > > > Any clues on how to fix this? > > Thanks, > > Calogero > > -- > Calogero Mauceri > Software Engineer > > Applied Coherent Technology Corporation (ACT) > www.actgate.com > > > Hi, maybe a bad/down mirror, mine works, using wget to find the url: > > wget > http://download.qt.io/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z > --2023-12-14 14:17:17-- > http://download.qt.io/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z > Resolving download.qt.io (download.qt.io)... 77.86.162.2 > Connecting to download.qt.io (download.qt.io)|77.86.162.2|:80... > connected. > HTTP request sent, awaiting response... 301 Moved Permanently > Location: > https://download.qt.io/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z > [following] > --2023-12-14 14:17:18-- > https://download.qt.io/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z > Connecting to download.qt.io (download.qt.io)|77.86.162.2|:443... > connected. > HTTP request sent, awaiting response... 302 Found > Location: > https://ftp.acc.umu.se/mirror/qt.io/qtproject/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z > [following] > --2023-12-14 14:17:18-- > https://ftp.acc.umu.se/mirror/qt.io/qtproject/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z > Resolving ftp.acc.umu.se (ftp.acc.umu.se)... 194.71.11.165, > 194.71.11.173, 194.71.11.163 > Connecting to ftp.acc.umu.se (ftp.acc.umu.se)|194.71.11.165|:443... > connected. > HTTP request sent, awaiting response... 302 Found > Location: > https://chuangtzu.ftp.acc.umu.se/mirror/qt.io/qtproject/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z > [following] > --2023-12-14 14:17:18-- > https://chuangtzu.ftp.acc.umu.se/mirror/qt.io/qtproject/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z > Resolving chuangtzu.ftp.acc.umu.se (chuangtzu.ftp.acc.umu.se)... > 194.71.11.167 > Connecting to chuangtzu.ftp.acc.umu.se > (chuangtzu.ftp.acc.umu.se)|194.71.11.167|:443... > connected. > HTTP request sent, awaiting response... 200 OK > Length: 11001956 (10M) [application/x-7z-compressed] > Saving to: > ‘4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z.1’ > > 4.6.1-0-202308231236tqtc-installer-f > 100%[>] > 10,49M 41,8MB/sin 0,3s > > 2023-12-14 14:17:18 (41,8 MB/s) - > ‘4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z.1’ > saved [11001956/11001956] > > So try this URL: > > https://chuangtzu.ftp.acc.umu.se/mirror/qt.io/qtproject/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z > > Rgrds Henry > > > > ___ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest > -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
[Interest] Qt online installer error (Mac)
Hi all, I'm trying to install latest Qt 6 release for Mac through qt online installer but I get the following error message Cannot download archive http://download.qt.io/online/qtsdkrepository/mac_x64/desktop/tools_maintenance/qt.tools.maintenance/4.6.1-0-202308231236tqtc-installer-framework-MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64-QtInstaller.7z: Socket operation timed out Any clues on how to fix this? Thanks, Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] QGraphicsView and OpenGL in Qt6
Volker, thanks for you suggestion. Just filed a bug report https://bugreports.qt.io/browse/QTBUG-119494 Calogero On Fri, Nov 24, 2023 at 5:37 PM Volker Hilsheimer wrote: > Hi Calogero, > > QGraphicsView is still supported, and, like all of Qt Widgets, is in no > danger of being deprecated. If you think that you are experiencing a bug in > Qt, please report as usual, with a reproducer that is ideally not your > pretty complex application :) > > Interesting information might be which platform you see this on, and > whether you are running your UI on a display with a fractional scale level, > as that might result in rounding errors in the integer-based painting > architecture of Qt Widgets and QGraphicsView. > > Volker > > > On 23 Nov 2023, at 16:28, Calogero Mauceri wrote: > > Hi Shawn, > > Thanks for your exhaustive explanation. > As I mentioned the application is pretty complex, it is not only showing > tiles but much more items the user can interact with. Reimplementing it > would be a huge amount of work that would require too much time and > resources and be bug prone. > > I am looking for a fix/workaround with the current QGraphicsView, if there > is one. If using OpenGL rendering is safe enough I'm OK in enabling it. The > fact that Graphics View is not supported anymore (and possibly at risk of > deprecation in future Qt releases) does not make me feel so good though. > > On Thu, Nov 23, 2023 at 3:40 PM Shawn Rutledge via Interest < > interest@qt-project.org> wrote: > >> >> On 23 Nov 2023, at 02:37, Calogero Mauceri wrote: >> >> Hi all, >> >> We finally decided to port our Qt5 based application to Qt6. >> It is a pretty complex application. The main view is a QGraphicsView with >> multiple items: images, paths, possible animations and so on. >> >> I remember in Qt5 OpenGL rendering was experimental with lots of issues. >> My question is, is QGraphicsView OpenGL rendering more stable in the Qt6 >> era? or even better, is it suggested to render using OpenGL? (note: it is a >> cross platform application that should run on Windows, Mac or Linux >> machines). >> >> To be more specific. The QGraphicsView shows a map. The map is made up of >> multiple tiles that should align perfectly. Each tile is a >> QGraphicsPixmapItem. After porting to Qt6, it sometimes happens that when >> applying a scale to the tiles, then there are gaps between them. It does >> not always happen, but it can. >> I'm pretty sure the QGraphicsPixmapItems are properly scaled and >> positioned. It was working as expected in Qt5. >> >> >> Depending on how much you want to invest in porting, maybe it’s time to >> check whether you can use Qt Quick now? >> >> I have also wondered if we need explicit support for large tiled images. >> We need tiles in Qt Location for example, but in that case it’s already >> conventional to download pre-rendered fixed-size tiles, so that’s what we >> do; and the implementation is a C++ one-off, not depending on any reusable >> tiling implementation, since we don’t have one yet. I also wondered how >> many people will want to use QtPDF to render very large pages >> (architectural drawings, electrical schematics, maps and so on), so I >> figured the tiling mechanism might be useful there too, if we had one. But >> I tried using TableView for that, and it was reasonably successful. >> TableView does a good job with instantiating the tiles just-in-time: you >> only get as many tiles as you can see onscreen, and an extra “border” of >> spare tiles in case you then pan the view by small increments. In the PDF >> case, rendering tiles is the bottleneck, because QtPDF uses the same raster >> engine that Chrome does to render PDF pages, and it's not >> multi-thread-capable; so tiling with TableView made it possible to render >> large pages at a higher resolution than you could fit into a single GPU >> texture, but caused a big slowdown (rendering each tile took almost as long >> as rendering the whole page at maximum texture size: just a demonstration >> of what’s wrong with CPU-based raster engines). But if you can get your >> tiles quickly, I think TableView is great for that. The tiles can fit >> together perfectly with no gap, and you get the advantage of its >> well-maintained dynamic loading mechanism. Each tile is a Qt Quick >> Item-based delegate though (at least an Image, plus whatever else you >> declare there), so as with item views in general, you should avoid making >> your delegates too complex (interactive per-tile features), because the >> overhead gets m
Re: [Interest] QGraphicsView and OpenGL in Qt6
Hi Shawn, Thanks for your exhaustive explanation. As I mentioned the application is pretty complex, it is not only showing tiles but much more items the user can interact with. Reimplementing it would be a huge amount of work that would require too much time and resources and be bug prone. I am looking for a fix/workaround with the current QGraphicsView, if there is one. If using OpenGL rendering is safe enough I'm OK in enabling it. The fact that Graphics View is not supported anymore (and possibly at risk of deprecation in future Qt releases) does not make me feel so good though. On Thu, Nov 23, 2023 at 3:40 PM Shawn Rutledge via Interest < interest@qt-project.org> wrote: > > On 23 Nov 2023, at 02:37, Calogero Mauceri wrote: > > Hi all, > > We finally decided to port our Qt5 based application to Qt6. > It is a pretty complex application. The main view is a QGraphicsView with > multiple items: images, paths, possible animations and so on. > > I remember in Qt5 OpenGL rendering was experimental with lots of issues. > My question is, is QGraphicsView OpenGL rendering more stable in the Qt6 > era? or even better, is it suggested to render using OpenGL? (note: it is a > cross platform application that should run on Windows, Mac or Linux > machines). > > To be more specific. The QGraphicsView shows a map. The map is made up of > multiple tiles that should align perfectly. Each tile is a > QGraphicsPixmapItem. After porting to Qt6, it sometimes happens that when > applying a scale to the tiles, then there are gaps between them. It does > not always happen, but it can. > I'm pretty sure the QGraphicsPixmapItems are properly scaled and > positioned. It was working as expected in Qt5. > > > Depending on how much you want to invest in porting, maybe it’s time to > check whether you can use Qt Quick now? > > I have also wondered if we need explicit support for large tiled images. > We need tiles in Qt Location for example, but in that case it’s already > conventional to download pre-rendered fixed-size tiles, so that’s what we > do; and the implementation is a C++ one-off, not depending on any reusable > tiling implementation, since we don’t have one yet. I also wondered how > many people will want to use QtPDF to render very large pages > (architectural drawings, electrical schematics, maps and so on), so I > figured the tiling mechanism might be useful there too, if we had one. But > I tried using TableView for that, and it was reasonably successful. > TableView does a good job with instantiating the tiles just-in-time: you > only get as many tiles as you can see onscreen, and an extra “border” of > spare tiles in case you then pan the view by small increments. In the PDF > case, rendering tiles is the bottleneck, because QtPDF uses the same raster > engine that Chrome does to render PDF pages, and it's not > multi-thread-capable; so tiling with TableView made it possible to render > large pages at a higher resolution than you could fit into a single GPU > texture, but caused a big slowdown (rendering each tile took almost as long > as rendering the whole page at maximum texture size: just a demonstration > of what’s wrong with CPU-based raster engines). But if you can get your > tiles quickly, I think TableView is great for that. The tiles can fit > together perfectly with no gap, and you get the advantage of its > well-maintained dynamic loading mechanism. Each tile is a Qt Quick > Item-based delegate though (at least an Image, plus whatever else you > declare there), so as with item views in general, you should avoid making > your delegates too complex (interactive per-tile features), because the > overhead gets multiplied by the number of delegates. > > Graphics View on the other hand has not been getting much attention in R&D > for over a decade already: only bug fixes. (Many of us haven’t used it > much ourselves, aren’t very familiar with the implementation, and haven’t > learned all the lessons that we could from it. This includes me, although > I had a simple use case for it once in an application.) We hope it will > eventually be obsolete when we’ve developed solutions for the known use > cases in Qt Quick, but we also know that we’re not there yet. I suspect > that tiling could be considered just a specialization of a more general > spatial-instantiation architecture: if you have a big collection of 2D > assets with random sizes and positions, stored in some kind of model (QAIM > or hopefully something better?), can we propose a standard API to figure > out which views of them (delegates) will intersect the viewport? > (Obviously, without instantiating all the delegates just to find out) One > big difference between CPU-based rendering and Qt Quick is that y
Re: [Interest] Modeless dialog issue on Mac
Thanks Oliver for you hint, I tried the example application you suggested, it seems none of the flags combination results in the wanted result: either the window is behind the main application or it is on top of all desktop applications On Wed, Nov 15, 2023 at 1:25 PM Oliver Knoll wrote: > > > Am 15.11.2023 um 13:14 schrieb Oliver Knoll : > > But I understand your use case better now, and yes, it is different from > mine. However I don‘t know any „top of application (only)“ flag myself (not > saying that Qt doesn’t provide such a flag - I just don’t know). > > > And what do we do if we developers are too lazy to read the fine manual? > Exactly! We have someone else read it for us - like your favourite LLM! ;) > > Here is what ChatGPT has to say about it: > > https://zzzcode.ai/answer-question?id=d21e6762-84c8-406c-823c-f379471ce766 > > Quote: „ Yes, in Qt, there is a flag that can be used to make a modeless > dialog stay on top of the application. This flag is called > Qt::WindowStaysOnTopHint. By setting this flag on a modeless dialog, you > can ensure that the dialog remains on top of all other windows in the > application.“ > > And even better: a quick research reveals that this flag („hint“) actually > seems to exist ;) > > In fact, you can try it out right away and tell us how it went: > > https://doc.qt.io/qt-6/qtwidgets-widgets-windowflags-example.html > > ;) > > Hope that helps! > Oliver > > -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Modeless dialog issue on Mac
Here "this" is a pointer to the parent dialog. I've tried with QMainWindow too as a parent, but unfortunately the problem is still there, not sure if that's another bug. The only way I found for having the modeless dialog on top of its parent is to create it with Qt::Tool flag. That problem is only happening on Mac, it is properly working both on Windows and Linux. On Tue, Nov 14, 2023 at 4:22 PM Frank Osterfeld wrote: > > > > On 14. Nov 2023, at 11:49, Calogero Mauceri wrote: > > > > Hi all, > > > > I have the following problem with dialogs on the Mac. > > > > I have a main window/dialog and I am opening a modeless dialog, I need > to have both the main window/dialog and the modeless dialog visible at the > same time. > > I create the modeless dialog as simple as this > > > > QDialog* myDialog = new QDialog(this); > > What is “this” here? The main window? I’ve seen these problems (unexpected > window stacking) on Mac more than elsewhere when no parent/the wrong parent > was passed, but can’t remember seeing it when passing the main window. > (Haven’t done much macOS/Widget development recently though) > > — > Frank Gonçalves Osterfeld | frank.osterf...@kdab.com | Senior Software > Engineer & Teamlead > KDAB (Deutschland) GmbH, a KDAB Group Company > Tel: +49-30-521325470 > KDAB - The Qt, C++ and OpenGL Experts > -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Modeless dialog issue on Mac
Thanks, https://bugreports.qt.io/browse/QTBUG-119129 On Tue, Nov 14, 2023 at 1:09 PM Tor Arne Vestbø wrote: > The broken button rendering is a bug, please file one in JIRA, thanks :) > > On 14 Nov 2023, at 11:49, Calogero Mauceri wrote: > > Hi all, > > I have the following problem with dialogs on the Mac. > > I have a main window/dialog and I am opening a modeless dialog, I need to > have both the main window/dialog and the modeless dialog visible at the > same time. > I create the modeless dialog as simple as this > > QDialog* myDialog = new QDialog(this); > [...] > myDialog->show(); > myDialog->raise(); > myDialog->activateWindow(); > > The problem I'm having is that if I click on the main window then the > dialog disappears behind the main application window. > The workaround I've found is to create the dialog as a tool dialog. In > that case the dialog stays always on top of the main application window, > but there are some issues with the modeless dialog default button rendering > when the dialog loses focus as visible in the following image where the > default button in the first one. > > > > I created a very sample application that opens both a "standard" dialog > and a tool dialog, here are both issues in a screenshot > > > > > The standard dialog is behind the main application, while the tool dialog > default button is not properly rendered when the tool dialog loses focus. > > Is there any workaround? Is this a Qt bug? > Attached is the code for the above example. > The example works fine on windows, with both types of dialogs. > > -- > Calogero Mauceri > Software Engineer > > Applied Coherent Technology Corporation (ACT) > www.actgate.com > > ___ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest > > > -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Unable to build Qt 5.12 on Ubuntu 14.04
Fair, thank you all for you great hints. We now know why we were getting the config error and will take a decision based on your hints. Thanks, Calogero On Wed, Mar 20, 2019 at 7:28 PM Thiago Macieira wrote: > On Wednesday, 20 March 2019 06:29:19 PDT Kevin Funk wrote: > > Also, another hint for you and the other person(s) trying to build > recent Qt > > on an old Ubuntu LTS: Note that Ubuntu 14.04 is reaching end-of-life in > one > > month(!), and only the ESM version contains further security fixes. > > > > See: > > https://blog.ubuntu.com/2019/02/05/ubuntu-14-04-trusty-tahr > > > > Time to upgrade I think. You're two LTS versions behind. > > Which is one of the reasons that dropping the bundled xkbcommon was > acceptable: recent enough distros have it. > > -- > 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 > -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Unable to build Qt 5.12 on Ubuntu 14.04
On Tue, Mar 19, 2019 at 7:54 PM Thiago Macieira wrote: > On Tuesday, 19 March 2019 09:40:42 PDT Calogero Mauceri wrote: > > Hi all, > > > > I'm trying to build Qt 5.12.2 on Ubuntu 14.04. > > I get the following error just after I launch the configure > > > > ERROR: Feature 'xcb' was enabled, but the pre-condition 'features.thread > && > > features.xkbcommon && libs.xcb' failed. > > > > here is the configure line I'm using > > > > ./configure -qt-zlib -fontconfig -qt-xcb > > > > I have libxcb1 and libxcb1-dev 1.10-2ubuntu1 installed on the system. > > I am building on a 32 bit system, but I get the same error on a 64 bit > > machine. > > Am I missing some other dependencies? Do you know how to check? > > Yes, the error message told you which one: "features.xkbcommon && > libs.xcb". > Since you have installed the XCB libraries, you should check for xkbcommon > ones. > > If you have libxcb1-dev installed, why are you passing -qt-xcb? And, for > that > matter, why -qt-zlib? Just use your distro's packages for those. > Thanks Thiago for your reply, xkbcommon is installed on the machine, version 0.4.1, but we still get that issue. We are building qt with the -qt-xcb option to limit the number of system dependencies for our application. -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
[Interest] Unable to build Qt 5.12 on Ubuntu 14.04
Hi all, I'm trying to build Qt 5.12.2 on Ubuntu 14.04. I get the following error just after I launch the configure ERROR: Feature 'xcb' was enabled, but the pre-condition 'features.thread && features.xkbcommon && libs.xcb' failed. here is the configure line I'm using ./configure -qt-zlib -fontconfig -qt-xcb I have libxcb1 and libxcb1-dev 1.10-2ubuntu1 installed on the system. I am building on a 32 bit system, but I get the same error on a 64 bit machine. Am I missing some other dependencies? Do you know how to check? Thanks in advance for you help, -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Error building Qt 5.8 with Xcode 8
Thank you very much Alexandru! executing the following command worked sudo /usr/bin/xcode-select -switch /Applications/Xcode.app/Contents/Developer On Fri, May 19, 2017 at 6:34 PM, Alexandru Croitor wrote: > Maybe try executing > > sudo /usr/bin/xcode-select -switch /Applications/Xcode.app/Contents/Developer > > > or > > $ DEVELOPER_DIR="/Applications/Xcode.app/Contents/Developer/" > $ export DEVELOPER_DIR > > and then the xcrun command. > > It might be also that you need to install the command line tools via App > store (I think you can do it through XCode preferences as well). > > > On 19 May 2017, at 18:31, Calogero Mauceri wrote: > > Hi Alexandru, > > executing > > /usr/bin/xcrun -find xcodebuild > > I get the following error > > xcrun: error: unable to find utility "xcodebuild", not a developer tool or > in PATH > > Note that xcodebuild is in /usr/bin and that path in is PATH > > I installed XCode via App Store > > Calogero > > > > On Fri, May 19, 2017 at 6:17 PM, Alexandru Croitor io> wrote: > >> Hi, >> >> If you grep for the message, you can find that it's printed in >> qtbase/mkspecs/features/mac/default_pre.prf >> >> It checks for xcode by running "/usr/bin/xcrun -find xcodebuild >> 2>/dev/null" >> >> Try to run that from your terminal and check what's the output. >> >> One possible cause might be when you installed Xcode through different >> means: via app store or via regular download. >> >> Alex. >> >> On 19 May 2017, at 18:08, Calogero Mauceri wrote: >> >> Hi all, >> >> Trying to build Qt 5.8 on Mac OS 10.12.5, I get get the following error >> >> ./configure >> >> + cd qtbase >> + /Users/myuser/qt-everywhere-opensource-src-5.8.0/qtbase/configure >> -top-level >> >>Xcode not set up properly. You may need to confirm the license >>agreement by running /usr/bin/xcodebuild without arguments. >> >> >> XCode 8.3.2 is properly installed and configured on that machine. >> >> Any suggestions on how to fix this issue? >> >> Thanks, >> Calogero >> >> -- >> Calogero Mauceri >> Software Engineer >> >> Applied Coherent Technology Corporation (ACT) >> www.actgate.com >> ___ >> Interest mailing list >> Interest@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/interest >> >> >> > > > -- > Calogero Mauceri > Software Engineer > > Applied Coherent Technology Corporation (ACT) > www.actgate.com > > > -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Error building Qt 5.8 with Xcode 8
Hi Alexandru, executing /usr/bin/xcrun -find xcodebuild I get the following error xcrun: error: unable to find utility "xcodebuild", not a developer tool or in PATH Note that xcodebuild is in /usr/bin and that path in is PATH I installed XCode via App Store Calogero On Fri, May 19, 2017 at 6:17 PM, Alexandru Croitor wrote: > Hi, > > If you grep for the message, you can find that it's printed in > qtbase/mkspecs/features/mac/default_pre.prf > > It checks for xcode by running "/usr/bin/xcrun -find xcodebuild > 2>/dev/null" > > Try to run that from your terminal and check what's the output. > > One possible cause might be when you installed Xcode through different > means: via app store or via regular download. > > Alex. > > On 19 May 2017, at 18:08, Calogero Mauceri wrote: > > Hi all, > > Trying to build Qt 5.8 on Mac OS 10.12.5, I get get the following error > > ./configure > > + cd qtbase > + /Users/myuser/qt-everywhere-opensource-src-5.8.0/qtbase/configure > -top-level > >Xcode not set up properly. You may need to confirm the license >agreement by running /usr/bin/xcodebuild without arguments. > > > XCode 8.3.2 is properly installed and configured on that machine. > > Any suggestions on how to fix this issue? > > Thanks, > Calogero > > -- > Calogero Mauceri > Software Engineer > > Applied Coherent Technology Corporation (ACT) > www.actgate.com > _______ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > > > -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Error building Qt 5.8 with Xcode 8
Hi all, Trying to build Qt 5.8 on Mac OS 10.12.5, I get get the following error ./configure + cd qtbase + /Users/myuser/qt-everywhere-opensource-src-5.8.0/qtbase/configure -top-level Xcode not set up properly. You may need to confirm the license agreement by running /usr/bin/xcodebuild without arguments. XCode 8.3.2 is properly installed and configured on that machine. Any suggestions on how to fix this issue? Thanks, Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt 5.8 - fontconfig config error
yes, I did :/. Just to add more information, the system is 64 bit and I'm building Qt in 32 bit. Of course I installed fonconfig and freetype (and development packages) in 32 bit. Calogero On Mon, Apr 3, 2017 at 2:45 PM, Konstantin Tokarev wrote: > > > 03.04.2017, 15:44, "Calogero Mauceri" : > > Hi all, > > > > I'm trying to build Qt 5.8 on Ubuntu 14.04 but I get an error related to > fontconfig > > > > Here is my configure string > > > > ./configure -qt-zlib -system-libpng -system-libjpeg -platform > linux-g++-32 -qt-xcb -nomake examples -nomake tools -fontconfig > > > > and this is the error I get > > > > ERROR: Feature 'fontconfig' was enabled, but the pre-condition > '!config.win32 && !config.darwin && features.system-freetype && > libs.fontconfig' failed. > > > > I installed both fontconfig and freetype for i386. Is there anything > else I need to install? > > Have you installed development packages? > > > > > Thanks in advance for your help, > > Calogero > > > > -- > > Calogero Mauceri > > Software Engineer > > > > Applied Coherent Technology Corporation (ACT) > > www.actgate.com > > , > > > > ___ > > Interest mailing list > > Interest@qt-project.org > > http://lists.qt-project.org/mailman/listinfo/interest > > > -- > Regards, > Konstantin > -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Qt 5.8 - fontconfig config error
Hi all, I'm trying to build Qt 5.8 on Ubuntu 14.04 but I get an error related to fontconfig Here is my configure string ./configure -qt-zlib -system-libpng -system-libjpeg -platform linux-g++-32 -qt-xcb -nomake examples -nomake tools -fontconfig and this is the error I get ERROR: Feature 'fontconfig' was enabled, but the pre-condition '!config.win32 && !config.darwin && features.system-freetype && libs.fontconfig' failed. I installed both fontconfig and freetype for i386. Is there anything else I need to install? Thanks in advance for your help, Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Problem with XCB and OpenGL
Il 5/18/2016 3:46 PM, Sean Harmer ha scritto: On Wednesday 18 May 2016 13:13:42 Calogero Mauceri wrote: GLX no What OpenGL do you have? Any? You need the EGL (for OpenGL ES) or GLX for "desktop" OpenGL typically. Make sure configure can find those headers etc. Sean, thank you very much for your hint. I had GLX installed on my machine but since Qt could not find it I installed EGL too. I think I'm affected by this bug https://bugreports.qt.io/browse/QTBUG-43784 causing GLX to be disabled when -qt-xcb option is used in configure. I applied the patch suggested there (*https://codereview.qt-project.org/#/c/150646/2/configure*) and the configure output seems OK now (see attached file). I also managed to compile Qt (5.6.0) without any apparent error. Unfortunately when I run the application I still have the same issue: "QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled7" Do you have any other hints? Thanks, Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com Configure summary Build type:linux-g++-32 (i386, CPU features: none detected) Build options: Configuration .. accessibility accessibility-atspi-bridge audio-backend avx c++11 clock-gettime clock-monotonic compile_examples concurrent dbus enable_new_dtags evdev eventfd fontconfig full-config getaddrinfo getifaddrs harfbuzz iconv inotify ipv6ifname large-config largefile linuxfb medium-config minimal-config mremap nis opengl openssl pcre png posix_fallocate precompile_header qpa qpa reduce_exports reduce_relocations release rpath shared small-config sse2 sse3 sse4_1 sse4_2 ssse3 system-freetype system-jpeg system-png threadsafe-cloexec xcb xcb-glx xcb-plugin xcb-qt xcb-xlib xinput2 xkbcommon-qt xlib xrender zlib Build parts libs Mode ... release Using sanitizer(s).. none Using C++ standard . c++11 Using gold linker... no Using new DTAGS yes Using PCH .. yes Using LTCG . no Target compiler supports: SSE2/SSE3/SSSE3 .. yes/yes/yes SSE4.1/SSE4.2 yes/yes AVX/AVX2 . yes/no Qt modules and options: Qt D-Bus ... yes (loading dbus-1 at runtime) Qt Concurrent .. yes Qt GUI . yes Qt Widgets . yes Large File . yes QML debugging .. yes Use system proxies . no Support enabled for: Accessibility .. yes ALSA ... no CUPS ... no Evdev .. yes FontConfig . yes FreeType ... yes (system library) Glib ... no GStreamer .. no GTK theme .. no HarfBuzz ... yes (bundled copy) Iconv .. yes ICU no Image formats: GIF .. yes (plugin, using bundled copy) JPEG . yes (plugin, using system library) PNG .. yes (in QtGui, using system library) libinput no Logging backends: journald ... no syslog ... no mtdev .. no Networking: getaddrinfo .. yes getifaddrs ... yes IPv6 ifname .. yes libproxy.. no OpenSSL .. yes (loading libraries at run-time) NIS yes OpenGL / OpenVG: EGL .. no OpenGL ... desktop OpenVG ... no PCRE ... yes (bundled copy) pkg-config . yes PulseAudio . no QPA backends: DirectFB . no EGLFS no EGLFS i.MX6 no EGLFS i.MX6 Wayland. no EGLFS EGLDevice no EGLFS GBM .. no EGLFS Mali . no EGLFS Raspberry Pi . no EGLFS X11 .. no LinuxFB .. yes Mir client no XCB .. yes (bundled copy) EGL on X ... no GLX yes MIT-SHM yes Xcb-Xlib ... yes Xcursor yes (loaded at runtime) Xfixes . yes (loaded at runtime) Xi . no Xi2 yes Xinerama ... yes (loaded at runtime) Xrandr . yes (loaded at runtime) Xrender yes XKB yes XShape . yes XSync .. yes XVideo . yes Session management . yes SQL drivers: DB2 .. no InterBase no MySQL no OCI .. no ODBC . yes (plugin) PostgreSQL ... no SQLite 2 . no SQLite ... yes (p
[Interest] Problem with XCB and OpenGL
Hi all, My application is exiting with the following error whenever I try to use OpenGL QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled My desktop is Ubuntu 12.04 (32 bit). I configured Qt 5.6.0 with the following options ./configure -qt-zlib -system-libpng -system-libjpeg -platform linux-g++-32 -fontconfig -qt-xcb -nomake examples -nomake tools This is part of the configure output (full output attached) OpenGL / OpenVG: EGL .. yes OpenGL ... desktop OpenVG ... no [...] QPA backends: DirectFB . no EGLFS yes EGLFS i.MX6 no EGLFS i.MX6 Wayland. no EGLFS EGLDevice no EGLFS GBM .. no EGLFS Mali . no EGLFS Raspberry Pi . no EGLFS X11 .. yes LinuxFB .. yes Mir client no XCB .. yes (bundled copy) EGL on X ... yes GLX no MIT-SHM yes Xcb-Xlib ... yes Xcursor yes (loaded at runtime) Xfixes . yes (loaded at runtime) Xi . no Xi2 yes Xinerama ... yes (loaded at runtime) Xrandr . yes (loaded at runtime) Xrender yes XKB yes XShape . yes XSync .. yes XVideo . yes I've googled a lot about this issue but I did not find any solution to it. Do you have any clues on how to fix this issue? Thanks in advance for your help, Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com Running configuration tests (phase 1)... Done running configuration tests. Creating qmake... Done. Running configuration tests (phase 2)... Done running configuration tests. Configure summary Build type:linux-g++-32 (i386, CPU features: none detected) Build options: Configuration .. accessibility accessibility-atspi-bridge audio-backend avx c++11 clock-gettime clock-monotonic compile_examples concurrent dbus egl eglfs egl_x11 enable_new_dtags evdev eventfd fontconfig full-config getaddrinfo getifaddrs harfbuzz iconv inotify ipv6ifname large-config largefile linuxfb medium-config minimal-config mremap nis opengl openssl pcre png posix_fallocate precompile_header qpa qpa reduce_exports reduce_relocations release rpath shared small-config sse2 sse3 sse4_1 sse4_2 ssse3 system-freetype system-jpeg system-png threadsafe-cloexec xcb xcb-plugin xcb-qt xcb-xlib xinput2 xkbcommon-qt xlib xrender zlib Build parts libs Mode ... release Using sanitizer(s).. none Using C++ standard . c++11 Using gold linker... no Using new DTAGS yes Using PCH .. yes Using LTCG . no Target compiler supports: SSE2/SSE3/SSSE3 .. yes/yes/yes SSE4.1/SSE4.2 yes/yes AVX/AVX2 . yes/no Qt modules and options: Qt D-Bus ... yes (loading dbus-1 at runtime) Qt Concurrent .. yes Qt GUI . yes Qt Widgets . yes Large File . yes QML debugging .. yes Use system proxies . no Support enabled for: Accessibility .. yes ALSA ... no CUPS ... no Evdev .. yes FontConfig . yes FreeType ... yes (system library) Glib ... no GStreamer .. no GTK theme .. no HarfBuzz ... yes (bundled copy) Iconv .. yes ICU no Image formats: GIF .. yes (plugin, using bundled copy) JPEG . yes (plugin, using system library) PNG .. yes (in QtGui, using system library) libinput no Logging backends: journald ... no syslog ... no mtdev .. no Networking: getaddrinfo .. yes getifaddrs ... yes IPv6 ifname .. yes libproxy.. no OpenSSL .. yes (loading libraries at run-time) NIS yes OpenGL / OpenVG: EGL .. yes OpenGL ... desktop OpenVG ... no PCRE ... yes (bundled copy) pkg-config . yes PulseAudio . no QPA backends: DirectFB . no EGLFS yes EGLFS i.MX6 no EGLFS i.MX6 Wayland. no EGLFS EGLDevice no EGLFS GBM .. no EGLFS Mali . no EGLFS Raspberry Pi . no EGLFS X11 .. yes LinuxFB .. yes Mir client no XCB .. yes (bu
Re: [Interest] Error when compiling Qt 5.5.0 beta for Max OS X 10.8
Il 6/18/2015 12:01 PM, Sorvig Morten ha scritto: >> On 18 Jun 2015, at 10:58, Calogero Mauceri wrote: >> >> >> Il 5/20/2015 12:39 PM, Sorvig Morten ha scritto: >>>> On 19 May 2015, at 10:50, Calogero Mauceri wrote: >>>> >>>> Hi all, >>>> >>>> I'm trying to compile Qt 5.5.0 beta for Mac OS X 10.8, on Mac OS X 10.10. >>>> qxctestlogger.mm:129:27: error: property 'description' not found on >>>> object of >>>>type 'id' >>>> [NSDate date].description.UTF8String); >>>> >>>> Is this a bug or am I doing something wrong? >>> It’s a bug! Fixing is in progress, see >>> https://codereview.qt-project.org/#/c/112440/ >>> >>> Morten >> It seems this fix was not included in the RC. I'm still getting the same >> error when compiling 5.5.0 RC for Mac OS X 10.8. > Looks like the fix was committed for the 5.5 branch after 5.5.0 was branched > off it. That means it will be released with Qt 5.5.1. > > Morten > ___ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest Ouch. Shouldn't the minimum OS X platform supported by Qt 5.5.0 be Mac OS X 10.8? If this does not get fixed it will not compile there (unless of course you don't manually patch it yourself). The fix is very simple, is there no way to bring it in current release branch? Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Error when compiling Qt 5.5.0 beta for Max OS X 10.8
Il 5/20/2015 12:39 PM, Sorvig Morten ha scritto: >> On 19 May 2015, at 10:50, Calogero Mauceri wrote: >> >> Hi all, >> >> I'm trying to compile Qt 5.5.0 beta for Mac OS X 10.8, on Mac OS X 10.10. >> qxctestlogger.mm:129:27: error: property 'description' not found on >> object of >>type 'id' >> [NSDate date].description.UTF8String); >> >> Is this a bug or am I doing something wrong? > > It’s a bug! Fixing is in progress, see > https://codereview.qt-project.org/#/c/112440/ > > Morten It seems this fix was not included in the RC. I'm still getting the same error when compiling 5.5.0 RC for Mac OS X 10.8. Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Is QLocalSocket reentrant?
Il 5/22/2015 2:35 PM, Calogero Mauceri ha scritto:
> Hi all,
>
> sorry if this is a stupid question, but I'm having some weird memory
> corruption problems when using QLocalSocket in multiple threads.
>
> I have a server process, accepting connections from client processes
> through a QLocalServer instance. Every time a new connection is accepted
> by the QLocalServer, the server launches a thread that communicates with
> the client through the QLocalSocket.
>
> The code I'm using to launch the threads in the server is something like
> this
>
> void LocalServer::newClientConnectionSlot()
> {
> QLocalSocket *localSocket = localServer->nextPendingConnection();
> if (localSocket) {
> QThread *thread= new QThread;
> MyWorker *worker = new MyWorker();
> worker ->moveToThread(thread);
>
> thread->start();
>
> localSocket->setParent(NULL);// remove local server parent
> in order to properly use the socket on another thread
> localSocket->moveToThread(thread);
> rpcPingReplyer->setLocalSocket(localSocket);
> rpcPingReplyer->startPingReplying();
> }
> }
>
> Each thread is using its own localSocket to communicate with the client.
>
> My question is, is it safe to use different instances of QLocalSocket
> from different threads without guarding those sockets? The documentation
> does not report QLocalSocket is reentrant. What does it imply? Should I
> guard all QLocalSocket instances with a global mutex before using them?
>
> Thanks in advance for your hints!
> Calogero
Sorry, the example I previously wrote was not fully correct.
Here is a better one
void LocalServer::newClientConnectionSlot()
{
QLocalSocket *localSocket = localServer->nextPendingConnection();
if (localSocket) {
QThread *thread= new QThread;
MyWorker *worker = new MyWorker();
worker->moveToThread(thread);
thread->start();
// move local socket to thread
localSocket->setParent(NULL);
localSocket->moveToThread(thread);
worker->setLocalSocket(localSocket);
// start communicating with client
worker->startCommunicate();
}
}
--
Calogero Mauceri
Software Engineer
Applied Coherent Technology Corporation (ACT)
www.actgate.com
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Is QLocalSocket reentrant?
Hi all,
sorry if this is a stupid question, but I'm having some weird memory
corruption problems when using QLocalSocket in multiple threads.
I have a server process, accepting connections from client processes
through a QLocalServer instance. Every time a new connection is accepted
by the QLocalServer, the server launches a thread that communicates with
the client through the QLocalSocket.
The code I'm using to launch the threads in the server is something like
this
void LocalServer::newClientConnectionSlot()
{
QLocalSocket *localSocket = localServer->nextPendingConnection();
if (localSocket) {
QThread *thread= new QThread;
MyWorker *worker = new MyWorker();
worker ->moveToThread(thread);
thread->start();
localSocket->setParent(NULL);// remove local server parent
in order to properly use the socket on another thread
localSocket->moveToThread(thread);
rpcPingReplyer->setLocalSocket(localSocket);
rpcPingReplyer->startPingReplying();
}
}
Each thread is using its own localSocket to communicate with the client.
My question is, is it safe to use different instances of QLocalSocket
from different threads without guarding those sockets? The documentation
does not report QLocalSocket is reentrant. What does it imply? Should I
guard all QLocalSocket instances with a global mutex before using them?
Thanks in advance for your hints!
Calogero
--
Calogero Mauceri
Software Engineer
Applied Coherent Technology Corporation (ACT)
www.actgate.com
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Error when compiling Qt 5.5.0 beta for Max OS X 10.8
Il 5/20/2015 12:39 PM, Sorvig Morten ha scritto: >> On 19 May 2015, at 10:50, Calogero Mauceri wrote: >> >> Hi all, >> >> I'm trying to compile Qt 5.5.0 beta for Mac OS X 10.8, on Mac OS X 10.10. >> qxctestlogger.mm:129:27: error: property 'description' not found on >> object of >>type 'id' >> [NSDate date].description.UTF8String); >> >> Is this a bug or am I doing something wrong? > > It’s a bug! Fixing is in progress, see > https://codereview.qt-project.org/#/c/112440/ > > Morten Great, thanks! -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Error when compiling Qt 5.5.0 beta for Max OS X 10.8
If I compile with the same options but using Mac OS X 10.9 SDK (-sdk macosx10.9) then it completes without any problems. It must be something related to 10.8 SDK. Calogero Il 5/19/2015 4:15 PM, Liang Qi ha scritto: 5.5 Beta does support 10.8, at least CI still covers it. The issue must be related with "-platform macx-clang-32", that's unsupported for a while. Regards, Liang On 19 May 2015 at 11:58, Tim Blechmann <mailto:t...@klingt.org>> wrote: > Is this a bug or am I doing something wrong? qt-5.5 does not compile on 10.8 out of the box. it is probably going to be fixed before the release (afaict, 10.8 is still supported) tim -- http://www.qiliang.net ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Error when compiling Qt 5.5.0 beta for Max OS X 10.8
Hi all, I'm trying to compile Qt 5.5.0 beta for Mac OS X 10.8, on Mac OS X 10.10. This is the configuration line I'm using. ./configure -prefix /Developer/libs/qt-5.5.0_beta -qt-zlib -qt-libpng -qt-libjpeg -nomake tests -nomake examples -platform macx-clang-32 -opensource -confirm-license -sdk macosx10.8 The compilation stops with the following error [...] cd testlib/ && ( test -e Makefile || /Users/mauceri/work/dev/libs/qt-everywhere- opensource-src-5.5.0-beta/qtbase/bin/qmake /Users/mauceri/work/dev/libs/qt-every where-opensource-src-5.5.0-beta/qtbase/src/testlib/testlib.pro -o Makefile ) && /Applications/Xcode.app/Contents/Developer/usr/bin/make -f Makefile /Applications/Xcode.app/Contents/Developer/usr/bin/make -f Makefile.Debug all /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/u sr/bin/clang -c -pipe -arch i386 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk -mmacosx-version-min=10.7 -F/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/D eveloper/Library/Frameworks -g -fvisibility=hidden -fvisibility-inlines-hidden - std=c++11 -stdlib=libc++ -Wall -W -DQT_NO_MTDEV -DQT_NO_LIBUDEV -DQT_NO_EVDEV -DQT_NO_TSLIB -DQT_NO_LIBINPUT -DQT_NO_CAST_TO_ASCII -DQT_NO_CAST_FROM_ASCII -DQT_ NO_DATASTREAM -DHAVE_XCTEST -DQT_BUILD_TESTLIB_LIB -DQT_BUILDING_QT -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x05 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_CORE_LIB -I. -I../../include -I../../include/QtTest -I../../include/QtTest/5.5.0 -I../../include/QtTest/5.5.0/QtTest -I../../lib/QtCore.framework/Headers -I../../lib/QtCore.framework/Headers/5.5.0 -I../../lib/QtCore.framework/Headers/5.5.0/QtCore -I.moc/debug -I../../mkspecs/macx-clang-32 -F/Users/mauceri/work/dev/libs/qt-everywhere-opensource-src-5.5.0-beta/qtbase/lib qxctestlogger.mm -o .obj/debug/qxctestlogger.o qxctestlogger.mm:129:27: error: property 'description' not found on object of type 'id' [NSDate date].description.UTF8String); ^ qxctestlogger.mm:250:17: warning: property 'testObjectName' requires method 'testObjectName' to be defined - use @synthesize, @dynamic or provide a method implementation in this class implementation [-Wobjc-property-implementation] @implementation QtTestLibTest ^ qxctestlogger.mm:75:41: note: property declared here @property (nonatomic, retain) NSString* testObjectName; ^ qxctestlogger.mm:250:17: warning: property 'testObjectName' requires method 'setTestObjectName:' to be defined - use @synthesize, @dynamic or provide a method implementation in this class implementation [-Wobjc-property-implementation] @implementation QtTestLibTest ^ qxctestlogger.mm:75:41: note: property declared here @property (nonatomic, retain) NSString* testObjectName; ^ qxctestlogger.mm:250:17: warning: property 'testFunctionName' requires method 'testFunctionName' to be defined - use @synthesize, @dynamic or provide a method implementation in this class implementation [-Wobjc-property-implementation] @implementation QtTestLibTest ^ qxctestlogger.mm:76:41: note: property declared here @property (nonatomic, retain) NSString* testFunctionName; ^ qxctestlogger.mm:250:17: warning: property 'testFunctionName' requires method 'setTestFunctionName:' to be defined - use @synthesize, @dynamic or provide a method implementation in this class implementation [-Wobjc-property-implementation] @implementation QtTestLibTest ^ qxctestlogger.mm:76:41: note: property declared here @property (nonatomic, retain) NSString* testFunctionName; ^ 4 warnings and 1 error generated. make[4]: *** [.obj/debug/qxctestlogger.o] Error 1 make[3]: *** [debug-all] Error 2 make[2]: *** [sub-testlib-make_first] Error 2 make[1]: *** [sub-src-make_first] Error 2 make: *** [module-qtbase-make_first] Error 2 Is this a bug or am I doing something wrong? Thanks, Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Bad application rendering on Remote Desktop
Interesting. Well in that case I think I'll need to modify my code to
use ANGLE, as you are suggesting.
That'll require quite an effort so for the time being I'll stay with
QGLWidget.
Thanks a lot for your hints.
Calogero
Il 4/29/2015 11:31 AM, Agocs Laszlo ha scritto:
> Hi Calogero,
>
> When adding a QOpenGLWidget or QQuickWidget into a widget hierarchy in a
> window, the entire window will be rendered differently: it is switched
> over to OpenGL-based compositing. This involves using OpenGL features not
> present in OpenGL 1.1.
>
> If you avoid adding (parenting) the QOpenGLWidget into the window, you
> will find that it becomes functional with GL 1.1 again. This is because
> you then use the traditional path without relying on GL.
>
> Note also that switching back and forth between the rendering models is
> not fully in place: making a QOpenGLWidget invisible or even removing it
> may not have any effect on how the window is rendered afterwards.
>
> Best regards,
> Laszlo
>
> On 29/04/15 10:26, "Calogero Mauceri" wrote:
>
>> Thanks Laszlo for your explanation.
>>
>> I still do not understand why the whole application is not properly
>> rendered, not only the OpenGL stuff.
>> The application we are developing is a quite complex one, having
>> multiple windows, and the OpenGL one is a small part of it.
>> Simply including just one instance of QOpenGLWidget in the application
>> causes the bad rendering, even if that widget is not even shown.
>>
>> Calogero
>>
>> Il 4/28/2015 8:54 PM, Agocs Laszlo ha scritto:
>>> Because when using remote desktop you are suddenly left with OpenGL 1.1
>>> (ouch) and so QOpenGLWidget and friends that rely on OpenGL 2.0 features
>>> (like framebuffer objects) cease to function.
>>>
>>> The solution is to rely on ANGLE or a software rasterizer (like Mesa
>>> llvmpipe) in this case.
>>>
>>> When using the dynamic OpenGL builds, the fallback to ANGLE will happen
>>> automatically when using remote desktop. I assume you are using the
>>> -opengl packages from 5.4.1 and that's why this is not in place. With
>>> 5.5
>>> this won't be an issue since desktop OpenGL packages will not be
>>> provided
>>> anymore.
>>>
>>> Best regards,
>>> Laszlo
>>>
>>>
>>> On 27/04/15 17:17, "Calogero Mauceri" wrote:
>>>
>>>> Hi all,
>>>>
>>>> switching my application from using QGLWidget to the new QOpenGLWidget
>>>> I
>>>> noticed a very weird problem when using the application through Remote
>>>> Desktop on Windows. The whole application is fully black, it is not
>>>> properly rendered, not only the QOpenGLWidget, but also the other
>>>> widgets in the application.
>>>>
>>>> I created a very simple example demonstrating my issue.
>>>>
>>>> MyWidget::MyWidget(QWidget* parent, Qt::WindowFlags fl)
>>>> : QWidget(parent, fl)
>>>> {
>>>> QVBoxLayout *vBoxLayout = new QVBoxLayout(this);
>>>> QHBoxLayout *hLayout = new QHBoxLayout;
>>>>
>>>> QLabel *myLabel = new QLabel("Test", this);
>>>> QPushButton *myButton = new QPushButton("Test", this);
>>>> hLayout->addWidget(myLabel);
>>>> hLayout->addWidget(myButton);
>>>>
>>>> QGLWidget *myOPenGLWidget = new QGLWidget(this);
>>>> // QOpenGLWidget *myOPenGLWidget = new QOpenGLWidget(this);// this
>>>> causes bad app rendering on Remote Desktop
>>>>
>>>> vBoxLayout->addItem(hLayout);
>>>> vBoxLayout->addWidget(myOPenGLWidget);
>>>> }
>>>>
>>>> When I use QGLWidget the widgets are properly rendered, as you can see
>>>> in the attached image. When I replace the QGLWidget with its counter
>>>> part QOpenGLWidget then the whole app is fully black when launched
>>>> through remote desktop (on Windows), no widget is rendered (see other
>>>> image attached). If I run the application on my local machine, then
>>>> everything is properly rendered.
>>>>
>>>> Am I doing something wrong? Or is this a limit/bug in Qt (I'm using
>>>> latest Qt version, 5.4.1)?
>>>>
>>>> This is my main
>>>>
>>>> int main( int argc, char *argv[] )
>>>> {
>>>> QApplication appMain(argc,
Re: [Interest] Bad application rendering on Remote Desktop
Thanks Laszlo for your explanation.
I still do not understand why the whole application is not properly
rendered, not only the OpenGL stuff.
The application we are developing is a quite complex one, having
multiple windows, and the OpenGL one is a small part of it.
Simply including just one instance of QOpenGLWidget in the application
causes the bad rendering, even if that widget is not even shown.
Calogero
Il 4/28/2015 8:54 PM, Agocs Laszlo ha scritto:
> Because when using remote desktop you are suddenly left with OpenGL 1.1
> (ouch) and so QOpenGLWidget and friends that rely on OpenGL 2.0 features
> (like framebuffer objects) cease to function.
>
> The solution is to rely on ANGLE or a software rasterizer (like Mesa
> llvmpipe) in this case.
>
> When using the dynamic OpenGL builds, the fallback to ANGLE will happen
> automatically when using remote desktop. I assume you are using the
> -opengl packages from 5.4.1 and that's why this is not in place. With 5.5
> this won't be an issue since desktop OpenGL packages will not be provided
> anymore.
>
> Best regards,
> Laszlo
>
>
> On 27/04/15 17:17, "Calogero Mauceri" wrote:
>
>> Hi all,
>>
>> switching my application from using QGLWidget to the new QOpenGLWidget I
>> noticed a very weird problem when using the application through Remote
>> Desktop on Windows. The whole application is fully black, it is not
>> properly rendered, not only the QOpenGLWidget, but also the other
>> widgets in the application.
>>
>> I created a very simple example demonstrating my issue.
>>
>> MyWidget::MyWidget(QWidget* parent, Qt::WindowFlags fl)
>> : QWidget(parent, fl)
>> {
>> QVBoxLayout *vBoxLayout = new QVBoxLayout(this);
>> QHBoxLayout *hLayout = new QHBoxLayout;
>>
>> QLabel *myLabel = new QLabel("Test", this);
>> QPushButton *myButton = new QPushButton("Test", this);
>> hLayout->addWidget(myLabel);
>> hLayout->addWidget(myButton);
>>
>> QGLWidget *myOPenGLWidget = new QGLWidget(this);
>> // QOpenGLWidget *myOPenGLWidget = new QOpenGLWidget(this);// this
>> causes bad app rendering on Remote Desktop
>>
>> vBoxLayout->addItem(hLayout);
>> vBoxLayout->addWidget(myOPenGLWidget);
>> }
>>
>> When I use QGLWidget the widgets are properly rendered, as you can see
>> in the attached image. When I replace the QGLWidget with its counter
>> part QOpenGLWidget then the whole app is fully black when launched
>> through remote desktop (on Windows), no widget is rendered (see other
>> image attached). If I run the application on my local machine, then
>> everything is properly rendered.
>>
>> Am I doing something wrong? Or is this a limit/bug in Qt (I'm using
>> latest Qt version, 5.4.1)?
>>
>> This is my main
>>
>> int main( int argc, char *argv[] )
>> {
>> QApplication appMain(argc, argv);
>>
>> MyWidget *mainWin = new MyWidget;
>> mainWin->show();
>>
>> return appMain.exec();
>> }
>>
>> I enabled qt.qpa.gl debugging and this is the output of the application
>> in the two cases.
>>
>> Output in case of QGLWidget enabled:
>> [...]
>> qt.qpa.gl: QWindowsIntegration::createPlatformOpenGLContext
>> QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 1,
>> redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize
>> -1, stencilBufferSize 1, samples -1, swapBehavior 2, swapInterval -1,
>> profile 0)
>> qt.qpa.gl: Qt: Using WGL and OpenGL from "opengl32.dll"
>> qt.qpa.gl: QOpenGLStaticContext::create OpenGL: "Microsoft
>> Corporation","GDI Generic" default ContextFormat: v1.1 profile: 0
>> options: QFlags(0x4)
>> Extensions: 3
>> qt.qpa.gl: QWindowsGLContext::QWindowsGLContext 0x6be850 GDI
>> requested: QSurfaceFormat(version 2.0, options QFlags(),
>> depthBufferSize 1, redBufferSize -1, greenBufferSize -1, blueBufferSize
>> -1, alphaBufferSize -1, stencilBufferSize 1, samples -1, swapBehavior 2,
>> swapInterval -1, profile 0)
>> obtained # 8 GDI QSurfaceFormat(version 1.1, options QFlags(0x4),
>> depthBufferSize 16, redBufferSize 8, greenBufferSize 8, blueBufferSize
>> 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior 2,
>> swapInterval 1, profile 0)
>> PIXELFORMATDESCRIPTOR dwFlags=0x465 PFD_DRAW_TO_WINDOW
>> PFD_SUPPORT_OPENGL PFD_GENERIC_FORMAT PFD_DOUBLEBUFFER iPixelType=0
>> cColorBits=32 cRedBits=8 cRedShift=16 cGreenBits=8 cGreenShif
[Interest] Bad application rendering on Remote Desktop
00 QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader bool __thiscall QOpenGLTextureBlitter::create(void) Could not link shader program: "" QOpenGLBuffer::bind(): buffer not created QOpenGLBuffer::release(): buffer not created QOpenGLBuffer::bind(): buffer not created QOpenGLBuffer::release(): buffer not created [...] Thanks in advance for your help! Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How to force scroll bars always visible on Mac
Bill thank you very much! You made my day ;). Calogero Il 4/8/2015 3:22 PM, Bill Jones ha scritto: > Calogero, > > There is a way to do this, you need to set a QProxyStyle on the scrollbar’s > whose behavior you want to change and over-ride the > QStyle::SH_ScrollBar_Transient setting. > > Bill > > > > On Apr 8, 2015, at 3:49 AM, Calogero Mauceri wrote: > >> Hi John, >> >> Unfortunately even if I hover where the scroll bars *should* be, they never >> show up, neither on other mac applications. >> I know I can change that behavior from the machine settings, but that will >> solve the problem on my machine, my application users will still have the >> problem. >> >> I was just wondering if Qt exposes some functionalities for forcing the >> scroll bars to be always visible. I tried to change the ScrollBarPolicy for >> vertical and horizontal scrollbars to be Qt::ScrollBarAlwaysOn, but that did >> not change anything, the scroll bars all always hidden. >> >> Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How to force scroll bars always visible on Mac
Hi John,
Unfortunately even if I hover where the scroll bars *should* be, they
never show up, neither on other mac applications.
I know I can change that behavior from the machine settings, but that
will solve the problem on my machine, my application users will still
have the problem.
I was just wondering if Qt exposes some functionalities for forcing the
scroll bars to be always visible. I tried to change the ScrollBarPolicy
for vertical and horizontal scrollbars to be |Qt::ScrollBarAlwaysOn|,
but that did not change anything, the scroll bars all always hidden.
Calogero
Il 4/7/2015 6:03 PM, John Weeks ha scritto:
Whether you agree with the design or not, that's the way it is. Presumably, if
you hover where the scroll bars *should* be, they should show up if they are
needed. As a 25-year Macintosh user I hate it!
The behavior is controlled by the user via the General control panel. There are three
radio buttons for "Show scroll bars:" Automatically (what I described), When
scrolling (I think that's like when you drag with two fingers), and Always. Being an
old-time Mac user who believes in the old Mac HIG that said we shouldn't have hidden UI
elements, I have mine set to Always.
-John Weeks
On 07 Apr 2015, at 8:01 am, Calogero Mauceri wrote:
Hi all,
I have a tricky problem on Mac OS X 10.10 related to scrolling content
on a QGraphicsView.
I have a QGraphicsView where I reimplemented the wheelEvent to zoom
in/out the content of the view. The only way I have for scrolling the
content is clicking and dragging the scroll bars. Actually on Mac OS X
10.10 scroll bars are hidden by default and shown only when the user
scrolls the area through mouse or trackpad. Having reimplemented the
default behavior the scrollbars in my QGraphicsView are never shown.
Is there any Qt way to force the scroll bars to be always visible? Do
you have any other suggestion on how to fix this problem?
Thanks,
Calogero
--
Calogero Mauceri
Software Engineer
Applied Coherent Technology Corporation (ACT)
www.actgate.com
___
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
--
Calogero Mauceri
Software Engineer
Applied Coherent Technology Corporation (ACT)
www.actgate.com
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
[Interest] How to force scroll bars always visible on Mac
Hi all, I have a tricky problem on Mac OS X 10.10 related to scrolling content on a QGraphicsView. I have a QGraphicsView where I reimplemented the wheelEvent to zoom in/out the content of the view. The only way I have for scrolling the content is clicking and dragging the scroll bars. Actually on Mac OS X 10.10 scroll bars are hidden by default and shown only when the user scrolls the area through mouse or trackpad. Having reimplemented the default behavior the scrollbars in my QGraphicsView are never shown. Is there any Qt way to force the scroll bars to be always visible? Do you have any other suggestion on how to fix this problem? Thanks, Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] string conversion to longlong error
On 9/3/2014 6:11 PM, Rogers Nate wrote:
> On 09/03/2014 11:53 AM, Calogero Mauceri wrote:
>> Hi all,
>>
>> I'm doing something really simple, but which is driving me crazy.
>>
>> I'm reading a string from a file and converting it to a long long
>> integer, but the conversion fails.
>> The code I'm running is as simple as this
>>
>> // this string is read from a file
>> QString str("18446744073709551615");
>> bool ok;
>> qint64 value = str.toLongLong(&ok);// Error
>>
>> the number should be representable in 64 bit. Am I doing something wrong?
>>
>> More hints, if I convert the number to unsigned long long integer then
>> it works
>>
>>bool ok;
>>quint64 value = str.toULongLong(&ok);// OK
>>
>> Similarly initializing the long long from the literal value is failing too
>>
>> Q_INT64_C(18446744073709551615) ; // Error, returns -1
>> Q_UINT64_C(18446744073709551615);// OK
>>
>> Thanks for your help!
>> Calogero
>>
> 18446744073709551615 is too big to fit into a long long. It is actually the
> biggest number you can have a unsigned long long. A long long can't fit the
> same size number because it has to use one bit to hold the sign. The maximum
> number you can fit in a long long is 9223372036854775807.
>
Nate,
thanks for your reply, now I see the problem.
Calogero
--
Calogero Mauceri
Software Engineer
Applied Coherent Technology Corporation (ACT)
www.actgate.com
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
[Interest] string conversion to longlong error
Hi all,
I'm doing something really simple, but which is driving me crazy.
I'm reading a string from a file and converting it to a long long
integer, but the conversion fails.
The code I'm running is as simple as this
// this string is read from a file
QString str("18446744073709551615");
bool ok;
qint64 value = str.toLongLong(&ok);// Error
the number should be representable in 64 bit. Am I doing something wrong?
More hints, if I convert the number to unsigned long long integer then
it works
bool ok;
quint64 value = str.toULongLong(&ok);// OK
Similarly initializing the long long from the literal value is failing too
Q_INT64_C(18446744073709551615) ; // Error, returns -1
Q_UINT64_C(18446744073709551615);// OK
Thanks for your help!
Calogero
--
Calogero Mauceri
Software Engineer
Applied Coherent Technology Corporation (ACT)
www.actgate.com
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
[Interest] QGraphicsView widgets have transparent background
Hi all,
I'm creating a widget having as parent a QGraphicsView. When the widget
is shown it is drawn with a transparent background, as you can see in
the following link
http://tinypic.com/r/2ildg7r/5
Here is the code I use to create the widget
// initialize the view
scene = new QGraphicsScene(this);
scene->setBackgroundBrush(Qt::green);
gvView = new QGraphicsView(parent);
gvView->setScene(scene);
// initialize the widget
MyWidget *myWidget = new MyWidget(gvView);
myWidget->setLabelText("Test Widget");
myWidget->show();
MyWidget is a simple widget with a label and a button.
creating the widget with the Qt:Dialog flag, I have this result (the
background is visible)
http://tinypic.com/r/2ylwg7r/5
What am I doing wrong? How can I force the widget to have a background
color?
Thanks in advance for your help,
Calogero
--
Calogero Mauceri
Software Engineer
Applied Coherent Technology Corporation (ACT)
www.actgate.com
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Relashionship between time_t and QDateTime
On 8/27/2013 11:01 PM, Constantin Makshin wrote: The original Calogero's message mentioned a file from December 2007, a date outside of DST (unless there's a country that uses DST during winter). Now it's August, so the DST is active and during "UTC -> local time" conversion Windows adds that 1 hour Calogero is seeing. DST gets incorrectly applied because it's active at the moment of conversion, although it wasn't used at the moment the original timestamp represents. I bet that the problem will go away when DST ends [again]. :) I think Constantin's analysis is correct. Just for your information, I'm using Qt 4.8.4. The machine where I noticed the problem is running Microsoft Windows Server 2003. The Time Zone is set to (GMT-05:00) Eastern Time (US & Canada), in DST currently. Let me know if you need any additional information Calogero On 08/27/2013 11:42 PM, Thiago Macieira wrote: On terça-feira, 27 de agosto de 2013 22:59:44, Constantin Makshin wrote: Windows can store information about daylight saving transitions for past years, but always uses one for the current year. And since daylight saving transition dates and time tend to slightly drift from year to year, there's absolutely no guarantees of getting correct time conversion results; in general case 1-hour error is nearly inevitable. If you're on Windows, either calculate and apply DST yourself or forget about correct "UTC <-> local time" conversions. This is not about the corner case of a file that was created in the hour of the transition, or even in the week that shifted between non-DST in one year to DST in another (or vice-versa). >From what I understand, we're talking about a file created in DST and checked outside of DST (or vice-versa) in the *same* *year*. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Relashionship between time_t and QDateTime
On 8/26/2013 7:30 PM, Thiago Macieira wrote: > On segunda-feira, 26 de agosto de 2013 17:42:58, Calogero Mauceri wrote: >> QDateTime myDateTime = QDateTime::fromTime_t(f_mtime); >> >> The date time printed doing a myDateTime.toString() is >> >> Wed Dec 5 12:36:18 2007 >> >> >> Retrieving the last modified information using QFileInfo, the result is >> different >> >> QFileInfo fi(filepath); >> QDateTime myDateTime = fi.lastModified(); >> >> I get this result >> >> Wed Dec 5 11:36:18 2007 >> >> That is there is one hour difference. I guess the difference is due to >> the daylight saving management, >> but I can not understand how that management is performed. >> >> Note: if I look at the file properties on Windows dialog, the last >> modified time is shown as >> >> Wed Dec 5 12:36:18 2007 > Ah, Windows... > > The problem might be simply a matter of timezones. The timestamps on files on > Windows are not stored with time_t, but with some Windows-specific data. We > get > a FILETIME back from Win32. > > Anyway, up until Qt 5.2, you cannot trust the output of a QDateTime with > qDebug since it does not include the timezone. You have to ensure that the > dates you're comparing by text are in the same timezone: > > qDebug() << dt.toUTC(); Thanks for your reply. Unfortunately the problem is still there even if I force a toUTC() conversion for both QDateTime, either the one initialized from time_t or the one returned by QFileInfo :/. Similarly QDateTime dtFromTime_t = QDateTime::fromTime_t(mtime).toUTC(); QDateTime dtFromFileInfo = fi.lastModified().toUTC(); int sec = ABS(dtFromTime.secsTo(dtFromFileInfo)); // sec returned is 3600 Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Relashionship between time_t and QDateTime
Hi all, I'm facing the following problem when initializing a QDateTime with time_t value. I get the last modified timestamp of a file as time_t value ... time_t mtime; struct stat statbuf; fstat(fd, &statbuf); mtime = statbuf.st_mtime; ... Then I use that mtime value to initialize a QDateTime as follows: QDateTime myDateTime = QDateTime::fromTime_t(f_mtime); The date time printed doing a myDateTime.toString() is Wed Dec 5 12:36:18 2007 Retrieving the last modified information using QFileInfo, the result is different QFileInfo fi(filepath); QDateTime myDateTime = fi.lastModified(); I get this result Wed Dec 5 11:36:18 2007 That is there is one hour difference. I guess the difference is due to the daylight saving management, but I can not understand how that management is performed. Note: if I look at the file properties on Windows dialog, the last modified time is shown as Wed Dec 5 12:36:18 2007 Thanks in advance for your help. Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] How to know QSharedMemory maximum system allowed size
Hi all, I'm using QSharedMemory to share data between different processes. I found out that there is a limit to the maximum size a shared memory segment can be. On Mac OS for example the QSharedMemory::create returned an error like "system-imposed size restrictions". Is there a way programmatically to know which is the maximum size the system allows for the QSharedMemory, in order to adopt proper data splitting policies depending on it? Thank you very much for your help. Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt5 and Georeferenced Images
Qt does not support geo images. In our software we leverage in a combination of GDAL and proj4 to read/reproject geo data and use Qt to view/navigate the images. Hope that helps. Best Regards, Calogero Il 18/04/2013 15.50, Miller, Doug ha scritto: > Does Qt5 have any inherent capabilities that could be leveraged in making > applications like a GIS viewer or a GPS tracker? I'm thinking about > stand-alone applications that do not utilize on-line services. Or do > applications have to integrate with tool sets like GDAL? Any ideas would be > appreciated. > > > > Thanks. > ___ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Program runs only on four core processors.... sometimes.
In your tests try to double check also the status of the machine TCP/UDP ports. On Windows the commad should be netstat -an It helped me debugging an application I wrote that was consuming all the ports available in the machine (opening and closing consecutively a huge amount of TCP connections). Hope that helps, Calogero Il 21/03/2013 8.48, Till Oliver Knoll ha scritto: > Am 20.03.2013 um 23:00 schrieb Guido Seifert : > >> Hi, >> I have here a strange problem. Probably not 100% ontopic for this list. But >> it is a Qt program. :-) >> >> My problem: I have three programs, which exchange data with a fourth program >> via tcp and udp. On my i7 and i5 with four cores it runs perfectly. It also >> runs perfectly on my partner's machines. Now I gave it to a few testers... >> and it was pure disaster. Bugs I have never seen before. From the >> description it seems to be some kind of deadlock. The main program just >> freezes. > Now we assume it is a deadlock caused by some race conditions for some > network (socket?) resources. But maye it is simply because the data is > sometimes wrong? Imagine one service would send image data "worth 4 > terrabytes" (because the "content size field" was wrongly set, or the > height/width fields), so what would your main program do? Would it try to > really create a QImage that large and hence be busy allocating virtual memory? > > That would be visible off course by its memory consumption which would grow > and grow. > > Off course my guess totally does not explain why it would (seem to) work on > some machines, and not on others (but that /could/ be a pure coincidence > which would wrongly lead us to believe it must be a threading/deadlock > problem). > > Cheers, >Oliver > _______ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Buttons on QGLWidget not shown on Mac OSX 10.8 (Mountain Lion)
John, Thanks for your hint, that can be the cause of the problem, even if it is a big limitation. Calogero Il 14/12/2012 19.50, John Weeks ha scritto: On 14-Dec-2012, at 10:26 AM, Calogero Mauceri wrote: The implementation is working greatly on Mac OSX 10.6 (from where I took the screen shot), but the button is not shown at all on Mac OSX 10.8. Actually the button is there but it seems completely transparent, I can click on it and the slot it is connected to is called. The same implementation works like a charm on Windows and linux too. Probably the problem is related to this statement in the QGLWidget documentation: On Mac OS X, when Qt is built with Cocoa support, a QGLWidget can't have any sibling widgets placed ontop of itself. This is due to limitations in the Cocoa API and is not supported by Apple. -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QGraphicsView widget vs opengl viewport
Il 27/11/2012 16.24, Samuel Rødal ha scritto: > On 11/27/2012 03:36 PM, Calogero Mauceri wrote: >> Hi, >> >> In my application I have a QGrapricsScene with a big amount of polygon >> items in it (more than 50,000 QGraphicsPolygonItem). >> >> I found out in the documentation that it is possible to set a QGLWidget >> as the viewport of the QGraphicsView. >> >> "By default, QGraphicsView provides a regularQWidget >> <http://qt-project.org/doc/qt-4.8/qwidget.html>for the viewport widget. >> You can access this widget by callingviewport >> <http://qt-project.org/doc/qt-4.8/qabstractscrollarea.html#viewport>(), >> or you can replace it by callingsetViewport >> <http://qt-project.org/doc/qt-4.8/qabstractscrollarea.html#setViewport>(). >> To render using OpenGL, simply call setViewport(newQGLWidget >> <http://qt-project.org/doc/qt-4.8/qglwidget.html>)." >> >> As far as I understand that should work out of the box, without any >> additional code. The system should use automatically opengl rendering >> from now on. >> My question is, can my QGraphicsScene benefit of the OpenGL rendering? >> Do you think I should always enable it? Are there some cases where the >> classic widget viewport can work better? >> Is the QGraphicsScene OpenGL rendering well supported on multiple >> platforms (Win, linux, Mac)? >> >> I'm using Qt 4.8.3. >> >> Thanks in advance for your advice, >> Calogero > Performance wise you can get quite large benefits from using a QGLWidget > viewport. Quality wise the rendered output might look slightly worse, > with lower antialiasing quality and less precise rounding of lines and > other primitives. > > It depends on whether you find the rendered output acceptable for use case. > > -- > Samuel If it is just a matter of performace vs quality, then I'll choose the OpenGL rendering. Currently I'm even disabling the antialising in the qgraphicsview trying to speed up the rendering a little bit view->setOptimizationFlags(QGraphicsView::DontAdjustForAntialiasing); Thank you very much for your hint! Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] QGraphicsView widget vs opengl viewport
Hi, In my application I have a QGrapricsScene with a big amount of polygon items in it (more than 50,000 QGraphicsPolygonItem). I found out in the documentation that it is possible to set a QGLWidget as the viewport of the QGraphicsView. "By default, QGraphicsView provides a regularQWidget <http://qt-project.org/doc/qt-4.8/qwidget.html>for the viewport widget. You can access this widget by callingviewport <http://qt-project.org/doc/qt-4.8/qabstractscrollarea.html#viewport>(), or you can replace it by callingsetViewport <http://qt-project.org/doc/qt-4.8/qabstractscrollarea.html#setViewport>(). To render using OpenGL, simply call setViewport(newQGLWidget <http://qt-project.org/doc/qt-4.8/qglwidget.html>)." As far as I understand that should work out of the box, without any additional code. The system should use automatically opengl rendering from now on. My question is, can my QGraphicsScene benefit of the OpenGL rendering? Do you think I should always enable it? Are there some cases where the classic widget viewport can work better? Is the QGraphicsScene OpenGL rendering well supported on multiple platforms (Win, linux, Mac)? I'm using Qt 4.8.3. Thanks in advance for your advice, Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] How to clear the result in a QFuture/QFutureWatcher
Hi list,
I have a QFuture and QFutureWatcher I'm using to run asynchronously a
heavy operation.
My QFutureWatcher is a member of my class and every time a new
computation needs to be done it is initialized with a new QFuture. When
the QFutureWatcher finishes I read the result.
After I've used the result I'd like to clear the content of the
QFutureWatcher, but I did not find any method in QFutureWatcher to do
that. Which is the way to clear the QFutureWatcher result?
This is an example of what I'm doing
class MyClass{
QFutureWatcher myWatcher;
}
void MyClass::startOp() {
myWatcher.setFuture( QtConcurrent::run(&heavyOp) );
}
void MyClass::opFinished(){
MyRes res = myWatcher.result();
// how do I clear the result in myWatcher?
}
Thanks in advance for your help,
Calogero
--
Calogero Mauceri
Software Engineer
Applied Coherent Technology Corporation (ACT)
www.actgate.com
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Modeless dialog on Mac are not kept on top
Hi, I noticed on the Mac version of my application, that modeless dialogs are not kept on top when the user clicks on the main window application. The dialogs "disappear" behind the application main window. This problem is happening only on Mac, not on Windows or Linux (Gnome). I noticed this problem after upgrading my application from Qt 4.6.3 to the latest version (Qt 4.8.4). Is it a bug or is there a way to keep the dialog on top of the application main window? I can not create the dialog with Qt::Tool flag (that would cause the dialog toolbar to be different than a normal dialog toolbar) nor I can use the Qt::WindowStaysOnTopHint flag (that would cause the dialog to be on top of any window opened in the system, also the ones of other applications). Thanks in advance for your help, Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How to know bindTexture failure
Il 08/10/2012 12.33, Samuel Rødal ha scritto: > On 10/08/2012 11:01 AM, Calogero Mauceri wrote: >> Il 05/10/2012 17.21, Calogero Mauceri ha scritto: >>> Il 05/10/2012 17.04, Samuel Rødal ha scritto: >>>> On 10/05/2012 04:46 PM, Calogero Mauceri wrote: >>>>> Hi, >>>>> >>>>> is there a way to know programmatically whether the >>>>> QGLWidget::bindTexture function fails? >>>>> Sometime my bindTexture fails, I can see in the log file there is a line >>>>> reporting the binding failure: >>>>> >>>>> texture upload failed, error code 0x500, enum: 3553 (de1) >>>> Hmm, looks like the error reporting is a bit lacking. If you have your >>>> own build of Qt you can uncomment the line that says #define >>>> QGL_BIND_TEXTURE_DEBUG in qgl.cpp to get more detailed debug output from >>>> the bind function. >>> Thanks Samuel for your reply. >>> We do have our own build of Qt, but I really would avoid to change them, >>> it would be very difficult for us to keep our changes in sync with the >>> new Qt distributions. >>> >>>>> but the bindTexture returns a valid texture id (> 0) and the >>>>> glGetError() returns 0 (no error). >>>>> How do I know the binding has failed from my code? >>>> Yeah, glGetError() won't return an error since it clears the error state >>>> when it's called from within bindTexture(). >>>> >>>> Btw, which OS and Qt version are you using? >>> I'm using Qt 4.7.3 on Windows, Linux and Mac. >>> I double checked the bindTexture source code on Qt 4.8 and there does >>> not seem to be a different error handling than in 4.7 version :( >>> >> So anyone can confirm that there is no way to know whether the >> QGLWidget::bindTexture has failed? >> If it is no, it seems to me a function design problem. > Yep, maybe you could file a bug about that? > I just submitted a bug report https://bugreports.qt-project.org/browse/QTBUG-27481 Regards, Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How to know bindTexture failure
Il 08/10/2012 12.34, Samuel Rødal ha scritto: > On 10/05/2012 05:21 PM, Calogero Mauceri wrote: >> Il 05/10/2012 17.04, Samuel Rødal ha scritto: >>> On 10/05/2012 04:46 PM, Calogero Mauceri wrote: >>>> Hi, >>>> >>>> is there a way to know programmatically whether the >>>> QGLWidget::bindTexture function fails? >>>> Sometime my bindTexture fails, I can see in the log file there is a line >>>> reporting the binding failure: >>>> >>>> texture upload failed, error code 0x500, enum: 3553 (de1) >>> Hmm, looks like the error reporting is a bit lacking. If you have your >>> own build of Qt you can uncomment the line that says #define >>> QGL_BIND_TEXTURE_DEBUG in qgl.cpp to get more detailed debug output from >>> the bind function. >> Thanks Samuel for your reply. >> We do have our own build of Qt, but I really would avoid to change them, >> it would be very difficult for us to keep our changes in sync with the >> new Qt distributions. > I didn't mean a permanent change, just a temporary one to help figure > out what step in the texture upload that goes wrong. > > If it only fails in certain circumstances, maybe you could file a bug > about that. > Actually it fails when the texture image is big. How much big is machine dependent. That's why I would like to know whether the texture loading fails in order to properly warn the user. Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How to know bindTexture failure
Il 05/10/2012 17.21, Calogero Mauceri ha scritto: > Il 05/10/2012 17.04, Samuel Rødal ha scritto: >> On 10/05/2012 04:46 PM, Calogero Mauceri wrote: >>> Hi, >>> >>> is there a way to know programmatically whether the >>> QGLWidget::bindTexture function fails? >>> Sometime my bindTexture fails, I can see in the log file there is a line >>> reporting the binding failure: >>> >>> texture upload failed, error code 0x500, enum: 3553 (de1) >> Hmm, looks like the error reporting is a bit lacking. If you have your >> own build of Qt you can uncomment the line that says #define >> QGL_BIND_TEXTURE_DEBUG in qgl.cpp to get more detailed debug output from >> the bind function. > Thanks Samuel for your reply. > We do have our own build of Qt, but I really would avoid to change them, > it would be very difficult for us to keep our changes in sync with the > new Qt distributions. > >>> but the bindTexture returns a valid texture id (> 0) and the >>> glGetError() returns 0 (no error). >>> How do I know the binding has failed from my code? >> Yeah, glGetError() won't return an error since it clears the error state >> when it's called from within bindTexture(). >> >> Btw, which OS and Qt version are you using? > I'm using Qt 4.7.3 on Windows, Linux and Mac. > I double checked the bindTexture source code on Qt 4.8 and there does > not seem to be a different error handling than in 4.7 version :( > So anyone can confirm that there is no way to know whether the QGLWidget::bindTexture has failed? If it is no, it seems to me a function design problem. Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How to know bindTexture failure
Il 05/10/2012 17.04, Samuel Rødal ha scritto: > On 10/05/2012 04:46 PM, Calogero Mauceri wrote: >> Hi, >> >> is there a way to know programmatically whether the >> QGLWidget::bindTexture function fails? >> Sometime my bindTexture fails, I can see in the log file there is a line >> reporting the binding failure: >> >> texture upload failed, error code 0x500, enum: 3553 (de1) > Hmm, looks like the error reporting is a bit lacking. If you have your > own build of Qt you can uncomment the line that says #define > QGL_BIND_TEXTURE_DEBUG in qgl.cpp to get more detailed debug output from > the bind function. Thanks Samuel for your reply. We do have our own build of Qt, but I really would avoid to change them, it would be very difficult for us to keep our changes in sync with the new Qt distributions. >> but the bindTexture returns a valid texture id (> 0) and the >> glGetError() returns 0 (no error). >> How do I know the binding has failed from my code? > Yeah, glGetError() won't return an error since it clears the error state > when it's called from within bindTexture(). > > Btw, which OS and Qt version are you using? I'm using Qt 4.7.3 on Windows, Linux and Mac. I double checked the bindTexture source code on Qt 4.8 and there does not seem to be a different error handling than in 4.7 version :( -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] How to know bindTexture failure
Hi, is there a way to know programmatically whether the QGLWidget::bindTexture function fails? Sometime my bindTexture fails, I can see in the log file there is a line reporting the binding failure: texture upload failed, error code 0x500, enum: 3553 (de1) but the bindTexture returns a valid texture id (> 0) and the glGetError() returns 0 (no error). How do I know the binding has failed from my code? This is how the bindTexture is called QImage imgTexture(myImgPath); int _texture = bindTexture( imgTexture, GL_TEXTURE_2D ); Thanks in advance for your help, Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Digia to acquire Qt from Nokia
That would be really interesting to know. Il 29/08/2012 19.41, Mike Short ha scritto: I would be interested in learning about this as well. The effects of the different licensing models fascinates me, and having a knowledge about what the numbers looked like over time, based on the different licensing models would speak volumes. -Mike Short *From:*interest-bounces+mike.short=fawkesengineering@qt-project.org [mailto:interest-bounces+mike.short=fawkesengineering@qt-project.org] *On Behalf Of *Jason H *Sent:* Wednesday, August 29, 2012 10:09 AM *To:* chuck.pier...@nokia.com; charleyb...@gmail.com; bm_witn...@yahoo.com *Cc:* interest@qt-project.org *Subject:* Re: [Interest] Digia to acquire Qt from Nokia I'd be curious. It seems to me that that strategy would see use go up, then some time later commercial licensing would pick up, as the barrier to entry came down, and user bases were established which required support, which in turn enabled commercial licenses. *From:*"chuck.pier...@nokia.com <mailto:chuck.pier...@nokia.com>" mailto:chuck.pier...@nokia.com>> *To:* charleyb...@gmail.com <mailto:charleyb...@gmail.com>; bm_witn...@yahoo.com <mailto:bm_witn...@yahoo.com> *Cc:* interest@qt-project.org <mailto:interest@qt-project.org> *Sent:* Wednesday, August 29, 2012 10:24 AM *Subject:* Re: [Interest] Digia to acquire Qt from Nokia Hi, Is there an interest on this list in learning about the business implications of going LGPL using the Trolltech example? Trolltech's acquisition by Nokia allowed it to add the LGPL license option and then continue conducting business for the next 3 years. If you look at the aggregate business over that time it seems a useful question to ask what happened - Did the initial dramatic license revenue drop turn into growth later because of broader use? Is this a topic people would be interested in and find useful? Chuck Piercey ___ Interest mailing list Interest@qt-project.org <mailto: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 -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Problems animating QGraphicsProxyWidget
Hi All,
I'm trying to animate a push button I have in my scene.
I want the button to become visible with an animation when the mouse
enters the scene (essentially gradually changing the opacity of the
button from 0 to 1)
The QPropertyAnimation class seems to be exactly what I need but it is
not working with QGraphicsProxyWidget.
This is the way I'm creating the button when I initialize the interface
of the QGraphicsView
void MyQGraphicsView::buildInterface(){
myButton = new QPushButton(this);// myButton member
QPushButton variable
myButtonProxy = scene()->addWidget(myButton);// myButtonProxy
member QGraphicsProxyWidget variable
...
}
void MyQGraphicsView::enterEvent( QEvent * )
{
QPropertyAnimation *animation = new QPropertyAnimation(_bt3DView,
"opacity");
animation->setDuration(1000);
animation->setStartValue(0);
animation->setEndValue(1);
animation->start(QAbstractAnimation::DeleteWhenStopped);
}
The animation has no effect on the opacity of the button. I also tried
for test to modify with an animation the position of the button. Well If
I create the QPropertyAnimation using the proxy widget then the
animation is not working, if I create it using the button itsself then
the animation is working (see example below)
void MyQGraphicsView::enterEvent( QEvent * )
{
// QPropertyAnimation *animation = new
QPropertyAnimation(myButtonProxy, "pos");// DOES NOT WORK
QPropertyAnimation *animation = new QPropertyAnimation(myButton,
"pos");
animation->setDuration(1000);
animation->setStartValue(QPointF(0,0));
animation->setEndValue(QPointF(scene()->width()/2,
scene()->height()/2));
animation->start(QAbstractAnimation::DeleteWhenStopped);
}
I'm using Qt 4.7.3
Do you have any idea how to fix this issue?
Thanks in advance,
Calogero
--
Calogero Mauceri
Software Engineer
Applied Coherent Technology Corporation (ACT)
www.actgate.com
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
