Re: [Interest] QImage family of classes - image bucket

2020-12-16 Thread David M. Cotter
if i understand your problem (and i may not), then i recommend using https://doc.qt.io/qt-5/qgraphicsscene.html and https://doc.qt.io/qt-5/qgraphicspixmapitem.html therefore use: https://doc.qt.io/qt

[Interest] QImage family of classes - image bucket

2020-12-16 Thread Nicholas Yue
Hi, I am writing an application that is receiving images in rectangular buckets. These buckets may be destined for different layers of images. I plan to create a list for the layers so that I can show selected and individual ones of interest. Which QImage class is easier to work with wh

Re: [Interest] Is it safe to update to Xcode 12 when still relying on Qt 5.12?

2020-12-16 Thread Tor Arne Vestbø
Hi Nuno, It likely works fine, but is unsupported. The supported case is building Qt with Xcode 10, as per https://doc-snapshots.qt.io/qt5-5.12/ios.html You can still build your _app_ with with Xcode 12 though. Your best bet is upgrading to Qt 5.15: https://doc-snapshots.qt.io/qt5-5.15/ios.htm

[Interest] determining graphics frame swap time when rendering in Qt 6

2020-12-16 Thread Be
Hi, I am a maintainer of Mixxx DJ software and I'm trying to come up with a roadmap for the future of our GUI. The current GUI uses a home-baked XML layout system for QWidgets that predates Qt's UIC. One of the main features of the application is waveform visualizations of the audio tracks being p

Re: [Interest] shell_path, QMAKE_COPY, etc. are broken when building for Android under Windows

2020-12-16 Thread Jérôme Godbout
Maybe a fallback check could be done first, Cygwin add env variables: OSTYPE which can be check to see if this is Cygwin. Or maybe uname detection to confirm. Could be more robust then path executable. With Windows Linux subsystem taking traction versus Cygwin, this check can become even more u

[Interest] Is it safe to update to Xcode 12 when still relying on Qt 5.12?

2020-12-16 Thread Nuno Santos
Hi, I’ve been relying on Qt 5.12. In order to run apps on iOS 14 manually adding Device Support to Xcode doesn’t seem to do the trick. An update to Xcode 12 is required. Is it safe to update to Xcode 12 and compile Qt 5.12 from the source on it? I’m still using Mac OS 10.15 Catalina. Thanks!

Re: [Interest] shell_path, QMAKE_COPY, etc. are broken when building for Android under Windows

2020-12-16 Thread Alexander Dyagilev
Nice... Yes, I have. But it's not used at all. I build using Qt Creator... On 12/16/2020 12:07 PM, Kai Köhne wrote: Hi, Do you have a sh.exe in PATH? If so , qmake assumes you’re running in a Cygwin shell. Regards Kai *From:* Interest *On Behalf Of *Alexander Dyagilev *Sent:* Wednesd

Re: [Interest] shell_path, QMAKE_COPY, etc. are broken when building for Android under Windows

2020-12-16 Thread Kai Köhne
Hi, Do you have a sh.exe in PATH? If so , qmake assumes you’re running in a Cygwin shell. Regards Kai From: Interest On Behalf Of Alexander Dyagilev Sent: Wednesday, December 16, 2020 9:20 AM To: interest Subject: [Interest] shell_path, QMAKE_COPY, etc. are broken when building for Android

Re: [Interest] [Qt BLE] multiple devices connected to an app

2020-12-16 Thread Simon FEUTRIER
Hi Andreas, Here is the issue : https://bugreports.qt.io/browse/QTBUG-89534 In fact, I already have other tickets for BLE (security problem). BLE (Qt) under Windows 10 seems to be hard to manage ! Best regards, Simon Feutrier Le mer. 16 déc. 2020 à 09:41, Andreas Buhr a écrit : > Hi Simon, >

Re: [Interest] [Qt BLE] multiple devices connected to an app

2020-12-16 Thread Andreas Buhr
Hi Simon, On 15.12.20 09:26, Simon FEUTRIER wrote: I developed a remote device which has a u-blox BLE module (this module has an embedded nordic nrf chip if you know it). Thus, I communicate with this module with AT commands and I don't have a lot of information. Some more information I can g

[Interest] shell_path, QMAKE_COPY, etc. are broken when building for Android under Windows

2020-12-16 Thread Alexander Dyagilev
Hello, Is it known bug? Is there workaround? What I mean: The following in .pro file: message(QMAKE_COPY=$$QMAKE_COPY) message(shellpathforPWDis:$$shell_path($$PWD)) Generates the following outputs (under Windows OS): When building for Windows (there is no bug): Project MESSAGE: QMAKE_COPY =