Re: [Interest] qt_add_qml_module() RESOURCES vs qt_add_resources()

[Sze Howe Koh]

On Tue, 13 Feb 2024 at 22:10, ekke  wrote:
>
> Am 13.02.24 um 14:52 schrieb Nils Jeisecke:
> > Hi,
> >
> > On Tue, Feb 13, 2024 at 2:41 PM ekke  wrote:
> >> thx. But it's not the prefix. If I add images.qrc and data-assets.qrc to
> >> the executable, it's working.
> > If cmake policy QTP0001 is set to new, the resource prefix defaults to
> > "/qt/qml/", so your previous URIs won't work.
> >
> > Did you check the generated qrc file for paths?
> >
> > Nils
>
> Hi Nils,
>
> the .qrc are ok with pathes. per ex: "qrc:/images/..." finds the
> requested image
>
> QTP0001 is not set to new, because I cannot easy change my file
> structure. (have 20 mobile business apps ported to 6.6 - some grown over
> 6+ years ;-)
>
> think the best is, I create a Bugreport together with a small demo app.
> current work done with 6.6. Before reporting an issue, will test with
> 6.7 beta2 next days. before this, have to finish my QMake-CMake for iOS
> ;-) Android done :)
>
> ekke

Hi Ekke,

There is no bug. If your resource files are part of your QML module,
then they will be in the same folder as your *.qml files. Probably
"qrc:/Main_Module/images/..." in your case.

To list your app's resource file paths, add the following lines to
your main() function:

QDirIterator qrc(":", QDirIterator::Subdirectories);
while(qrc.hasNext())
qDebug() << qrc.next();


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt online installer error (Mac)

[Sze Howe Koh]

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
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] qt_add_qml_model() dependency issue

[Sze Howe Koh]

Sounds like https://bugreports.qt.io/browse/QTBUG-106683 which was already
fixed in Qt 6.5.2.

However, there's still a related issue outstanding:
https://bugreports.qt.io/browse/QTBUG-115166

As a workaround, use Ninja instead of Makefiles, since Ninja wasn't
affected by these issues.


Regards,
Sze-Howe


On Sun, Oct 29, 2023, 06:04 Stefan Seefeld  wrote:

> Hello,
>
> I just started using the `at_add_qml_model()` function, where the "backing
> target" is a (shared) library. I notice that each time I call `make`, the
> target is rebuilt. Specifically, the sequence
>
> ```
> Running moc --collect-json for target XXX
> Automatic QML type registration for target XXX
> Consolidate compiler generated dependencies of target XXX
> Building CXX object
> libs/XXX/CMakeFiles/XXX.dir/xxx_qmltyperegistrations.cpp.o
> ...
> ```
> is executed (and thus, everything depending on `XXX` needs to be updated
> as well.
>
> Is this a known issue ? I had expected a second call to `make` to do
> nothing, as all targets are up to date.
>
> Thanks,
>
>   ...ich hab' noch einen Koffer in Berlin
>
>
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QtLocation and API key

[Sze Howe Koh]

Hello Petric,

The OpenStreetMap plugin originally did not require an API key.
However, the previous tile server stopped working, so a new tile
server (Thunderforest) was chosen to replace it. Thunderforest wants
an API key, which is why you see the watermark.

Qt Location needs to be updated to pass an API key to Thunderforest. See:
* https://bugreports.qt.io/browse/QTBUG-114118
* https://bugreports.qt.io/browse/QTBUG-115742


Regards,
Sze-Howe


On Mon, 7 Aug 2023 at 20:49, Petric Frank  wrote:
>
> Hello,
>
> i compiled the example "minimal_map". It runs well except there is a watermark
> "API Key Required" at the picture.
>
> By reading some web pages (here: 
> https://uxper.gitbook.io/wp-golo/faqs/how-to-create-an-api-key-for-openstreetmap)
>  it seems you can obtain one from MapBox.
> But how to integrate it into the (example) application ?
>
> Or am i on the wrong track ?
>
> kind regards
>   Petric
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Installer problems

[Sze Howe Koh]

On Mon, 3 Jul 2023 at 20:49, Turtle Creek Software
 wrote:
>
> To diagnose a recent problem, we needed to install Qt on several different 
> computers with different Qt and OS setups.
>
> The open source installer has about a 33% success rate. It gives several hash 
> and socket time-out errors along the way, then often aborts completely. At 
> that point it deletes all previously downloaded files, even if 1GB done out 
> of 1.13GB.
>
> I think the design probably can be improved.  Every other app download goes 
> OK here. Even if interrupted, they finish the remainder later.
>
> Thanks, Casey McDermott
> TurtleSoft.com

Does it help if you choose a different mirror?
https://wiki.qt.io/Online_Installer_4.x#Selecting_a_mirror_for_opensource


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt Quick: no qmake support anymore?

[Sze Howe Koh]

The ability to generate new Qt Quick projects using qmake was deliberately
removed from Qt Creator 10.0:
https://bugreports.qt.io/browse/QTCREATORBUG-28964

It will come back in a future release:
https://codereview.qt-project.org/c/qt-creator/qt-creator/+/473719

Qt Creator 10.0 can still load and build existing .pro files that use Qt
Quick. We can also manually convert a qmake-based console/widgets
application into a Qt Quick application.


Regards,
Sze-Howe

On Sat, 29 Apr 2023 at 19:55, Axel Spoerl via Interest <
interest@qt-project.org> wrote:

> ...that means, Creator has at least one valid Qt Version in
> Edit->Preferences->Kits->Qt Versions, that
>
>- is pointing to a qmake executable,
>- located in a build tree that has (at least) qtbase, qtshadertools
>and qtdeclarative compiled / installed?
>
>
> If all of that is the case, Creator should offer the qmake option for
> Quick. That's what it does here.
>
> If it still doesn't offer it for you, please file a bugreport. Would be
> great if it included screenshots of
>
>- the respective Qt Version in Creator
>- toplevel directories in the build tree, or
>- of the online installer, showing which kits have been installed
>
>
> --
> *Von:* Alexander Dyagilev 
> *Gesendet:* Samstag, 29. April 2023 13:09
> *An:* Axel Spoerl ; interest@qt-project.org <
> interest@qt-project.org>
> *Betreff:* Re: [Interest] Qt Quick: no qmake support anymore?
>
>
> It's installed correctly and is able to find qmake.
>
>
> If I try to create a Widgets application - there is qmake available. I
> don't see it only in case of Qt Quick application project.
>
>
> On 4/29/2023 1:38 PM, Axel Spoerl via Interest wrote:
>
> Hi Alexander,
>
> if Qt Creator has been installed correctly and it finds qmake, it is
> available and supported.
> This is my Qt Creator 10 on MacOS:
>
>
>
> Cheers
> Axel
> --
> *Von:* Interest 
>  im Auftrag von Alexander Dyagilev
>  
> *Gesendet:* Samstag, 29. April 2023 12:05
> *An:* interest@qt-project.org 
> 
> *Betreff:* [Interest] Qt Quick: no qmake support anymore?
>
> Hello,
>
> I'm trying to create a new Qt Quick application in Qt Creator 10 under
> macOS.
>
> On the Define Build System steps there are only two available: cmake and
> qbs.
>
> Is it a bug or qmake is not supported anymore? If it's not supported,
> what will happen with existing projects? I do not get any errors while
> building existing qmake projects.
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
> ___
> Interest mailing 
> listInterest@qt-project.orghttps://lists.qt-project.org/listinfo/interest
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QML plugin with wasm not building

[Sze Howe Koh]

Does it work if you use STATIC instead of SHARED?

Is the plugin built at the same time as the main application?


On Tue, Feb 14, 2023, 14:44 Konstantin Shegunov  wrote:

> Me again. If it matters, the exact diagnostics is as follows:
>
> On Mon, Feb 13, 2023 at 10:22 AM Konstantin Shegunov 
> wrote:
>
>> `qt_register_pluginXXX` (or something of this sort).
>>
>
> Here's what emscripten reports:
>
> error: undefined symbol: _Z31qt_static_plugin_XXX_UiPluginv (referenced by
> top-level compiled C/C++ code)
> warning: Link with `-sLLD_REPORT_UNDEFINED` to get more information on
> undefined symbols
> warning: To disable errors for undefined symbols use
> `-sERROR_ON_UNDEFINED_SYMBOLS=0`
> warning: __Z31qt_static_plugin_XXX_UiPluginv may need to be added to
> EXPORTED_FUNCTIONS if it arrives from a system library
> Error: Aborting compilation due to previous errors
>
> If I don't use  `PLUGIN_TARGET xxx`, instead I get a cmake warning and the
> runtime says the plugin can't be loaded:
> ---/qtbase/lib/cmake/Qt6Qml/Qt6QmlMacros.cmake:2821 (message):
>   The qml plugin 'xxx-uiplugin' is a dependency of 'xxx', but the link
>   target it defines (xxx-uiplugin) does not exist in the current scope.
>   The plugin will not be linked.
> Call Stack (most recent call first):
>   ---/qtbase/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:640
> (qt6_import_qml_plugins)
>   ---/qtbase/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:640 (cmake_language)
>   ---/qtbase/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:705
> (_qt_internal_finalize_executable)
>   ---/qtbase/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:562:EVAL:1
> (qt6_finalize_target)
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] MSVC not-the-latest: are you using it? why?

[Sze Howe Koh]

On Sat, Feb 4, 2023, 07:51 Bob Babcock  wrote:
>
> Thiago Macieira  wrote in
> news:2741742.BEx9A2HvPv__44352.1315975644$1674404321$gmane$org@tjmaciei-m
> obl5:
>
> > So, are you still
> > sticking to older MSVC releases years after there's a new one? Why?
>
> Because when I run the maintnance tool for 6.4.2, I see MSVC 2019, but not
> 2022 (even after installing 2022).

They are binary-compatible. You can use MSVC 2022 with DLLs that were
built with MSVC 2019.

This has been the case since MSVC 2015:
https://learn.microsoft.com/en-us/cpp/porting/binary-compat-2015-2017?view=msvc-170


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Text resources

[Sze Howe Koh]

On Sun, 15 May 2022 at 07:24, Turtle Creek Software
 wrote:
>
> We just started moving a Mac project to Windows.
>
> When reading text resources into a QString, the Win version automatically 
> replaces all /n line endings with /r/n.  That screws up our line parsing.

Shouldn't it be the other way round...? A text file Reader converts
"\r\n" to "\n" on Windows.

It's a text file Writer that converts "\n" in a QString to "\r\n" in a
file on Windows.


> The code creates a QString from QFile:readAll(), and the change happens 
> somewhere in that constructor.
>
> Is there a way to prevent that behavior?  Using QFile::readLine() would be a 
> pain.
>
> Thanks, Casey McD

What behaviour do you want, and how does it make it less painful?


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QtCreator >= 6 - Problems using code indentation shift with tab key

[Sze Howe Koh]

On Fri, 15 Apr 2022 at 15:02, André Pönitz  wrote:
>
> On Fri, Apr 15, 2022 at 06:28:34AM +0100, Nuno Santos wrote:
> > Kevin,
> >
> > Thanks for your feedback.
> >
> > Is anyone from the Qt Creator team around and aware of this? Is this a new
> > setting? A bug? A feature?
> >
> > Should we open bug report?
>
> That would probably be the best approach.
>
> Andre'

Someone already did: https://bugreports.qt.io/browse/QTCREATORBUG-27365


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Creating fat binaries for Qt6 on macOS

[Sze Howe Koh]

On Wed, 13 Apr 2022 at 07:34, Dirk Hohndel  wrote:
> > > So... hear me out here... if Qt can switch to OpenGL... and if this thingy
> > > doesn't work unless it's OpenGL... shouldn't Qt simply switch to OpenGL?
> > > Or is this too radically useful?
> > >
> >
> > My guess is that it has to be explicit on your side because Metal has some
> > advantage that OpenGL doesn't. I wouldn't know what, since it's not an area 
> > I
> > pay attention to.
> >
>
> :-)
>
> So instead of defaulting to something that works, Qt defaults to something 
> that
> may have some vague advantage that you aren't certain about.
>
> Solid reasoning. 藍

Apple has let their OpenGL implementation stagnate since 2010 [1].
They then officially deprecated it in 2018, citing significant
advantages of Metal over OpenGL [2]. They have not revealed when
OpenGL will be removed.

Most of Qt Quick works well with Metal -- it's only QQuickWidget that
doesn't. In contrast, the graphics API setting affects all of Qt
Quick. Furthermore, QQuickWidget has limitations [3] compared to other
ways of displaying a Qt Quick UI, so it shouldn't be the first choice
unless you really need to mix widgets with Qt Quick.

Given all this, I don't think it makes sense for Qt to default to
something that can be killed off any day now, just to make it easier
to use QQuickWidget.

In any case, I think the error message "QQuickWidget is only supported
on OpenGL. Use QQuickWindow::setGraphicsApi() to override the default"
is clear enough as a once-off message for those who want to use
QQuickWidget.


Regards,
Sze-Howe

[1] https://support.apple.com/en-us/HT202823
[2] 
https://venturebeat.com/2018/06/06/apple-defends-end-of-opengl-as-mac-game-developers-threaten-to-leave/
[3] https://doc.qt.io/qt-6/qquickwidget.html#performance-considerations
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QtWebEngine missing in Qt6.2.4 ?

[Sze Howe Koh]

It is now "QT += webenginequick" (in contrast to "QT +=
webenginewidgets"):
https://doc.qt.io/qt-6/qtwebenginequick-module.html

This is a kind of source compatibility break; it would be nice if
there were deprecation warnings instead of an outright error.


Regards,
Sze-Howe

On Fri, 8 Apr 2022 at 20:27, Alexander Carôt  wrote:
>
> P.S.: The question arises from me trying to compile the QtWebBrowser:
>
> https://code.qt.io/cgit/qt-apps/qtwebbrowser.git/
>
> which includes the module via
>
> QT += qml quick webengine
>
> but out of the box it does not find the module:
>
> Project ERROR: Unknown module(s) in QT: webengine
>
>
> --
> http://www.carot.de
> Email : alexan...@carot.de
> Tel.: +49 (0)177 5719797
>
>
> > Gesendet: Freitag, 08. April 2022 um 13:50 Uhr
> > Von: "Alexander Carôt" 
> > An: "qt qt" 
> > Betreff: [Interest] QtWebEngine missing in Qt6.2.4 ?
> >
> > Hello all,
> >
> > I just installed Qt6.2.4 for OSX (12.2.1 Monterey) with any module, 
> > however, when trying to use QtWebEngine I realize it's not there:
> >
> > Project ERROR: Unknown module(s) in QT: webengine
> >
> > Did I possibly miss anything or is any further action required ?
> >
> > Thanks in advance for letting me know
> >
> > Alex
> >
> > --
> > http://www.carot.de
> > Email : alexan...@carot.de
> > Tel.: +49 (0)177 5719797
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Minimal Cmake version for building Qt 6.x

[Sze Howe Koh]

On Tue, 11 Jan 2022 at 21:18, Ramakanth Kesireddy  wrote:
>
> Hi,
>
> Can anyone let me know about the minimal Cmake version in building Qt 6.2.2 
> sources on embedded platforms (Linux)?

See 
https://doc.qt.io/qt-6/qt6-buildsystem.html#cmake-ninja-as-external-dependencies


> If am not mistaken, it requires C++ compatible compiler supporting atleast 
> C++17 in building Qt6.x,right?

Yes


> Best Regards,
> Ramakanth

Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Guide me through the Qt offerings for GUIs

[Sze Howe Koh]

On Thu, 22 Apr 2021 at 23:38, Eric Fedosejevs  wrote:
> I do not disbelieve you, but I live in the world of trust but verify
>
> I have been searching for years for an example of a substantial QML based 
> desktop productivity application without success. I want to know that it is 
> both possible and straightforward to build such an application before I 
> devote my time to it. I don't particular like having to use a scripting 
> language, but I can stomach it if it works well. However, the lack of 
> examples leads me to conclude that even if it is possible, it must be a royal 
> pain.

Someone brought up MuseScore in another post recently. Does this
count? https://github.com/musescore/MuseScore/tree/master/src/appshell/qml


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] [Development] [Releasing] download.qt.io is down

[Sze Howe Koh]

Thank you, Tuukka and co!


Regards,
Sze-Howe

On Fri, 22 Jan 2021 at 22:33, Tuukka Turunen  wrote:
>
> Hi,
>
>
>
> Servers have been restored and open-source downloads are working again.
>
>
>
> Archive of old and historic releases is missing, but will be made available 
> next week.
>
>
>
> Blog post: https://www.qt.io/blog/open-source-downloads-working-again
>
>
>
> Yours,
>
>
>
> Tuukka
>
>
>
> From: coroberti 
> Date: Friday, 22. January 2021 at 11.32
> To: Nils Jeisecke , Tuukka Turunen 
> , Qt Project Development 
> Subject: Re: [Development] [Releasing] [Interest] download.qt.io is down
>
> On Fri, Jan 22, 2021 at 10:38 AM Nils Jeisecke via Development
>  wrote:
> >
> > Hi there,
> >
> > On Fri, Jan 22, 2021 at 7:59 AM Tuukka Turunen  wrote:
> >>
> >> Hi,
> >>
> >>
> >>
> >> Status update of the problem with open-source downloads: Last night we 
> >> finally got a disk big enough for the packages from the service provider. 
> >> Most of the data has been transferred throughout the night with a few last 
> >> things still being uploaded to the new virtual server. After the data 
> >> transfer is complete we start testing and validation of the data and the 
> >> system. Target is to enable first the online installer, then the offline 
> >> packages and finally the achieve of old releases.
> >
> >
> > just a little "Thank You" from my side.
> >
> > I try to imagine being of those spending hour after hour to get things 
> > running again and then reading all those nasty comments on the blog post.
> >
> > Nils
>
> Joining the thanks of Nils.
> We are really appreciating your support of open-source distribution.
>
> Kind regards,
> Robert Iakobashvili
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] [Releasing] download.qt.io is down

[Sze Howe Koh]

On Wed, 20 Jan 2021 at 04:10, Tuukka Turunen  wrote:
>
>
> Hi,
>
> There are multiple mirrors, try for example:
>
>
>
> https://qt-mirror.dannhauer.de/
>
> https://www.funet.fi/pub/mirrors/download.qt-project.org/
>
> https://ftp.fau.de/qtproject/
>
>
>
> ...or just use the online installer, which picks mirrors automatically.
>
> Yours,
>
> Tuukka

Hi Tuuka,

The Online installer downloads files in 2 phases:

1. Retrieve metadata from download.qt.io
2. Retrieve actual binaries from the auto-selected mirror

Since Step #1 is blocked, it can't proceed to Step #2.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QCoreApplication, argc parameter type

[Sze Howe Koh]

On Fri, 8 Jan 2021 at 07:39, Bernhard Lindner
 wrote:
>
> Hi!
>
> Can someone tell me why QCoreApplication uses an 'int ' type parameter 
> instead of a
> plain 'int argc'? Does QCoreApplication expect the value to change? Does it 
> change the
> value by itself?
>
> When deriving from QCoreApplication this can cause funny crashes if one 
> forgets to use a
> reference type in the derived class' constructor parameter. So I guess there 
> must be a
> very good reason why QCoreApplication uses a reference instead of 
> copy-by-value.

According to the documentation
(https://doc.qt.io/qt-5/qapplication.html#QApplication and
https://doc.qt.io/qt-5/qcoreapplication.html#QCoreApplication ):

* Note: argc and argv might be changed as Qt removes command line
arguments that it recognizes.
* Warning: The data referred to by argc and argv must stay valid for
the entire lifetime of the QCoreApplication object.


> --
> Best Regards,
> Bernhard Lindner

Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Will a Qt 5.x release support macOS 11?

[Sze Howe Koh]

On Wed, 9 Dec 2020 at 20:48, Tor Arne Vestbø  wrote:
> > On 9 Dec 2020, at 13:16, Tor Arne Vestbø  wrote:
> >
> > Hi Benjamin,
> >
> > Qt 5 will officially support macOS 11 in upcoming 5.15 and 5.12 patch 
> > releases, but should work fine already. If you encounter issues with the 
> > current releases (or preferably after building from git), please let us 
> > know by filing bug reports. Thanks!
>
> Correction, 5.15, not 5.12.
>
> Cheers,
> Tor Arne

Hi Tor Arne,

To clarify: Qt 5.15 will continue to receive patch releases under the
open source licenses until all the planned Qt 5 add-on modules are
migrated/supported in Qt 6, right?


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt6 & "multimedia"

[Sze Howe Koh]

On Wed, 9 Dec 2020 at 05:20, David M. Cotter  wrote:
>
> I see that "multimedia" has been removed, and also i see here that things 
> were being worked on, but no work lately?
>
> My app IS a multimedia app and relies heavily on multimedia for camera input 
> and video playback.
>
> what is the status of this? what is the intended replacement?
>
> Specifically:
>
> is this the case:
> "we wanted to release Qt6 asap, so didn't wait until multimedia was done. we 
> will finish mutimedia and then make it part of Qt6"...
>
> or is it this case:
> "multimedia will no longer be part of Qt. we may in the future support some 
> parts of what used to be called multimedia (WUTBCM), but you will be expected 
> to rewrite anything that depends on WUTBCM"
>
> anyone know?

It's the first case.

https://www.qt.io/blog/add-on-support-in-qt-6.0-and-beyond


> On Dec 8, 2020, at 6:11 AM, Jani Heikkinen  wrote:
>
> Hi all!
>
> We have released Qt 6.0.0 today! Please see more information from Qt 6.0.0 
> release blog post: https://www.qt.io/blog/qt-6.0-released
>
> Big thanks to everyone involved!
>
> br,
> Jani Heikkinen
> Release Manager
> The Qt Company

Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] how exactly do you replace Qt4's QWidget::create(WId, ...) ?

[Sze Howe Koh]

On Mon, 10 Aug 2020 at 00:53, René J.V. Bertin  wrote:
>
> Hi,
>
> According to the documentation, where in Qt4/X11 one could create a "foreign" 
> QWidget with QWidget::create(WId id, ...), in Qt5 one has to do something like
>
> externalWindow = QWindow::fromWinId(id);
> if (externalWindow) {
> externalParent = externalWindow->parent();
> theWidget = QWidget::createWindowContainer(externalWindow);
> }
>
> (with externalParent required to reparent externalWindow before destroying 
> the container).
>
> Except that when I do this, I get 2 windows (neither of which will show my 
> content), and the original window gets resized even when I take care not to 
> ask for that (not directly at least).
>
> I also see a series of
>
> QWidget::paintEngine: Should no longer be called
> QPainter::begin: Paint device returned engine == 0, type: 1
>
> on the terminal which I don't see if I just create a new QWidget .
>
> I guess I must be missing something?

I haven't seen the symptoms that you've described, but I've seen other
weirdness with QWidget::createWindowContainer() on foreign windows:
https://bugreports.qt.io/browse/QTBUG-40320

I don't think they've ever been resolved in Qt 5.


> Thanks,
> R.
>
> PS: goal here is to convert an old KDE4 screensaver to Qt5 - a cute project 
> for a steamy sunday afternoon ;)

Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] List on moderation

[Sze Howe Koh]

On Fri, 17 Jul 2020 at 21:32, Andy Shaw  wrote:
>
> This seems as a good summary as any. Thanks Swe-Howe.
>
> We have taken the list off moderation now, so please do not do post personal 
> attacks or insult and be derogatory. We don't want to have to moderate the 
> list and want everything to be open for all and that this community is a safe 
> one for everyone to take part in.
>
> I hope you all have a relaxing weekend.
>
> Kind regards,
> Andy

Thanks Andy for encouraging the mailing list to run smoothly and
civilly, and for lifting restrictions again. (I suppose restrictions
would be re-imposed if things start to flare up again, like a virus
outbreak)


> -Original Message-
> From: Interest  on behalf of Howe Koh Sze 
> 
> Date: Friday, 17 July 2020 at 14:47
> To: "interest@qt-project.org" 
> Subject: Re: [Interest] List on moderation
>
> On Fri, 17 Jul 2020 at 13:37, Bernhard Lindner
>  wrote:
> >
> > > Ps: I usually don't read emails from xyz fully, but every now and 
> then, I like the
> > > critical approach, I just wish that these emails were straight to the 
> point.
> >
> > Same here.
> >
> > Roland, maybe you would reach more people if you could make it short 
> and a little less emotional?
>
> * Being critical is OK.
> * Being emotional is OK.
> * Being long-winded is OK.
> * Going off on a tangent once in a while is OK.
>
> * Challenging the status quo is OK.
> * Presenting personal opinions is OK.
> * Presenting sound technical arguments is OK.
> * Pointing out the flaws in others' approaches/arguments/ideas is OK.
>
> * Being insulting and derogatory is _not_ OK.
> * Going off on a tangent frequently is _not_ OK.
> * Repeatedly hijacking threads and derailing them for one's own agenda
> is _not_ OK.
> * Making factually incorrect statements, and then refusing to retract
> or acknowledge them when the error is pointed out, is _not_ OK.

I forgot an important set:

* Extolling the virtues of a particular technology/methodology is OK.
* Highlighting the flaws and limitations of a particular
technology/methodology is OK.

* Demanding or coercing all programmers to avoid a particular
technology/methodology -- for all industries and use-cases -- is _not_
OK.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] List on moderation

[Sze Howe Koh]

On Fri, 17 Jul 2020 at 13:37, Bernhard Lindner
 wrote:
>
> > Ps: I usually don't read emails from xyz fully, but every now and then, I 
> > like the
> > critical approach, I just wish that these emails were straight to the point.
>
> Same here.
>
> Roland, maybe you would reach more people if you could make it short and a 
> little less emotional?

* Being critical is OK.
* Being emotional is OK.
* Being long-winded is OK.
* Going off on a tangent once in a while is OK.

* Challenging the status quo is OK.
* Presenting personal opinions is OK.
* Presenting sound technical arguments is OK.
* Pointing out the flaws in others' approaches/arguments/ideas is OK.

* Being insulting and derogatory is _not_ OK.
* Going off on a tangent frequently is _not_ OK.
* Repeatedly hijacking threads and derailing them for one's own agenda
is _not_ OK.
* Making factually incorrect statements, and then refusing to retract
or acknowledge them when the error is pointed out, is _not_ OK.


> --
> Best Regards,
> Bernhard Lindner

Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Delete Account

[Sze Howe Koh]

On Mon, 24 Feb 2020 at 20:57, Frederik Schwarzer  wrote:
>
> Hi,
>
> I just tried to close down my qt.io account but it is not possible.
>
> The Wiki says: go to Support
> Support says: only for commercial customers
>
> Please advice me on how to delete a private account.

Hi,

If you're happy to post in the forum, you can post your request at
https://forum.qt.io/topic/69221/delete-qt-account/

I've also forwarded your email (BCC) to someone who can take care of
it for you; please wait for them to contact you.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QtWebkit error while building Qt5.12.7 sources

[Sze Howe Koh]

On Wed, 19 Feb 2020 at 08:05, Thiago Macieira  wrote:
>
> On Tuesday, 18 February 2020 15:45:26 PST Sze Howe Koh wrote:
> > That version is very old and unmaintained. It probably contains many
> > security holes and incompatibilites with Qt 5.12.
> >
> > Get the "5.212" branch from https://code.qt.io/cgit/qt/qtwebkit.git instead.
>
> No, don't. That's also very old an unmaintained, just less old than 5.5.
>
> There's no good solution for using qtwebkit. You have to stop using it.

I was under the impression that Konstantin Tokarev was keeping the Qt
WebKit sources up-to-date with upstream WebKit, even though it's not
part of the official Qt releases?

To Ramakanth: There is also Qt WebEngine which you can use
out-of-the-box with Qt 5.12.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QtWebkit error while building Qt5.12.7 sources

[Sze Howe Koh]

On Wed, 19 Feb 2020 at 00:33, Ramakanth Kesireddy  wrote:
>
> Hi,
>
> While trying to build Qt Webkit sources from Qt 5.5.1 as a separate module 
> being part of Qt 5.12.7 sources,

That version is very old and unmaintained. It probably contains many
security holes and incompatibilites with Qt 5.12.

Get the "5.212" branch from https://code.qt.io/cgit/qt/qtwebkit.git instead.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Why doesn't my model filter update?

[Sze Howe Koh]

On Wed, 19 Feb 2020 at 05:51, Matthew Woehlke  wrote:
>
> On 18/02/2020 16.31, Konstantin Shegunov wrote:
> > On Tue, Feb 18, 2020 at 11:20 PM Matthew Woehlke wrote:
> >> I wonder if anyone else can spot it? ;-)
> >
> > Without knowing anything about the code at all, my best guess based on a
> > very quick glance would be the range for the dataChanged is wrong.
>
> Okay, I'll give you half a cookie, since I can't really say much more
> without giving it away. (Incidentally, if I hadn't already figured it
> out, you comment probably would have helped!)
>
> Here's the broken code:
>
>   if (auto const rows = this->rowCount())
>   {
> auto const& first = this->index(0, 0);
> auto const& last = this->index(rows, 0);
>
> emit this->dataChanged(first, last, {MyFilterRole});
>   }
>
> It fell victim to one of the two hard problems of programming (as
> enumerated by Leon Bambrick¹). To wit, `last` is an invalid index, which
> trips one of the sanity checks in QSortFilterProxyModel's internal logic.
>
> If you can't tell *why* `last` is invalid, well, keep looking until you
> can ;-). All the information you need to spot the problem is in the
> above snippet, and it's *obvious* once you see it. (Note: assume that
> the class otherwise behaves in a correct fashion.)
>
> (¹ https://www.goodreads.com/quotes/7443069)
>
> --
> Matthew

The last valid row index is (rows-1), not (rows).

Do I get the other half-cookie?


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Signal/Slot connection fails, even though QMetaObject::activate is called

[Sze Howe Koh]

On Sat, 8 Feb 2020 at 06:45, Jonathan Purol  wrote:
>
> Hello everyone,
>
> I have a QMainWindow subclass called `text_editor` with a function
> `save` which looks as follows:
> ```cpp
> void text_editor::save() {
>
>  _textbox->document()->setModified(false);
>  _textbox->setFocus();
>
>  emit saved();
>
> }
> ```
>
> I now connect to that slot in another class like this:
> ```cpp
> _information_editor = new text_editor{this};
>
> connect(
>  _information_editor,
>  _editor::saved,
>  this,
>  [=]() {
>  std::cout << "hello\n";
>  }
> );
>
> ```

You passed `this` as the 3rd argument — this argument specifies the
"context" in which to run the lambda expression. In other words, you
are telling the lambda to run in the thread that `this` object lives
in.

If `this` object lives in a thread that doesn't have an event loop,
the lambda will never run.

Question: Which thread does `this` live in?


> I have verified that the signal is emitted, in fact, the method
> generated by the moc:
> ```cpp
> // SIGNAL 0
> void text_editor::saved()
> {
>  QMetaObject::activate(this, , 0, nullptr);
> }
> ```
> is definitely called (verified with gdb and some other debugging
> shenenigans).
> In addition, the connection object returned by `connect` is valid, as
> verified by its implicit bool-cast operator.
> However, "hello" is never printed.

Sanity check:
* If you write something to std::cout in main(), does it get printed?
* If you replace std::cout with qDebug(), does it get printed?


> I suspected this could be because
> `text_editor` inherits from `QMainWindow` and could have a different
> thread affinity, so I tried the following things:

Thread affinity is not affected by the inheritance tree in any way at
all. By default, the object has an affinity for the thread that
constructed it.

You can change an object's thread affinity (in other words, change the
thread that the object _lives in_) by calling QObject::moveToThread().
Note that moveToThread() must only be called in the thread that the
object currently lives in.


> 1. Move the editor to the same thread as the object which establishes
> the connection

If your text_editor is a subclass of QMainWindow, then it must always
be created in the GUI thread and it should always stay in the GUI
thread. Otherwise, Bad Things(TM) can happen.


> 2. Use a QueuedConnection

For a queued connection to work, the receiver thread must have a
running event loop.


> 3. Connect to the slot from WITHIN the text editor itself, making sure
> that we are 100% on the same slot

I don't quite understand what you mean here. Please post your connection code.


> and none of them worked.
> Just for clarification, the print of "hello" is only an example, so even
> if there was some issue with that, I would have detected it, the actual
> code is of course different.
>
> I'm really out of luck here, and would appreciate any help.
>
> Sincerely,
> Folling


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] qdoc \qmltype \inherits Module::Type now broken?

[Sze Howe Koh]

On Sun, 4 Aug 2019 at 08:48, Konstantin Podsvirov
 wrote:
>
> Hello to all!
>
> I'm develop osgQtQuick project:
>
> https://github.com/podsvirov/osgqtquick/tree/develop
>
> And use qdoc to generate documentation:
>
> https://podsvirov.github.io/osgqtquick/osgdoc/index.html
>
> The project consists of several modules, and before with cross-references 
> between modules everything was fine.
>
> I try to upgrade to version Qt 5.12, but the inheritance from types from 
> other modules has stopped working.
>
> I have the impression that the \inherits command stopped recognizing the full 
> type names with the module name prefix.
>
> --
> Regards,
> Konstantin Podsvirov

Hi Konstantin,

This might be fixed by https://codereview.qt-project.org/c/qt/qttools/+/268476


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Online doc URL improvement

[Sze Howe Koh]

On Sat, 8 Jun 2019 at 10:37, Hamish Moffatt  wrote:
>
> On 7/6/19 9:58 am, Sze Howe Koh wrote:
> > On Thu, 6 Jun 2019 at 10:09, Christian Gagneraud  wrote:
> >> Hi there,
> >>
> >> I quite often read the documentation online, b/c the urls are quite
> >> short and simple i usually type them in directly in the URL bar.
> > I also use the online docs a lot, but I rarely edit the URL.
> >
> > Instead, I use the Qt Doc Search browser extension for Chrome/Firefox:
> > https://forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches
> > (Disclaimer: I wrote this extension)
> >
> > I activate the URL bar and type [q] + [d] + [space] +  + 
> > [Enter]
> >
> > If Google's "I'm Feeling Lucky" or DuckDuckGo's "Ducky" are enabled,
> > you'll be taken straight to the class reference page.
>
> How is viewing the documentation online easier than using Qt Assistant?

When I'm already in the web browser (e.g. answering questions on the
forum, posting to the mailing list via Gmail, or writing bug reports),
then it's easiest for me to hit Ctrl+T and search the online docs in
the same browser. Furthermore, the online docs lets me copy+paste
relevant URL(s) into the forum/webmail/bugtracker. Qt Assistant
doesn't let me do that.

When I'm coding in Qt Creator, then it's easiest for me to hit F1 and
activate the embedded Qt Assistant.


> Hamishj

Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Online doc URL improvement

[Sze Howe Koh]

On Thu, 6 Jun 2019 at 10:09, Christian Gagneraud  wrote:
>
> Hi there,
>
> I quite often read the documentation online, b/c the urls are quite
> short and simple i usually type them in directly in the URL bar.

I also use the online docs a lot, but I rarely edit the URL.

Instead, I use the Qt Doc Search browser extension for Chrome/Firefox:
https://forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches
(Disclaimer: I wrote this extension)

I activate the URL bar and type [q] + [d] + [space] +  + [Enter]

If Google's "I'm Feeling Lucky" or DuckDuckGo's "Ducky" are enabled,
you'll be taken straight to the class reference page.

> One
> little thing is annoying me, the '.html extension.
> Wouldn't it be great if instead the url would be 'doc.qt.io/qt-5/qwidget'.
> That is shorter to type and easier to navigate to a class you know the
> name of. Currently you have to move the cursor around in the url field
> so that you replace the class name b/w '/' and '.html'. not having to
> deal with '.html' would make the process way faster/easier.

I don't feel strongly either way, but the final solution should be
consistent across all pages, not just C++ classes. What do you propose
for URLs like these?:

* https://doc.qt.io/qt-5/qwidget-members.html
* https://doc.qt.io/qt-5/qml-qtquick-item.html


> Of course to avoid breaking search engine, bookmarks, ... the url with
> '.html' would have to redirect to the one w/o.

(Off-tangent: The online docs broke things a few years ago when they
stopped supporting CamelCase. https://doc.qt.io/qt-5/QWidget.html used
to work, but now it gives Error 404... )

> Any thoughts?
>
> Chris

Thanks for thinking of new ways to improve the docs!


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] vs. Flutter

[Sze Howe Koh]

On Wed, 20 Feb 2019 at 00:33, Jason H  wrote:
> Also, FWIW, I don't know why PySide didn't take up Riverbank's PyQt. So now 
> we have Mobile and Python fragmentation in Qt.

They did try, but couldn't reach an agreement with Riverbank:
https://wiki.qt.io/PySide_FAQ (see "What About PyQt?")

PyQt is Commercial/GPL only. Nokia (the then-owners of Qt) wanted LGPL.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.12 Official packages for MinGW 64 bit?

[Sze Howe Koh]

On Tue, 16 Oct 2018 at 12:55, Andy  wrote:
>
> Yes - that's exactly why I was asking.
>
> I switched to MSVC specifically because I need WebEngine but would much 
> rather use MinGW or Clang.
>
> I have users who don't have admin privileges, so packaging MSVC-built 
> applications is a big headache.

Your users only need admin priviledges if you ask them to run the MSVC
Redistributable installer.

If I'm not mistaken, the EULA allows you to copy the required MSVC
DLLs into your application folder instead. See
https://social.msdn.microsoft.com/Forums/en-US/8089a33c-ddeb-48e1-92c3-609e43ca96a2/msvcrt-redistributable-wherehowdocumentationlicensing-
for example.


Regards,
Sze-Howe

> ---
> Andy Maloney  //  https://asmaloney.com
> twitter ~ @asmaloney
>
>
>
> On Tue, Oct 16, 2018 at 3:58 AM 黄其泽  wrote:
>>
>> I heard that the upstream Chromium supports clang for windows. Will Qt 
>> official package provide clang version?
>>
>> Distributing windows desktop software built with msvc is a big trouble. As 
>> the msvc redistribution packages require administrator privilege, and fail 
>> to install in many computer.
>>
>> Kai Koehne  于2018年10月16日周二 下午2:32写道：
>>>
>>> > -Original Message-
>>> > [...]
>>> > I don't know how the coin stuff works, but does this mean that there will 
>>> > be
>>> > official MinGW 64 bit packages for 5.12?
>>> >
>>> > If so, will WebEngine be included?
>>>
>>> No. Qt WebEngine currently supports only MSVC 2017.
>>>
>>> Kai
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.11.1 offline installer doesn't select Qt 5.11.1

[Sze Howe Koh]

On Wed, 19 Sep 2018 at 13:28, Jason H  wrote:
> I noticed that when using the offline installer that the Qt 5.11.1 box is not 
> checked by default. It would be good if it came pre-checked because that's 
> what I'm trying to do. :-) It's too easy to blow past that and get an install 
> were Qt Creator doesn't work...

There are multiple versions of Qt 5.11.1 underneath that box
(different compilers, different targets...). The installer doesn't
know which version they want. We could just install ALL versions to
ensure that nobody gets stuck... but that causes other problems
(namely, disk bloat).

I suggested a wizard to help identify which version the user wants, or
a popup warning if the user proceeds without selectng any version of
Qt. However, the installer team isn't keen on adding even more
interactive bits to the installer:
* http://lists.qt-project.org/pipermail/development/2018-April/032461.html
* http://lists.qt-project.org/pipermail/development/2018-April/032468.html

There is some good news: A UX consultant called Gearbox has been
commissioned to help iron things out (see, for example,
https://bugreports.qt.io/browse/QTIFW-940 ). If you have any other
ideas, post them to the bug tracker and ping the Qt-IFW team.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Does QNetworkAccessManager support HTTP persistent connections? (keep-alive)

[Sze Howe Koh]

On Sat, 28 Jul 2018 at 06:28, Giuseppe D'Angelo via Interest <
interest@qt-project.org> wrote:
> Extract the RPM, and there it is, in all of its glory, a KeepAlive Off
> by default in Apache's master configuration file:
>
> > $ grep -nr KeepAlive .
> > ./etc/httpd/conf/httpd.conf:73:# KeepAlive: Whether or not to allow
persistent connections (more than
> > ./etc/httpd/conf/httpd.conf:76:KeepAlive Off



> Cargo cult sysadminning FTW!
>
> (Luckily, it seems to have been removed in CentOS 7).

Great detective work, Giuseppe! You were spot on.

I shared your findings with a Qt Company ICT staff, and I received word
today that the host has changed the relevant settings.

I can confirm that the Qt Online Installer now re-uses connections for
downloading metadata. QNAM was working as advertised all along.


Thanks and regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Does QNetworkAccessManager support HTTP persistent connections? (keep-alive)

[Sze Howe Koh]

On Thu, 26 Jul 2018 at 09:24, Thiago Macieira  wrote:
>
> On Wednesday, 25 July 2018 17:59:07 PDT Sze Howe Koh wrote:
> > I think the comms was HTTP 1.1, because Wireshark showed "HTTP/1.1 200
> > OK(text/plain)"
>
> Ok, so the server chose to close the connection.
>
> It did not happen for me when using curl, also with download.qt.io. Possible
> reasons:
>  1) different mirror
>  2) server behaves differently based on the User-Agent
>
> #2 is likely.

Thanks for trying, Thiago.

To clarify: Did the server respond to your GET with "Connection:
keep-alive" instead of "Connection: close", when you downloaded a
metadata file (*meta.7z)?

I sent requests from 3 different programs with different user-agents
(plus 1 request from a VM). All of them got "Connection: close" from
the server.

Interestingly, all 3 requests from Windows got a RST from the server,
but the request from my Linux VM didn't. (All of them got "Connection:
close", however). Is this a clue, or a red herring?


=== cURL from Linux VM ===
GET 
/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.qtvirtualkeyboard.win64_msvc2015_64/5.9.0-0-201705291821meta.7z
HTTP/1.1
Host: download.qt.io
User-Agent: curl/7.52.1
Accept: */*


=== cURL from Windows host ===
GET 
/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.qtvirtualkeyboard.win64_msvc2015_64/5.9.0-0-201705291821meta.7z
HTTP/1.1
Host: download.qt.io
User-Agent: curl/7.53.1
Accept: */*


=== QNAM, default settings, from Windows host ===
GET 
/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.qtvirtualkeyboard.win64_msvc2015_64/5.9.0-0-201705291821meta.7z
HTTP/1.1
Host: download.qt.io
Connection: Keep-Alive
Accept-Encoding: gzip, deflate
Accept-Language: en-AU,*
User-Agent: Mozilla/5.0


=== Google Chrome from Windows host ===
GET 
/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.qtvirtualkeyboard.win64_msvc2015_64/5.9.0-0-201705291821meta.7z
HTTP/1.1
Host: download.qt.io
Connection: keep-alive
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99
Safari/537.36
DNT: 1
Accept: 
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
Accept-Encoding: gzip, deflate
Accept-Language: en,en-AU;q=0.9


Anyway, it looks like this isn't a QNAM issue so I'll ask a qt.io web admin.

Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Does QNetworkAccessManager support HTTP persistent connections? (keep-alive)

[Sze Howe Koh]

On Thu, 26 Jul 2018 at 08:57, Sze Howe Koh  wrote:
>
> On Thu, 26 Jul 2018 at 05:44, Thiago Macieira  
> wrote:
> >
> > On Wednesday, 25 July 2018 10:22:19 PDT Thiago Macieira wrote:
> > > On Wednesday, 25 July 2018 07:52:13 PDT Marian Beermann wrote:
> > > > Correct. If you augment your debugging a little, it is easy to see the
> > > > server sending a "Connection: close" header:
> > > >
> > > > qDebug() << ... << reply->rawHeader("Connection");
> > >
> > > The question is whether the request had a "Connection: keep-alive" header.
> > > You need to check the Wireshark logs to see that.
> >
> > Or if the request was HTTP/1.1, which changed the Connection default to 
> > keep-
> > alive.
>
> The reply's "Connection" header was "close", and Wireshark's traces
> have no mention keep-alive.
>
> Explicitly setting the "Connection" header in the request had no effect:
>
> for (auto url : urls)
> {
> QNetworkRequest req(url);
> req.setRawHeader("Connection", "keep-alive");
> auto reply = nam.get(req);
> QObject::connect(reply, ::finished, [=]
> {
> qDebug() << reply->request().url();
> qDebug() << '\t' << "Reqst:" <<
> reply->request().rawHeader("Connection");
> qDebug() << '\t' << "Reply:" << reply->rawHeader("Connection");
> reply->deleteLater();
> });
> }
>
> Debug outputs:
>
> 
> QUrl("http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.win64_msvc2015_64/5.9.0-0-201705291821meta.7z;)
> Reqst: "keep-alive"
> Reply: "close"
> …
>
> Does this mean the server is ignoring the keep-alive flag? How do I
> check if QNAM is setting it correctly in the first place?

I think the comms was HTTP 1.1, because Wireshark showed "HTTP/1.1 200
OK(text/plain)"


Regards,
Sze Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Does QNetworkAccessManager support HTTP persistent connections? (keep-alive)

[Sze Howe Koh]

On Thu, 26 Jul 2018 at 05:44, Thiago Macieira  wrote:
>
> On Wednesday, 25 July 2018 10:22:19 PDT Thiago Macieira wrote:
> > On Wednesday, 25 July 2018 07:52:13 PDT Marian Beermann wrote:
> > > Correct. If you augment your debugging a little, it is easy to see the
> > > server sending a "Connection: close" header:
> > >
> > > qDebug() << ... << reply->rawHeader("Connection");
> >
> > The question is whether the request had a "Connection: keep-alive" header.
> > You need to check the Wireshark logs to see that.
>
> Or if the request was HTTP/1.1, which changed the Connection default to keep-
> alive.

The reply's "Connection" header was "close", and Wireshark's traces
have no mention keep-alive.

Explicitly setting the "Connection" header in the request had no effect:

for (auto url : urls)
{
QNetworkRequest req(url);
req.setRawHeader("Connection", "keep-alive");
auto reply = nam.get(req);
QObject::connect(reply, ::finished, [=]
{
qDebug() << reply->request().url();
qDebug() << '\t' << "Reqst:" <<
reply->request().rawHeader("Connection");
qDebug() << '\t' << "Reply:" << reply->rawHeader("Connection");
reply->deleteLater();
});
}

Debug outputs:


QUrl("http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.win64_msvc2015_64/5.9.0-0-201705291821meta.7z;)
Reqst: "keep-alive"
Reply: "close"
…

Does this mean the server is ignoring the keep-alive flag? How do I
check if QNAM is setting it correctly in the first place?


Regards,
Sze Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Does QNetworkAccessManager support HTTP persistent connections? (keep-alive)

[Sze Howe Koh]

Hi all,

Revisiting this topic after a hiatus. Thanks for confirming, Thiago and Hamish.

On 13 April 2018 at 10:08, Thiago Macieira  wrote:
> On quinta-feira, 12 de abril de 2018 15:44:54 PDT Sze Howe Koh wrote:
>> Can QNAM re-use a TCP connection for multiple HTTP requests?
>
> Yes. It's the default. You don't have to do anything to enable it.

In a quick test, I used 1 QNAM to download 12 files simultaneously.
(Windows 10 Pro x64 build 1803, using Qt 5.11.1 + MSVC 2015 32-bit)

In Wireshark, I expected to see my PC send 6 SYNs (because QNAM does 6
connections in parallel and re-uses connections) and 12 GETs (because
I'm downloading 12 files).

However, I saw my PC send 12 SYNs and 12 GETs. I also saw the server
send 12 RSTs, 1 after each file finished downloading. My
interpretation is that the server terminates the connection after each
GET, which prevents connection re-use. Is this expected?

Test code:

const QStringList urls
{

"http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.win64_msvc2017_64/5.9.0-0-201705291821meta.7z;,

"http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.win64_msvc2015_64/5.9.0-0-201705291821meta.7z;,

"http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.win64_msvc2013_64/5.9.0-0-201705291821meta.7z;,

"http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.win32_msvc2015/5.9.0-0-201705291821meta.7z;,

"http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.win32_mingw53/5.9.0-0-201705291821meta.7z;,

"http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.qtwebengine/5.9.0-0-201705291821meta.7z;,

"http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.qtwebengine.win64_msvc2017_64/5.9.0-0-201705291821meta.7z;,

"http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.qtwebengine.win64_msvc2015_64/5.9.0-0-201705291821meta.7z;,

"http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.qtwebengine.win32_msvc2015/5.9.0-0-201705291821meta.7z;,

"http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.qtvirtualkeyboard/5.9.0-0-201705291821meta.7z;,

"http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.qtvirtualkeyboard.win64_msvc2017_64/5.9.0-0-201705291821meta.7z;,

"http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/qt5_59/qt.59.qtvirtualkeyboard.win64_msvc2015_64/5.9.0-0-201705291821meta.7z;
};
QNetworkAccessManager nam;
for (auto url : urls)
{
auto reply = nam.get(  QNetworkRequest( QUrl(url) )  );
QObject::connect(reply, ::finished, [=]
{
qDebug() << reply->request().url() << reply->readAll().size();
reply->deleteLater();
});
}


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtQuick for mobile - any experience to share?

[Sze Howe Koh]

On 29 May 2018 at 06:39, René Hansen  wrote:
>
> I can't speak for IOS, but at least on Android, all Qt libraries are packed 
> inside the application apk as .so files, so no static linking there.
>
> It seems the "go-to" reply on the list and from Qt in general is, "just buy 
> the license". Somewhat shortsighted, but understandable as it is, Qt is a 
> business, out to make a profit. However, and as I'm surely not alone in 
> thinking, I really don't get this approach towards small-timers. The license 
> cost just isn't feasible for a lone couch coder with a pet project, who just 
> want to put a $1 proprietary app on the store. Most those kinds of apps never 
> make much sales anyway and Qt is quickly excluded from the list of candidate 
> frameworks, due to this perceived upfront cost.
>
> The side effect of supporting indie devs and tinkerers are a lot more 
> profound though. That is where the ecosystem grows. Bigger ecosystem = more 
> growth opportunity for the "business" down the line.
>
> It's a shame that many devs are left with the same impression as yourself, 
> and easily jump ship to React Native or similar. Qt could easily be the 
> defacto standard for mobile app development. It's just not the narrative 
> being supported by the Qt corp. Hence, you won't find any official guide or 
> writeup on how to publish a closed source LGPL paid app on the app store.
>
> As far as I can tell though, there's really no reason why you can't publish a 
> paid app, which is still compliant.
>
> You need to let people relink against other versions of Qt, but that simply 
> entails making object files available on request. If ever one is made...
>
>
> /René

Dynamic libraries are allowed from iOS 8 onwards:
https://stackoverflow.com/questions/4733847/can-you-build-dynamic-libraries-for-ios-and-load-them-at-runtime


Regards,
Sze-Howe


> On Mon, 28 May 2018 at 20:08 Sylvain Pointeau  
> wrote:
>>
>> My mistake, I understood the question was about to make my app GPL compliant.
>> I would agree with you for the desktop version but I don't think that it is 
>> feasible for a mobile app (is it not statically linked BTW?)
>> and I also understood the app store was not GPL friendly, but maybe my 
>> knowledge is outdated.
>>
>> Best regards,
>> Sylvain
>>
>> Le lun. 28 mai 2018 à 19:37, Jean-Michaël Celerier 
>>  a écrit :
>>>
>>> > I thought about it but that does not work for all projects, and I don’t 
>>> > see the business model in that case for my app.
>>>
>>> in which case would using Qt under the LGPL affect your business model ? 
>>> You don't have to publish your sources, only under the GPL.
>>>
>>>
>>>
>>>
>>> ---
>>> Jean-Michaël Celerier
>>> http://www.jcelerier.name
>>>
>>> On Mon, May 28, 2018 at 4:32 PM, Sylvain Pointeau 
>>>  wrote:


 On Mon, 28 May 2018 at 16:21, René Hansen  wrote:
>
> Or...
>
> Just make your app LGPL compliant and use Qt anyway.


 I thought about it but that does not work for all projects, and I don’t 
 see the business model in that case for my app.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QDatastream, QMap, QImage serialization

[Sze Howe Koh]

On 21 May 2018 at 17:08, Christian Gagneraud  wrote:
> On 21 May 2018 at 20:12, Jean-Michaël Celerier
>  wrote:
>>> Why is QImage even a GUI type? 99% of what I do with QImage is not for
>>> GUI. I can understand that QPixmap is GUI, but to me QImage is i/o and
>>> pixel/metadata manipulation (using scanline() where appropriate) . Yes,
>>> occasionally I use a QPainter on one, but that does not beed to be bound to
>>> a windowing system. A non-GUI raster painter would be sufficient.
>>
>> +1 (and also QColor ! plenty of command-line apps that work with colors :p)
>
> +1 (and also QPen and QBrush, they are (should be) just bundled properties)
>
> Once i wrote a graphical document format library (load, store and
> models), that could have not depend on GUI at all if it didn't use
> QColor, QPen, QBrush.

I agree that QColor, QRgb, QRgba64, QGradient (and its subclasses),
QGradientStop, and QPolygon are data types that are independent of
GUIs, so they can be simply moved out of the Qt GUI module if desired.

However, other classes can't be cleanly separated from Qt GUI (at
least without significant re-design) because:
* QPixmap is tied to system graphics resources
* QPaintDevice has the concept of "physical DPI" and "logical DPI"
which are GUI-related.

* QPainter depends on QPaintEngine which depends on QPaintDevice
* QPen depends on QBrush which depends on QPixmap
* QPen and QBrush are useless without QPainter
* QImage inherits QPaintDevice
* QRegion depends on QBitmap which inherits QPixmap


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QMetaMethod::invoke / Q_ARG with a temporary

[Sze Howe Koh]

On 8 May 2018 at 04:12, Giuseppe D'Angelo  wrote:
> Il 07/05/2018 20:24, Christian Ehrlicher ha scritto:
>>
>> I did not found a hint int the documentation about this behavior.
>> Therefore my question - should this work for a queued connection or not?
>> At least msvc2017 and gcc 4.8 don't like it when compiling with -O2...
>
>
> The documentation doesn't talk about QArgument, but about Q_ARG and
> Q_RETURN_ARG, which is what you should use.
>
> (Under the hood, the problem is that QArgument simply stores a pointer to
> your variable. If that variable is a temporary, that pointer becomes
> immediately dangling. For this reason, do not store what Q_ARG builds, e.g.
> in an variable declared auto!)

>From Qt 5.10 onwards, we can even do without Q_ARG (and QArgument).
Pass a function pointer or lambda expression to
QMetaObject::invokeMethod().


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Does QNetworkAccessManager support HTTP persistent connections? (keep-alive)

[Sze Howe Koh]

Can QNAM re-use a TCP connection for multiple HTTP requests?

This feature would be very helpful for
https://bugreports.qt.io/browse/QTIFW-1130


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] update to 5.10

[Sze Howe Koh]

On 3 February 2018 at 00:39, Dimitrios Anagnostakis
 wrote:
> Hi,
>
>
>
> I mean what repository do I need to include in the maintenance tool for
> updating Qt. The one from git didn’t work.
>
>
>
> Thanks a lot.

Hi Dimitrios,

You don't need to change or add repositories to update Qt. However,
the update process depends on how you installed Qt in the first place.

If you used the Offline installer, then you cannot use the Maintenance
Tool to update Qt. You must download the new installer for Qt 5.10.

If you used the Online installer:
1. If you also used the Qt SDK Repo Chooser
(https://github.com/JKSH/QtSdkRepoChooser), then you must re-run the
Chooser tool first. If you didn't use the Chooser tool before, ignore
this step.
2. Run the Maintenance Tool and select "Update components". You might
need to run this more than once, until there are no more updates.
3. Finally, select "Add or remove components". Here, you can add Qt
5.10 to your system.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How to make a looping element?

[Sze Howe Koh]

On 30 January 2018 at 03:07, Jason H  wrote:
>
> This is more like a rotation.. I'm looking for the other kind of rotation 
> where bearing % 360 can go from 359 to 1, without sweeping backwards while 
> animating the sweep.  Rather than sweep, I'd prefer to seek
> 090180270360
>  -->--> increase
> <-- sweep back (how can I avoid this?)

Two things come to mind:

1. Use relative moves instead of absolute moves. E.g. instead of "359°
to 1°", do "359° + 2°"
2. Support values <= 0° and >= 360°. E.g. instead of "359° to 1°", do
"359° to 361°". After the animation is done, you can normalize "361°"
-> "1°" (optional)


Regards,
Sze-Howe

> Sent: Monday, January 29, 2018 at 1:23 PM
> From: "Ola Røer Thorsen" 
> To: No recipient address
> Cc: "interestqt-project.org" 
> Subject: Re: [Interest] How to make a looping element?
> Try the RotationAnimation item and set the direction property to shortest.
> http://doc.qt.io/qt-5/qml-qtquick-rotationanimation.html
>
> Cheers,
> Ola
>
>
> Den 29. jan. 2018 kl. 02.15 skrev Jason H :
>
>
> I am trying to make a compass control, something that shows 0-360, like a 
> boat compass. It's got hash marks and numbers 350...0...10, etc. I have 
> something that largely works, but when the position crosses over 360 to 0, 
> the whole thing swings back around. It's very jerky, so I animate it, and 
> it's got that nice smoothness. I've tried to use complete() to make the 
> animation finish when it's a switch over, no luck.
>
> Does anyone have tips on how I can do this?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Tricky to download Qt online installer for 64-bit Linux

[Sze Howe Koh]

On 7 January 2018 at 06:02, Christian Gagneraud  wrote:
> On 7 January 2018 at 10:18, René J. V.  Bertin  wrote:
>> Christian Gagneraud wrote:
>>
 Uh... why do we provide a 32-bit installer in the first place, if we don't
 provide a 32-bit build of Qt?
>>>
>>> This one allows to install Qt/32bits on a 32bits PC, up to Qt-5.5.
>>
>> Lucky raskals, we on Mac get a "Maintenance Tool" for about all Qt5 versions 
>> but
>> that runs only on recent OS versions... and that will insist on updating 
>> itself
>> to a version that maybe won't run on the current host.
>
> We (Linux users) are not as lucky as you think, the two installers
> come with maintenance tools as well, but don't play together, you
> would have to install them side by side (not tested). One allows you
> to develop with Qt/32bits <= 5.5, while the other Qt/64bits >= 5.0
> The 32 bits comes with an old version of QtCreator, basically it's
> just a frozen version of the last official Linux-32 binaries.
> It might be useful for some thought.
>
> Anyway, there's definitely a bug on qt.io. Is anyone from the Qt
> Company aware of this?
>
>
> Chris

Another issue is that adblockers cause the download buttons to
disappear: https://forum.qt.io/topic/86525/cannot-find-the-download-link

I've pinged our Community Manager about the website issues (which can
also be reported at https://bugreports.qt.io/ under "Qt Project
Website")

As for the issues related to the design of the Online Installer for
Linux and macOS, I suggest creating reports under "Qt Installer
Framework"


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Contributing to Qt

[Sze Howe Koh]

On 30 Dec. 2017 16:12, "Igor Mironchik"  wrote:

Hello,

I want to contribute a little to Qt.

I cloned qtbase from git://code.qt.io/qt/qtbase.git

Created branch with

git branch test

git checkout test

made changes

git commit -a

Great but now I have a question: how should I correctly push my changes?

Provide a working example please.

Thank you.


Hi Igor,

The short version is: You need to set up your Gerrit account, add Git
hooks, and and configure your local repository to use the Gerrit remote
repository. Push your commits to the remote repository.

The exact details are a bit long. To get started, read through
https://wiki.qt.io/Qt_Contribution_Guidelines and
https://wiki.qt.io/Setting_up_Gerrit

Note: If you use the "init-repository" Perl script from qt5.git, it will
automatically set up the Git hooks and the remote repo for all Qt 5 repos
(not just qtbase.git). If you don't use this script, you will need to
manually configure every repo.

Finally, since this thread is about contributing to Qt, let's continue this
discussion at developm...@qt-project.org (remove interest@qt-project.org
when you reply)


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] qt.git: broken v5.6.0 .gitmodules?

[Sze Howe Koh]

On 11 December 2017 at 09:35, Thiago Macieira  wrote:
>
> On domingo, 10 de dezembro de 2017 14:50:33 PST Christian Gagneraud wrote:
> > > Use git submodule. Or just download the sources that match this tag.
> >
> > I'm thinking about downloading the source archives, but i'm not sure if
> > they contain absolutely everything, like:
> > - I need webengine from qt
>
> qtwebengine is part of the release tarballs as well as the repository. I don't
> know what you mean by "source archives" but it must surely mean one of those
> two. There is not third option.
>
> > - I need (ideally) qbs from qtc.
>
> That's not part of Qt. You can find qbs in the qbs releases.
>
> > For those interested, here is my (WIP) docker project:
> > https://gitlab.com/chgans/qtcreator-x86_32-docker-image
> >
> > I'm planning to add Qt-5.9 too.
> >
> > As a side note: My point about ini-repository broken script is that it
> > is a very bad experience as a paid-customer.
>
> The script is only meant for developers of the project itself. In that sense,
> you're neither a paid customer or an open source user: you're a Qt developer.
> Using that hat, you're going to check out the 5.6 branch, not a tag, and much
> less a non-current tag, at least until the time you're trying to fix a bug and
> prove a regression.
>
> That's why the script hasn't worked for a couple of years now for tag releases
> and no one has noticed. No one has needed that functionality until you, just
> now. And besides, there are alternatives and the correct one (git submodules,
> despite what the wiki says) is not known to have any problems.
>
> > Luckily i'm all in for the
> > "Qt Project/company", but new customer might be disappointed when they
> > realise that the build instructions/systems are out of date and/or broken.
>
> Don't blindly trust wikis. And do fix them if you run into issues.

I hope this helps clarify things:
https://wiki.qt.io/index.php?title=Building_Qt_5_from_Git=revision=32377=31996


> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center

Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Compiling the latest Qt versions post-5.10

[Sze Howe Koh]

On 22 October 2017 at 20:21, Jeffrey Brendecke
 wrote:
>
> On 21. Oct 2017, at 15:56, Jeffrey Brendecke 
> wrote:
>
> Is it possible to access the latest development branches for Qt versions
> after 5.10?
>
> If so, where do I get the source and are there compilation/installation
> instructions beyond what is found here:
>
> https://wiki.qt.io/Building_Qt_5_from_Git
>
>
> The process for cloning and checking out the dev branch goes fine until
> qtnetworkauth. At that point I am consistently prompted to authenticate,
> which does not succeed with my GitHub account.
>
> Do I need to be registered anywhere as a user in order to get access? I just
> want read-only access at this time.
>
> $ git clone https://github.com/qtproject/qt5.git --branch dev

No registration is required.


=== EXPLANATION ===
Some time ago, the libraries moved from https://github.com/qtproject/
to https://github.com/qt/.

So, https://github.com/qtproject/qt5.git now redirects to
https://github.com/qt/qt5.git (try it in your web browser). GitHub
takes care of the redirection when you clone.

However, Qt Network Authorization is a much newer module. It never
existed under the old qtproject account, so a redirection doesn't
exist. You can go to https://github.com/qt/qtnetworkauth.git, but
https://github.com/qtproject/qtnetworkauth.git gives error 404.


=== SOLUTION ===
If you edit your the qt5/.git/config file and set remote "origin" to
https://github.com/qt/qt5.git, you should be able to run the
init-repository script again. (You might need to use the --force
option)

If all that is too hard, you can also delete everything, clone
https://code.qt.io/qt/qt5.git (as recommended by the wiki), and run
init-repository from scratch.


> $ cd qt5
> $ git checkout dev
> $ perl init-repository
> --module-subset=default,-qtwebkit,-qtwebkit-examples,-qtwebengine
>
> Error message:
> + git clone --no-checkout https://github.com/qtproject/qtnetworkauth.git
> qtnetworkauth
> Cloning into 'qtnetworkauth'...
> Username for 'https://github.com': 
> Password for 'https://x...@github.com':
> remote: Invalid username or password.
> fatal: Authentication failed for
> 'https://github.com/qtproject/qtnetworkauth.git/'
> git clone --no-checkout https://github.com/qtproject/qtnetworkauth.git
> qtnetworkauth exited with status 32768 at init-repository line 198.
> Qt::InitRepository::exe('Qt::InitRepository=HASH(0x7f89f2803ff0)', 'git',
> 'clone', '--no-checkout', 'https://github.com/qtproject/qtnetworkauth.git',
> 'qtnetworkauth') called at init-repository line 534
> Qt::InitRepository::git_clone_one_submodule('Qt::InitRepository=HASH(0x7f89f2803ff0)',
> 'qtnetworkauth', 'qtnetworkauth.git', 0) called at init-repository line 407
> Qt::InitRepository::git_clone_all_submodules('Qt::InitRepository=HASH(0x7f89f2803ff0)',
> 'qt5', 0, 'preview', 'essential', 'addon', 'deprecated', '-qtwebkit',
> '-qtwebkit-examples', ...) called at init-repository line 644
> Qt::InitRepository::run('Qt::InitRepository=HASH(0x7f89f2803ff0)') called at
> init-repository line 655


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Interest Digest Wiki instructions for PI cross compile do not work for PostgreSQL support

[Sze Howe Koh]

On 19 October 2017 at 20:43, Roland Hughes  wrote:
>
> Scroll down and watch the video. QML is an 800 lb gorilla trying to ride in a 
> 2 cylinder car.
>
> http://www.logikalsolutions.com/wordpress/information-technology/raspberry-qt-part-12-qml-blows-big-stinky-chunks/


Roland,

Your code uses Qt Quick Controls 1, which was not designed with
embedded systems In mind.

Try again with Qt Quick Controls 2, which was designed for embedded
applications. You will see a marked improvement in performance and
resource consumption.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] strip: Customise Qt intaller, remove *.qt.io

[Sze Howe Koh]

On 29 September 2017 at 06:01, Christian Gagneraud  wrote:
> On 28 September 2017 at 22:34, Artem Sidyakin  wrote:
>>> I would like to disable some/most “*.qt.io" resources
>>
>> You can uncheck “unwanted” repositories in settings, and then installer will 
>> fetch only the stuff you need.
>>
>> For example, that’s how you get Qt Creator only:
>>
>> 1) https://i.imgur.com/EC9c6S5.png
>> 2) https://i.imgur.com/lteXbdm.png
>
> Thanks for sharing, appreciated.
>
> Still to get there i have to go first through "Preparing meta
> information download..." which takes a couple of minutes, I don't know
> why, but network speed sounds like a plausible cause.
>
> Chris

I just did a quick test on a PC without Qt installed. I'm in
Australia, and my current default mirror is ftp.jaist.ac.jp

During the "Preparing meta information download..." phase, Resource
Monitor told me that the data is crawling in at 10 Bytes per second
(yes, bytes), and it took a few minutes to get the meta info. However,
once I get past that stage, the actual Qt Creator files come in at
~300 KiB per second. Resource Monitor reports that both sets of
downloads came from the same mirror, so it's not just a connection
issue.

I wonder what's the reason for this huge discrepancy? Is it because
the meta information comes in as lots of tiny files?


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] strip: Customise Qt intaller, remove *.qt.io

[Sze Howe Koh]

On 28 September 2017 at 17:40, Kai Koehne  wrote:
>
> > -Original Message-
> > From: Interest [mailto:interest-bounces+kai.koehne=qt...@qt-project.org]
> > On Behalf Of Christian Gagneraud
> > Sent: Thursday, September 28, 2017 9:29 AM
> > To: interest@qt-project.org
> > Subject: [Interest] strip: Customise Qt intaller, remove *.qt.io
> >
> > Hi there,
> >
> > I would like to customise the Qt installer, not only by adding new
> > "resources", but i would like to disable some/most "*.qt.io"
> > resources.
> >
> > The reason for removing qt.io are multiples:
> > - From New Zealand, the Qt installer spends 5 to 10 minutes to fetch 
> > "*.qt.io"
> > stuff, and i'm getting tired of it (blame NZ, unfortunately), and i think 
> > it is
> > unacceptable for my potential users (co-workers).
> > [...]
> > PS: I have a Qt license, could this be useful on that topic?
>
> Please also raise this with Qt Support then. Maybe we just have to add 
> another mirror in the region then.

It's not that we're too far away from the available mirrors. Rather,
our link to our default mirror is slow. If I choose a different mirror
(e.g. by using the Qt SDK Repo Chooser [1]), speeds are fine.

---

QTIFW-441 [2] is reported as Done in v3.0.1.

I was under the impression that this feature would allow end-users to
manually select a mirror in the installer (see the comments under
QTIFW-441). However, after upgrading my Qt Online Installer, I still
don’t see a way to choose a mirror.

Could you please confirm if the ability to select a mirror has been integrated?


> Regards
>
> Kai

Regards,
Sze-Howe

[1] 
https://forum.qt.io/topic/43349/slow-downloads-with-the-online-installer-try-this-tool
[2] https://bugreports.qt.io/browse/QTIFW-441
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Online installer: How to properly remove old versions of documentation/examples?

[Sze Howe Koh]

On 19 June 2017 at 22:18, Kai Koehne <kai.koe...@qt.io> wrote:
>
> Hi,
>
> This sounds like a bug, please feel free to create a bug report.
>
> Anyhow, as a workaround you can launch the maintenance tool with the 
> --show-virtual-components argument. This will show you also packages that are 
> usually hidden in the user interface, because they should be automatically 
> enabled or disabled. You should be able to find any installed documentation 
> packages there and e.g. remove the "Qt 5.7 Examples".
>
> Regards
>
> Kai

Thanks, your workaround cleaned things up.

https://bugreports.qt.io/browse/QTIFW-986


Regards,
Sze-Howe

> > -Original Message-
> > From: Interest [mailto:interest-bounces+kai.koehne=qt...@qt-project.org]
> > On Behalf Of Sze Howe Koh
> > Sent: Monday, June 19, 2017 3:20 PM
> > To: interest@qt-project.org
> > Subject: [Interest] Online installer: How to properly remove old versions of
> > documentation/examples?
> >
> > Hello,
> >
> >
> > I'm running Windows 10 x64. My current "instance" of Qt has existed since
> > July 2015, although it has gone through numerous updates over the years.
> >
> >
> > I've just installed Qt 5.9 and uninstalled Qt 5.8. Months ago, I also 
> > uninstalled
> > all copies of Qt 5.5 and 5.7. I currently have Qt 5.4, 5.6, and 5.9 on my 
> > system.
> >
> >
> > While the headers and binaries for Qt 5.5, 5.7, and 5.8 are now gone, all 
> > their
> > documentation and examples are still there. Furthermore, because I had
> > installed Qt 5.7.0 but not 5.7.1, the "Update components" option in
> > MaintenanceTool.exe still prompts me to update the Qt 5.7 docs/examples
> > (even though I have no 5.7 binaries/headers anymore)
> >
> >
> > What's the proper way to uninstall the old docs/examples?
> >
> >
> >
> >
> > Thanks and regards,
> > Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Can the new Qt 5 (function pointer based) connections ever fail?

[Sze Howe Koh]

Someone posted the quested at http://stackoverflow.com/
questions/43487752/when-qt-5-will-fail-the-connect and I'm curious to know
the answer.

Since the connections are checked at compile-time, does that mean
QObject::connect() is guaranteed to succeed at run-time unless a duplicate
connection is attempted with Qt::UniqueConnection?


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QML WebView modules

[Sze Howe Koh]

On 4 April 2017 at 21:39, Nibedit Dey  wrote:
>
>
> Hi Mark,
>
> Qt WebEngine is only supported on desktop platforms.Hence Linux is supported.
> It's not supported on mobile platforms yet .So Qt 5.5.1 doesn't support.
> Refer: https://doc.qt.io/archives/qt-5.5/qtmodules.html
>
> To use WebView module, in pro file add:
> QT += webkit
> greaterThan(QT_MAJOR_VERSION, 4):QT+=webkitwidgets

The Qt WebView module is not related to WebKit.

Unfortunately, there are two different things named "WebView" in Qt,
which is very confusing:

* http://doc.qt.io/archives/qt-5.5/qml-qtwebview-webview.html
* http://doc.qt.io/archives/qt-5.5/qml-qtwebkit-webview.html


> For WebEngine module add:
> QT += webengine
>
> In both cases, Linux should be working.
>
> Regards,
> Nibedit
> .
>
>
> -- Forwarded message --
> From: Mark Tucker 
> Date: Tue, Apr 4, 2017 at 3:56 PM
> Subject: [Interest] QML WebView modules
> To: "interest@qt-project.org" 
>
>
> Hi,
>
>
>
> I'm currently trying to create a QML app that works on both a Linux platform 
> and an Android platform. Due to the nature of my target platforms (embedded 
> systems), I'm limited to Qt 5.5.1 and cannot upgrade.
>
> Note that my app is pure QML and I cannot write any C++ code to solve this.
>
> To get the app running on Android, I can put "import QtWebView 1.1" into my 
> QML file imports, and then create a simple WebView component and set its URL 
> and that works.
>
> That same import doesn't work for me on Linux, however. I can use either 
> "import QtWebKit 3.0" or "import QtWebEngine 1.1" (with the latter, changing 
> my WebView to a WebEngineView too) and I can then see a webview that works 
> with no issues, but neither of those are available on my Android target (nor, 
> from what I understand, will they ever be).
>
> So, is there a way I can get the QtWebView import working on Linux? I can't 
> seem to figure out how to build it, or if it's even a valid option.
>
> If not, then I guess that means I'll need to have different QML for both 
> Linux and Android…

When Qt WebView first started as a Tech Preview in Qt 5.4, it only
supported Android and iOS. These platforms were chosen specifically
because Qt WebKit and Qt WebEngine can't run on them.

In later releases, support for desktop platforms was added to Qt
WebView, but I'm not exactly sure which version. Qt 5.5 might be too
early.


> Thanks in advance
>
> Mark

Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] virus warnings

[Sze Howe Koh]

On 9 December 2016 at 07:28, Jocala  wrote:
> Windows 10 Defender is rejecting and deleting my QT 5.6 software. I know the
> end-user workarounds, and I know how to submit false positives. But this is
> happening every freaking time I do a new release. Software is deleted, users
> accuse me of distributing a virus.
>
> Is there anything I can do to prevent this from happening?  I'm using Qt 5.6
> and mingw49_32

You are not alone, e.g.:
https://us.battle.net/forums/en/hearthstone/topic/20752237958

There's not much that can be done on the Qt side. Some ideas that could help:

1. Add a prominent notice to your website to alert users about this
known issue and encourage them to update their virus definitions, so
that they don't get a nasty surprise
2. Keep submitting false positives, and encourage your users to do the same
3. Before publishing a release, test run your software on your own
Windows 10 machine with Defender, to see if it complains


> Defender says:
>
> Trojan:win32/Detplock
>
> The following error occurred: Error code 0x80508023. The program could not
> find the malware and other potentially unwanted software on this computer.
>
> Category: Trojan
>
>
> Description: This program is dangerous and executes commands from an
> attacker.
>
>
> Recommended action: Remove this software immediately.

Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Why is this a binding loop?

[Sze Howe Koh]

On 16 Nov. 2016 21:19, "Jason H"  wrote:
>
> > Il 15/11/2016 23:15, Jason H ha scritto:
> > > Rectangle {
> > > width: parent.width
> > > height: childrenRect.height * 2
> > > Text {
> > > text: "title"
> > > anchors.centerIn: parent
> > > }
> > > }
> > >
> > > 'QML Rectangle: Binding loop detected for property "height"'
> > >
> > > I think that computation should be possible without creating a
binding loop?
> >
> > * The height of the Rectangle depends on the size + the position of the
> > children
> >
> > * The position of the Text child depends on the size of the parent,
> > therefore it depends on the height of the parent
> >
> > Hence you've got a binding loop.
>
> Well, yeah. I guess there is some ambiguity of childrenRect. I'd figure
it's the bounding rect of the union of all the child areas, then offset
x,y. So using this reasoning, x,y, might not always be zero, but if
childrenRect is including the offset, then the x,y can only ever be zero,
and we get a binding loop.
>
> Here's what the docs say:
> """childrenRect group
> childrenRect.x : real
> childrenRect.y : real
> childrenRect.width : real
> childrenRect.height : real
>
> This property holds the collective position and size of the item's
children.
> This property is useful if you need to access the collective geometry of
an item's children in order to correctly size the item."""
>
> It's probably too late to change it, but I'm wondering if someone can
elaborate on why childrenRect.[width|height] includes the offset? It seems
that it would be useful to provide a parameter that provides the offset
unapplied to the rect.

I'm guessing it's because childrenRect is a QRect, which is a structure
that has always contained info about the position (offset) and size (width
& height) of a rectangle.

The related data structure that omits the position/offset is QSize.

Perhaps an additional property for Item might be useful? I can't think of a
good name for it though. (For consistency and non-ambiguity, the name for
such a property should not contain the term "rect")

Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Current QDataStream format documentation?

[Sze Howe Koh]

On 22 September 2016 at 23:11, Jason H  wrote:
> Nevermind. The trick does work. I have no idea what I did wrong. 
> http://doc.qt.io/qt-5/datastreamformat.html
>
> "qt5 serialization" is what I had to search for. The 5.x page never came up 
> in the Google results, only 4.8. I think we need to add something to the 
> Qt.io site that allows you to select the version?
> This 4.8 being first in results is getting annoying.

http://lists.qt-project.org/pipermail/interest/2016-September/024285.html


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] What don't you like about Qt?

[Sze Howe Koh]

On 19 September 2016 at 17:20, Michael Sué  wrote:
> Hi,
>
> - nothing new for widgets.
> - not yet full support for VS 2015, missing "Addin" that is, for more than a
> year now.
> - missing C++ support for mobile platforms.
> - unusable Docs for Qt3D.
>
> Best, Michael.

Hi Michael,

Regarding VS 2015, keep an eye on the Qt VS Tools:
https://blog.qt.io/blog/2016/08/11/from-visual-studio-add-in-to-qt-vs-tools-beta/
Add-Ins can no longer be used because Microsoft removed support for
them.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] What don't you like about Qt?

[Sze Howe Koh]

On 19 September 2016 at 01:14, Nate Rogers via Interest
 wrote:
>
> I'm a Linux user but a guy at work was trying out Qt on windows for a project 
> he was working on. He tried the new installer and it didn't come 
> preconfigured with a compiler like it used to. I didn't have time to trouble 
> shoot it so I just had him download 5.5 because that one works without any 
> messing around. Sorry I don't have more info
>
> Nate

Hi Nate,

For future reference: If you want an included compiler on Windows, be
sure to download the _MinGW_ based Qt. Regarding the availability of
"preconfigured"/bundled compilers, Qt 5.7 is actually the same as Qt
5.5.

Microsoft does not allow their compiler to be distributed by 3rd
parties, thus the Visual Studio (MSVC) based Qt cannot come bundled
with a compiler.


Regards,
Sze-Howe


> On Sun, Sep 18, 2016 at 1:05 PM, Freddy Martinez Garcia
>  wrote:
> Hi Nate, I’m a macOS user and I hate Windows, but right now I’m involve in a 
> big project developed with QML, Qt Widgets and C++ (because we have various 
> apps for desktop and mobile).
>
> In Windows I only had problem with the compiler from Visual Studio, which has 
> a lot of problem with the compatibilities with C++11/14 and we must use it 
> because MinGW (how in my opinion is much more better) has not support for Qt 
> Web Engine.
>
> What is your problem wit Qt 5.7 in Windows ? Just to know if I have the same 
> problem  my friend?
>
> regards
>
>
> =
> "El tamaño de tus logros depende del tamaño de tus metas."
> B.S. Computer Science
> Buenos Aires, Argentina
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Dealing with Qt 4.x docs in Google searches (Was: "What don't you like about Qt?")

[Sze Howe Koh]

On 18 September 2016 at 16:43, Jean-Michaël Celerier
 wrote:
>
> Some things that bother me :
>
> * The (perceived) lack of stability with QtQuick / QML : first there was 
> QtQuick with 4.8, then QtQuick 2.0, maybe QtQuick 3.0 with Qt 6 ? Then 
> Controls 1.0, then Controls 2.0 ... everytime with a somewhat short 
> life-span, which makes it a pain when looking for documentation or help, e.g. 
> on stackoverflow.
> * Features being QML-only instead of being usable from C++. I like coding in 
> C++ (but I agree it's hard).
> * Some features not really cross-platform (e.g. in QtMultimedia, 
> QAudioDecoder does not work everywhere, same for the 3D audio classes when 
> there is no OpenAL).
> * The goddamn 4.8 documentation still popping up prior to any other in google 
> search.

In my experience, this has improved significantly in the last year or so.

But if you're still encountering links to outdated docs, this Google
Chrome extension was created precisely to address that pain point:
https://forum.qt.io/topic/35616/chrome-extension-for-improved-doc-searches

It lets you filter Google searches such that only your specified
version of Qt is shown.


> * It's goddamn impossible to do any meaningful work with the QML designer, 
> every time in the change logs they state that it's becoming better, I drag 
> two random widgets and the thing crashes.
> * I agree for the FUD against licenses. But overall there is a lot of FUD 
> against the LGPL, not only Qt (e.g. "you can't statically link against LGPL 
> libs", yes you can). However, while I understand the need for the Qt company 
> to make licensing revenue, I don't think that alienating developers (hiding 
> the "OpenSource" part more and more in the website since the qt-project 
> merger) is the right way to do it.
> * I don't care a lot about moc, as Olivier Goffart has shown with Verdigris 
> it's either ugly macros or moc. And in CMake it's trivial to use anyway.
> However, I think that the Qt guys should *really* try to lobby the C++ 
> standard body's reflection working group so that when (if :'( ) there is 
> reflection in C++ 2α, Qt's meta object model can be implemented in terms of 
> it easily. This would make for something *very* powerful.
> * QString being UTF-16 :'(
>
> Some things that don't bother me at all but seems to bother a lot of people 
> on forums :
> * They expect Qt to be only a GUI toolkit, not a full-blown application 
> framework.
>
> But overall Qt rocks :p
> Best regards,
>
>
> ---
> Jean-Michaël Celerier
> http://www.jcelerier.name


Regards,
Sze-Howe


> On Sat, Sep 17, 2016 at 10:20 PM, Sérgio Martins  wrote:
>>
>> Hi,
>>
>>
>> It's not unusual for us developers and contributors to lose
>> perspective of what's important.
>> After many years spent on very particular implementation details, it
>> becomes difficult to see outside of the box.
>>
>> And because we already know the good aspects I'm asking only about the bad.
>> No need to discuss or reach an agreement, just go ahead and enumerate
>> what you don't like.
>>
>>
>> Personally, I don't know (too much time inside the box), but after
>> googling these came up frequently:
>>
>>
>> - C++ is difficult, Qt lacks quality bindings for mainstream languages
>> - moc (on build systems that don't automate this step)
>> - FUD around licensing
>>
>>
>>
>> Please state your top ones, even if it was already stated by someone
>> else, so we have an idea about which ones matter more.
>>
>>
>> Regards,
>> Sérgio Martins
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.6LTS vs 5.7+

[Sze Howe Koh]

On 5 September 2016 at 02:13, Roland Hughes  wrote:
> I just ran a simple QML project test on the Raspberry Pi:
> http://www.logikalsolutions.com/wordpress/information-technology/raspberry-qt-part-12-qml-blows-big-stinky-chunks/
> Yimminy is it a resource pig.

Would you be willing to re-run your test using Qt Quick Controls 2?

You can find relevant benchmarks for Raspberry Pi B+ at
http://blog.qt.io/blog/2015/03/31/qt-quick-controls-for-embedded/

See also http://blog.qt.io/blog/2016/06/16/qt-5-7-released/ -- "Qt
Quick Controls 1 were targeted at the desktop, and came with all the
bells and whistles required for desktop applications. This implied an
overhead that often made them too slow for usage on embedded devices.
Qt Quick Controls 2 solve these issues." The resource hog was not so
much JavaScript as the graphics stack.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Utilizing the GPU, how to start?

[Sze Howe Koh]

On 12 July 2016 at 14:53, John C. Turnbull  wrote:
> Thanks. I never thought of using Google ;-)
>
> Sadly Google shows me what *they* want me to see, not necessarily what I am 
> actually looking for.
>
> Hence asking the question here: amongst a group of Qt experts who are not 
> controlled by revenue-generating curating algorithms and who could point me 
> to the most appropriate articles for my questions.
>
> Thanks for the links. I will check them out and hopefully they will give me 
> the info I seek.
>
> -jct
>
>> On 12 Jul 2016, at 16:38, Mitch Curtis  wrote:
>>
>> Have you tried Google? :D These two links probably cover your first two 
>> questions:
>>
>> http://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph.html
>> http://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph-renderer.html
>>
>>
>>> -Original Message-
>>> From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org]
>>> On Behalf Of John C. Turnbull
>>> Sent: Tuesday, 12 July 2016 4:06 AM
>>> To: Uwe Rathmann 
>>> Cc: interest@qt-project.org
>>> Subject: Re: [Interest] Utilizing the GPU, how to start?
>>>
>>> Anyone?
>>>
> On 10 Jul 2016, at 23:23, John C. Turnbull 
 wrote:

 I am still new to Qt but am very interested in the technology and the
>>> deep innards of how it functions. I have worked in a 3D animation studio
>>> and learned a lot while I was there.

 Is there documentation or articles that:

 1) Describe in detail how the Qt Quick rendering pipeline is designed
>>> and how it operates.

 2) Describe the structure and overall architecture of the Qt Quick
>>> Scenegraph and how it is rendered?

 3) Describe the steps that have been taken so far and any further steps
>>> planned to optimise both (1) and (2)?

 I really want to know how all this hangs together as I may be able to
>>> further optimise and improve aspects of them.

 -jct

Hi John,

In addition to Mitch's links, these might also interest you as you
mentioned experience in a 3D animation studio:
* http://doc.qt.io/qt-5/qt3d-overview.html
* http://doc.qt.io/qt-5/qt3drender-framegraph.html

As for optimizations for Qt Quick, I think the Qt Company staff
members involved are in the best position to provide you with the
relevant info. Note that it is currently summer holidays in Norway, so
most of the staff are on leave till the end of July. Here's a small
peek at some of their recent work (although these are components built
on top of Qt Quick, rather than Qt Quick itself):
* http://blog.qt.io/blog/2015/03/31/qt-quick-controls-for-embedded/


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Sze Howe Koh]

On 22 June 2016 at 21:39, Jason H  wrote:
>
> > Subject: Re: [Interest] 5.8 Features?
> >
> > On 22 June 2016 at 09:34, Thiago Macieira  wrote:
> > >
> > > On terça-feira, 21 de junho de 2016 22:55:07 PDT Jason H wrote:
> > > > I feel like the last few releases have been run by the trolls, and not 
> > > > the
> > > > users of Qt. I was hoping open governance would enable the community to
> > > > direct Qt development, but I seem to have misinterpreted what it means.
> >
> > See https://wiki.qt.io/The_Qt_Governance_Model
> >
> > "Open governance" means that all members of the community can raise
> > proposals and vote on them. It is also a meritocratic system (as
> > opposed to democratic), which means more weight is given to members of
> > higher rank. Put simply, rank is gained through contributions and
> > commitment to the Qt Project.
>
> Where and when does this voting occur?

Where: Often at the Development mailing list:
http://lists.qt-project.org/mailman/listinfo/development
When: Whenever someone posts a proposal.

Examples:
* Proposal for choosing the list of platforms to support for Qt 5.8:
http://thread.gmane.org/gmane.comp.lib.qt.devel/24938/focus=24965
* Proposal for polishing and releasing QtSingleApplication:
http://thread.gmane.org/gmane.comp.lib.qt.devel/26279/focus=26358

My apologies, "voting" was the wrong word to use, as Thiago explained
in his email. Rather than counting votes, the process is a
discussion/debate where the proposals with the highest merit get
accepted.


> I've been vocal about improving Qt on mobile since mobile was an option. I've 
> been hardcore on the shortcomings for about 20 months. During that time, I 
> saw 5.6 get released, 5.7 get released at the same time as 5.6.1, and a lot 
> of meaningless (to me) modules added. And now 5.8 is only 1.5 months from 
> 5.7? What_the_hell? I'd like to see Qt complete it's mobile initiative.
>
> As for contributing, the past 20 months I've been under _multiple_ commercial 
> licenses, one that was paying for a Desktop just to use Qt Charts. I think 
> that's pretty material.

First of all, thank you for supporting Qt's development by purchasing
commercial licenses.

I'd imagine that funds from commercial licenses are normally allocated
to the development and maintenance of the entire Qt framework. Start a
conversation with your sales rep, and see if you can request greater
focus on specific areas. (Disclaimer: I'm not affiliated with the Qt
Company and I don't speak on their behalf, so please correct me if
this advice is inappropriate.)

Please remember: The Qt Company's commercial decision making process
and the Qt Project's Open Governance are _not_ the same thing. In the
context of Open Governance, "contribution" refers mainly to code
contributions. I don't have insight into the commercial decision
making process.

Anyway, as Tuukka pointed out in his email, Qt is making steady
progress in the mobile world (although "mobile" is still very broad,
and it sounds like the progress to date isn't in the areas that you're
interested in). There are multiple ways to get the mobile features
that you want, sooner:

* The open source community way: Get involved personally. Test,
review, and provide feedback for relevant patches, e.g.
https://codereview.qt-project.org/#/c/149602/ . If a patch gets
neglected, ping the list for more attention. Even better, write and
submit your own patches.
* The commercial customer way: Talk to your Qt Company sales rep
directly to try to influence their decisions.
* Use a ready-made 3rd party toolkit to complement official Qt
features, e.g. V-Play: http://v-play.net/
* Get 3rd party professionals on board to implement the specific
features that you want, e.g.
https://woboq.com/blog/qdockwidget-changes-in-56.html -- "You can hire
Woboq to fix your own Qt bugs or implement new features inside Qt"


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Sze Howe Koh]

On 22 June 2016 at 09:34, Thiago Macieira  wrote:
>
> On terça-feira, 21 de junho de 2016 22:55:07 PDT Jason H wrote:
> > I feel like the last few releases have been run by the trolls, and not the
> > users of Qt. I was hoping open governance would enable the community to
> > direct Qt development, but I seem to have misinterpreted what it means.

See https://wiki.qt.io/The_Qt_Governance_Model

"Open governance" means that all members of the community can raise
proposals and vote on them. It is also a meritocratic system (as
opposed to democratic), which means more weight is given to members of
higher rank. Put simply, rank is gained through contributions and
commitment to the Qt Project.

Regarding governance of new features, you can propose to add Feature X
to Qt. If nobody objects, that means you now have the green light to
implement and submit Feature X. (The normal review process still
applies.) You don't _have_ to make a formal proposal each time you
submit a patch, but it's strongly recommended when adding a large new
feature.


> > I'm
> > looking for what's going into 5.8.. not much listed on the releases page.
>
> Open governance allows developers of Qt, not users of Qt, to direct new
> features. I have added features to every version since 5.0 (inclusive) and
> have already submitted a few to 5.8. Open governance did not change the means
> for non-developing users to influence the progression.

To clarify Thiago's point, "Developers of Qt" refers to all
contributors, not just the Qt Company. You can become a developer of
Qt and direct new features simply by submitting, reviewing, and/or
testing code + documentation that pertain to the features you want.
For example, Qt 3D is now released mainly because KDAB poured
resources into its development [1].

Alternatively, you can achieve your goal indirectly by persuading
someone to develop the features that you want. For example, you can
persuade them by paying them [2], or by convincing them that it's
better to focus on Feature X instead of Feature Y or Bugfix Z.


Regards,
Sze-Howe

[1] https://blog.qt.io/blog/2016/06/16/introducing-qt-3d/
[2] https://woboq.com/blog/qdockwidget-changes-in-56.html
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] ApplicationWindow is not an Item?

[Sze Howe Koh]

On 16 June 2016 at 23:41, Jason H  wrote:
>
> I tried using Keys on an application window. I got an error that it is not an 
> item. While it's trivial to throw an item in, why isn't it an Item?

That's a design concept I wondered about too, but I think I've found
the answer: Because...

* An Item is something that can be painted and displayed inside a
window/viewport.
* An Item is a painting, but a Window is not; rather, it is a frame in
which paintings are inserted.
* Qt draws Items itself, while it relies on the operating system to
draw Windows.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] https://code.qt.io/qt/qt5.git

[Sze Howe Koh]

On 7 June 2016 at 00:26, Jason H  wrote:
>
> I'm getting a 404.
>
> It's referred to in https://wiki.qt.io/Building-Qt-5-from-Git

https://code.qt.io/qt/qt5.git is for git cloning. If you want to
navigate the repo in your web browser, go to
https://code.qt.io/cgit/qt/qt5.git/


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Are slots even needed these days?

[Sze Howe Koh]

On 17 March 2016 at 01:03, charleyb123 .  wrote:
> On Wed, Mar 16, 2016 at 10:57 AM, Giuseppe D'Angelo
>  wrote:
>>
>> Il 16/03/2016 17:24, charleyb123 . ha scritto:
>>>
>>> Current slot implementation bridges runtime-reflection capabilities
>>> (provided by QMetaObject), and provides the thread-safe event queue that
>>> bridges "slot-execution" to occur on the "target-thread" for which the
>>> "target-QObject" has "affinity".  Lambdas alone cannot do this -- some
>>> kid of "event-queue" would be required that is "thread-aware" (yes,
>>> could be provided through a library of some kind, that happens to be
>>> what Qt is doing).
>>
>>
>> This thread wasn't talking about lambdas, rather about the "old" connect
>> syntax (SIGNAL/SLOT based) vs the "new" one (PMF based).
>>
>> Anyhow, since you brought lambdas into discussion, you can pass an
>> affinity object for them as well:
>>
>>> https://doc.qt.io/qt-5/qobject.html#connect-5
>>
>>
>
> Ah, thanks:  I misunderstood the thread topic (sorry).  ;-)
>
> Agree that I don't have a use case for the "old" connect syntax anymore
> (fine with me to deprecate it).  I prefer catching errors at compile-time
> with the new syntax.
>
> I've "overheard" some discussions in other circles about ditching all of
> signal/slot in favor of lambdas, and apologies for dragging that into the
> discussion.  It's something I've been thinking about a lot ...   ;-)

There are two things that the new syntax doesn't support: (i) QML
connections, and (ii) default parameters. I haven't used (ii) myself,
but I definitely use (i).

See http://doc.qt.io/qt-5/signalsandslots-syntaxes.html for details.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Emitting signal from QThread::run()

[Sze Howe Koh]

On 28 February 2016 at 00:26, Alejandro Exojo  wrote:
>
> El Saturday 27 February 2016, Thiago Macieira escribió:
> > On sábado, 27 de fevereiro de 2016 11:45:50 PST Syam wrote:
> > > void MainWindow::someFunction()
> > > {
> > >
> > >MyThread *thread = new MyThread;
> > >connect(thread, SIGNAL(mySignal()), this, SLOT(myGuiSlot()),
> > >
> > > Qt::QueuedConnection);
> > >
> > >thread->start();
> > >
> > > }
> > >
> > >
> > > //
> > >
> > > Will the above code work fine? In myGuiSlot() I am typically manipulating
> > > some widgets - setting the text of a QLabel etc.
> >
> > Yes. The signal will be queued anyway.
>
> Will be queued without the explicit QueuedConnection? In other words, what
> does AutoConnection do here? run() is executed in another thread, but the
> QThread is in the same thread of MainWindow, right?

See http://doc.qt.io/qt-5/qt.html#ConnectionType-enum

"If the receiver lives in the thread that emits the signal,
Qt::DirectConnection is used. Otherwise, Qt::QueuedConnection is used.
The connection type is determined when the signal is emitted."

Qt checks to see which thread the signal is emitted from. Qt does not
check which thread the signal sender lives in.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] What happened to 5.5.1 branch?

[Sze Howe Koh]

On 6 February 2016 at 07:13, Jason H  wrote:
>
>
> > Sent: Friday, February 05, 2016 at 5:59 PM
> > From: "Thiago Macieira" 
> > To: interest@qt-project.org
> > Subject: Re: [Interest] What happened to 5.5.1 branch?
> >
> > Answering the subject: 5.5.1 is released, so it no longer needs a branch.
> >
> > On sexta-feira, 5 de fevereiro de 2016 23:32:09 PST Jason H wrote:
> > > Git issues:
> > > 1. I checked out the 5.5.1, and created a branch called
> > > osx_recording_params. SourceTree shows me the [osx_recording_params] in 
> > > the
> > > "SourceTree" window.
> >
> > Mistake. You should have checked out the 5.5 branch.
> >
> > > 2. Things were fine until 5.6 branch happened.  Now,
> > > the list of pre-5.6 branches is gone. $ git branch
> > > * (HEAD detached from c595fc7) # <- this was the 5.5.1 commit of
> > > qtmultimedia that I checked out. 5.6
> >
> > You were detached already. It just happened that the remote branch that you
> > happened to be detached from is now gone.
>
>
>
> Not sure why it got deleted. They are free.

It's free to keep it in the repository, but it adds noise to, say,
`git branch -r` (command line). The number of Qt versions only grows
over time.

Also, a branch is for making commits. Since no more commits are
accepted for Qt 5.5.1, it makes sense to remove the "5.5.1" branch.

If you want the 5.5.1, sources, you can check out the "v5.5.1" tag.


> And there are others. Now I'm always getting:
> 'git log' failed with code 128:'fatal: bad revision '(HEAD detached from 
> c595fc7)'
> with all my git actions.

That's a SourceTree issue, not a git issue. Here's an old, unresolved
bug report: 
https://answers.atlassian.com/questions/293099/git-log-failed-with-code-128-fatal-bad-revision-detached-from-35e6d4e

Here's what others have done to fix very similar errors:
https://answers.atlassian.com/questions/94201/error-encountered-on-source-tree-git-log-failed-with-code-128


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QuickModel - ORM for QML

[Sze Howe Koh]

On 18 November 2015 at 16:54, Daniel França  wrote:
> Hey Ben,
> I didn't know about qpm, sounds very interesting.
> I'll take a look on how to publish my project there.
>
> Thanks,
> Daniel
>
> Em ter, 17 de nov de 2015 às 18:08, Ben Lau  escreveu:
>>
>> Hi Daniel,
>>
>> Your project is interesting. Good Job. By the way, will you be interested
>> to publish it on qpm.io ?


You can also submit to http://inqlude.org/ which currently lists 3
other ORM related packages


Regards,
Sze-Howe

>> On 16 November 2015 at 06:35, Daniel França 
>> wrote:
>>>
>>> Hi guys,
>>> I've developed an ORM library for QML.
>>>
>>> The main intention was to use it for some of my projects, but as I've
>>> seen a lack of this kind of library for QML I'm making open-source on my
>>> github: https://github.com/danielfranca/quickmodel
>>>
>>> It's very simple and easy to use, basically it's only a single file that
>>> you can import in your project.
>>> The interface is inspired on Django ORM, so you can expect very similar
>>> method signatures:
>>> var artists_johnny = Artist.filter({name__like:
>>> ‘Johnny’}).limit(3).all();
>>>
>>> The documentation is available (but it's under construction) here:
>>> http://quickmodel.readthedocs.org/en/latest/
>>>
>>> Please let me know what you think about it, any feedback is welcome ;)
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] emulate windows 10 behaviour on a QT window

[Sze Howe Koh]

Hi Nicolas,

On 11 November 2015 at 05:57, Nicolas Jäger  wrote:
> Hi,
> I have to use QT5 on windows 10 (both are not my choice...), I wrote an ui 
> with QT, I have a
> borderless window and I use a widget to make the window bar. I can move the 
> window around the
> screen by clicking and holding the mouse button on that widget.
>
> Now, somebody asks me to emulate the same behaviour like usual windows do on 
> MS Window 10, e.g.
> when you got close of the top of the desktop, the window does an animation to 
> fullscreen it.

This feature is called "Aero Snap". It's designed with bordered
windows in mind, but I think hacks exist that emulate it in borderless
windows.

A quick search on Google for "borderless Aero Snap" yielded
http://stackoverflow.com/questions/16765635/aero-snap-with-borderless-window-in-qt
(Note: I have no experience with this myself, so I can't comment on
the quality of the proposed solution)


> I don't know how to do that, I'm not even sure I can do it. But I try to 
> figure if there is a way
> to do it with QT or if I can send some microsoft windows 10 event to force 
> the behaviour.
>
> I never wrote something for window neither for QT before, so it's quiet a 
> challenge for me.
>
> ps: not sure if the word emulate is a good choice
>
> regards,
> Nicolas Jäger

Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt interfacing to Android native UI ?

[Sze Howe Koh]

On 4 November 2015 at 22:51, Edward Sutton  wrote:
>
> I am having layout or other issues that make the mixed widget / qml not
> display well or at all on Android and iOS when Combining Qt Widgets and QML
> with QWidget::createWindowContainer() .  Hopefully that is something that is
> solvable else the mixed QML and C++ widget approach may be a dead-end.

There are known issues with QWidget::createWindowContainer().
QQuickWidget was introduced as a better alternative.


> I will continue reading Interacting with QML Objects from C++  with the goal
> of connecting a Tumbler added to Combining Qt Widgets and QML with
> QWidget::createWindowContainer()  to be readable and writable from C++.
>
> Thanks again Federico.
>
> -Ed


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt interfacing to Android native UI ?

[Sze Howe Koh]

On 4 November 2015 at 06:47, Edward Sutton  wrote:
> On Nov 3, 2015, at 4:24 PM, Federico Buti  wrote:
>
> On 3 November 2015 at 22:30, Edward Sutton 
> wrote:
>>
>> > On Nov 3, 2015, at 2:11 PM, Jason H  wrote:
>> >
>> >> Sent: Tuesday, November 03, 2015 at 10:12 AM
>> >> From: "Edward Sutton" 
>> >> To: "Qt Interest" 
>> >> Subject: [Interest] Qt interfacing to Android native UI ?
>> >>
>> >> I know I can use native iOS UI by mixing Objective-C++ and C++ in the
>> >> same *.mm file.
>> >>
>> >> I have done a little Android JNI.  Are there any examples for
>> >> interfacing to Android native UI elements?
>> >>
>> >> I need to create a UI picker for manually entering GPS latitude and
>> >> longitude in degrees,  or degrees, minutes, seconds for a widgets app.  I
>> >> expect it will be hard to make a touch usable widget UI picker.  
>> >> Developing
>> >> a native interface may take similar amount of time but result will be much
>> >> superior.
>> >
>> >
>> > >Define "much superior”?
>>
>> What the user expects. True native touch UI. Responsive and fast.
>>
>> >
>> > >Don't forget QML, which I think is the bee's knees. And then you have
>> > > one codebase for iOS and Android and Desktop, which to me is vastly
>> > > superior.
>>
>> Does QML have a numeric picker wheel ui element?
>
>
>>Since Qt 5.5 Tumbler is free.
>
>
> I just built and ran the Qt Quick Enterprise Controls and I saw tumbler.  I
> am glad it is free for others to use too.
>
> The PieMenu looked great too.
>
>
>  >Anyhow writing one in QML is quite easy using a PathView. Here is a
> component
>
>
> That was one of my concerns about QML.  Initially it looks like you could
> only use what Qt had created for you,  If something like a tumbler did not
> exist I assumed you were out-of-luck.  I need to research PathView and what
> it takes to create a new custom control.
>
>
>
>>
>> I have wanted to try creating UI elements in QML then display them in a
>> widget from my C++ Qt widget app.  I do not know if this is possible;
>> launching a QML ui then and receiving what the user selects from the QML UI.
>> It may be worth the effort.
>
>
>>
>> If I could mix some QML with my widget app it could be a better solution
>> compared to writing (and maintaining) two (2) native UI numeric pickers, one
>> for Android, and one for iOS.
>>
>>
>> So far I have one Qt widget codebase supporting Android, iOS, Linux, OS X,
>> and Windows desktops except for a few things like Bluetooth, sending email,
>> UIAlertView ( QMessageBox looks terrible on iOS ) and such.  If I start
>> adding native UI interfaces for Android and iOS I start to lose benefits of
>> Qt.
>
>
>>Mixing Qt Widget and QML is possible. Look at this blogpost.
>
>
> I just ran across that example.  It worked once I put the QML file into a
> resource.  However that example does not interact with C++.  I was hoping to
> find an example that would demonstrate how I could read the QML state from
> C++ ( or visa versa ).
>
> I assume ta QML toggle button could raise a toggled signal that a C++
> handler could react to?
>
> Or C++ could change the state of the QML toggle button?

See:
* 
http://doc.qt.io/qt-5/signalsandslots-syntaxes.html#connecting-c-objects-to-qml-objects
* http://doc.qt.io/qt-5/qtqml-cppintegration-topic.html


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] QML type checking quirk

[Sze Howe Koh]

I just found out (during the discussion at
https://forum.qt.io/topic/60021 ) that the following items all give a
height of 100:

// Initialization assignment
height: 100
height: "10" + "0"
height: "10" + 0
height: 10 + "0"

// Imperative assignment
height = "100"


However, this initialization assignment produces an error:

height: "100" // ERROR: "Invalid property assignment: number expected"


Is this intentional? Given that the first 5 examples are all legal,
shouldn't the last one be legal too?


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Creating pdf with QTextDocument with chart

[Sze Howe Koh]

On 24 October 2015 at 00:21, Duane  wrote:
> I need to create a document as a pdf file for my application.  I can use
> QTextDocument and html to do most of the document but I need to add a
> chart to it.
>
> I'm using Qt 4.8.  Any suggestions?

Hi Duane,

Try the Qt Widgets for Technical Applications library:
http://qwt.sourceforge.net/


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.5 DEB (or other install package) for Ubuntu 14.04 out there?

[Sze Howe Koh]

On 16 October 2015 at 04:33, Pau Garcia i Quiles  wrote:
>
> On Thu, Oct 15, 2015 at 10:23 PM, Jason Kretzer  wrote:
>>
>> Am I reading your response correctly?
>>
>> 1) I can install the Qt 5.5 Dev libs directly onto a machine to which I
>> want to deploy the app
>
>
> Technically, you will not be "installing" anything. You will be copying some
> files, which happen to be the Qt library files, to some system

To clarify, there is no difference between Qt "dev libs" and "end user
libs". They are one and the same.

OK, to be pedantic, developers also have Debug versions of each
library, which you would not give to an end user. The Release versions
of the "dev libs" are the ones that get packaged into apps' .deb files
-- these can also be copied directly to the deployment machine along
with your app executable, if you don't want to use a package manager.


Regards,
Sze-Howe


>> 2) I can create a DEB of the app that will point at those dev libs instead
>> of looking for the standard location? (/usr/lib/x86_64-linux-gnu  I think)
>>
>
> Yup
>
> In fact this turns out to be quite easy if you use CMake as the build
> system, CPack to generate the Debian packages with the binaries and the
> BundleUtilities.cmake module to get all the binaries and prerequisites
> together.
>
> https://cmake.org/Wiki/BundleUtilitiesExample
>
> (it uses GetPrerequisites.cmake internally)
>
>
>
>>
>> Is that correct?
>>
>> If that is not correct, is the above possible?
>>
>> -Jason
>>
>>
>> -Original Message-
>> From: Yuvraaj Kelkar [mailto:yuvr...@gmail.com]
>> Sent: Friday, October 09, 2015 11:18 AM
>> To: Jason Kretzer
>> Cc: interest@qt-project.org
>> Subject: Re: [Interest] Qt 5.5 DEB (or other install package) for Ubuntu
>> 14.04 out there?
>>
>> Qt5 libraries do exist on Ubuntu 14.04.
>> If you have built your deb on 14.04, then the debhelper should have put in
>> the correct dependency information.
>> If you build on a version > 14.04 and try to run on 14.04 then your
>> debianization scripts need to be explicit about versions.
>>
>> I used to do this by using a 14.04 VM. Now I use a 14.04 Docker image.
>>
>> -Uv
>>
>> On Fri, Oct 9, 2015 at 7:48 AM, Jason Kretzer  wrote:
>> > Basic question.  I have a Qt 5.5 application that I want to install and
>> > run on Ubuntu 14.04.  However, the most recent Qt libs are not available in
>> > the standard repos.  Anyone know where I can obtain such things?  My little
>> > application is to be distributed as a DEB file but fails on installation 
>> > due
>> > to the Qt lib version.
>> >
>> > Am I out of luck here and have to build my own or does such a repo exist
>> > somewhere that would obviously not only include the Qt 5.5 but their
>> > dependencies as well?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Is QObject::deleteLater() thread safe?

[Sze Howe Koh]

The function body simply calls the following, which is thread safe:

QCoreApplication::postEvent(this, new QDeferredDeleteEvent());

So, it looks like deleteLater() is safe to call from any thread. Are
there any technical or philosophical reasons not to do that?


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.5 DEB (or other install package) for Ubuntu 14.04 out there?

[Sze Howe Koh]

On 13 October 2015 at 05:54, Andreas Pakulat  wrote:
> Hi,
>
> On Mon, Oct 12, 2015 at 7:08 PM, Jason Kretzer  wrote:
>>
>> We are currently building on a 14.04 installation.  However, when I take
>> the DEB that is created to another pc with a stock installation of 14.04,
>> the DEB will not install since it relies on packages that are not available
>> through the repos.
>
>
> Are you building against Qt5.5 on that Ubuntu system? If so, where is that
> Qt 5.5 installation, how did it get there? If you can answer those questions
> you know where your users will find their Qt 5.5 to use your application.
>
>>
>> I am asking this question second hand, on behalf of a colleague, so I may
>> not be completely correct in the above.  The bottom line is that we are
>> stuck using a lower Qt version than we would like and do not know what we do
>> not know to make using Qt 5.5 happen.
>
>
> You may find more answers to the question wether some repository exists for
> Qt5.5 Ubuntu packages for Ubuntu 14.04 in an ubuntu forum/list as those
> providing such packages are more likely to lurk around there.
>
> Other options besides finding some repository would be linking your app
> statically against Qt, shipping the Qt libraries in a special subdir and
> using a shell script to setup the linker load path to include that directory
> or you create and provide such debs yourself.

For the "shipping the Qt libraries" option: Instead of using a custom
script to launch the application, you could just set the RPATH when
you compile. Just add something like this to your .pro file [1]:

QMAKE_LFLAGS += -Wl,-rpath,"'\$$ORIGIN'"


Regards,
Sze-Howe

[1] http://www.tripleboot.org/?p=138
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Using Qt as backend for plugin to be loaded on a host software

[Sze Howe Koh]

Hi,

On 16 September 2015 at 21:36, Nuno Santos  wrote:
> Hi.
>
> I’m developing a plugin to be loaded by a music software host (VST). There
> are some lighter alternatives to provide graphics, network and other kinds
> of useful resources but I want to use Qt. I simply Love Qt!
>
> When the plugin is open by the host, it provides a window ref to the plugin.
> On Window it is a HWND handle, on Mac it is supposedly a WindowRef.
>
> I have a working prototype for Windows. I don’t think it is all correct but
> its working. When the plugin is first started I check for the existence of a
> QApplication and start one if not.
>
> Then I create the main controller for my plugin and the QQuickView to draw
> on the window. To create the QQuickView i’m first creating a QWindow with
> the ptr to HWND handle as parent:
>
> window = QWindow::fromWinId((WId)ptr);
>
> view = new QQuickView(window);
> view->setSource(QUrl("qrc:/qml/vstmain.qml"));
> view->rootContext()->setContextProperty("controller", _controller);
> view->show();
>
> This is actually working quite well on Windows. The same strategy however,
> doesn’t work on a Mac. When I try to create a QWindow::fromWinId the result
> is a crash with the following stack trace:
>
> 2015-09-16 14:26:18.526 Live[91339:1091079] -[NSHIObject
> setPostsFrameChangedNotifications:]: unrecognized selector sent to instance
> 0x19806da0
>
> - The first question is: what is QWindow::fromWinId is expecting to be able
> to create a window? An NSView?
>
> - The second question is: the stack trace says that NSHIObject didn’t
> recognized the selector setPostsFrameChangedNotifications. What is a
> NSHIObject? I can only find references to HIObject from the HIToolbox and
> that belongs to the Carbon frame work. So far I haven’t been able to call
> Carbon methods inside my Qt environment even referencing -framework Carbon
>
> - Third question: On window I have an issue with the QApplication args and
> argv. On debug, there is an ASSERT that says that origArgc is different from
> the actual argc/argv. On release mode it crashes. Why does QApplication
> needs to receive the exact same arguments as the initial app?
>
> - Fourth question: how should I keep my run loop running without depending
> on the host? On Windows I have created a windows thread to call
> qApp->exec(). Although a warning that exec should be called on main thread
> it WORKS! How safe is this? Is there any other recommended option? What
> about Mac OS X?

I don't have experience with your other questions, but I know this one.

This approach works fine on Windows; I'm doing something similar in my
current project. Q(Gui)Application can be safely created in a non-main
thread. Just make sure that you all create all your GUI classes and
run their methods in that same thread.

However, this approach won't work on OS X. Cocoa requires all GUI
operations to be performed in the main thread:
http://stackoverflow.com/questions/9761953/running-a-cocoa-gui-in-a-non-main-thread.

For OS X, see the comments under the answer at
http://stackoverflow.com/questions/22289423/how-to-avoid-qt-app-exec-blocking-main-thread/22290909#22290909
-- Kuba Ober suggests a way to inject your Qt code into your main
thread. Note: I don't have a Mac, so I have never tested this myself.

Please let me know if it works, because I'd like to support OS X with
my project in the future.

(Note: One difference between my project and yours is that I only
create new windows in my plugin; I don't use Qt to manipulate an
existing window. I don't know if this will make a difference to you or
not.)


> I have been google a lot specially about the NSHIObject and I can’t find an
> answer, not even a simple lead. The closest I have is vstgui, a GUI
> framework for VST plugins that has open source code and support for Carbon
> and Cocoa backends but the NSHIObject is intriguing me because I can’t find
> any explicit reference on how to deal with it.
>
> Any thoughts would be high appreciated.
>
> Thanks in advance,
>
> With my best regards,
>
> Nuno


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Need argumentative help..... giving qobject copy/assignment constructor and put it in qlist/qmap

[Sze Howe Koh]

On 24 July 2015 at 01:28, Thiago Macieira thiago.macie...@intel.com wrote:
 On Thursday 23 July 2015 16:05:44 Guido Seifert wrote:
  Op 23-7-2015 om 08:42 schreef Thiago Macieira:
   Q_GADGET has existed since 4.0.
 
  Sure, but it was undocumented API.

 Not quite. It was badly documented API. I think it was mentioned in the 4.8
 docs in the Q_OBJECT section.

Well, I'll be! Never noticed that.


 What's new in 5.5 is the ability to register gadgets in QML.

So Guido, would your problem be resolved by converting your
QObject-in-a-container to a Q_GADGET-in-a-container?


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Need argumentative help..... giving qobject copy/assignment constructor and put it in qlist/qmap

[Sze Howe Koh]

On 23 July 2015 at 01:03, Guido Seifert warg...@gmx.de wrote:
 - the QObject's connections? Will all copies emit the same signals, will 
 all copies have their slots called?

 Worked somehow... probably through magic.

 This was my problem. It really looked like we could get away with it. The 
 whole class did not really need to be a
 QObject. It was only a QObject because it was used from QML. The whole design 
 was questionable.

Qt 5.5 introduced Q_GADGET for this purpose. What's more, you can
safely store a Q_GADGET inside a container.

Note that Q_GADGET doesn't support signals and slots though.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Is there a well-defined relationship between QScreen and QDesktopWidget?

[Sze Howe Koh]

Hello,

Is it safe to assume that, for a given value of 'i',
QGuiApplication::screens()[i] and QDesktopWidget::screen(i) refer to the
same physical screen?


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Restoring ICU to Qt 5.5 on Windows

[Sze Howe Koh]

Hello,

Qt 5.5 removed the dependency on ICU for the default Windows builds
(QTBUG-38259). This move is welcomed by many developers.

Now, I find myself in a rare position where I'd like to bring ICU back
for its codec support, which probably means I have to do a custom
build of Qt. I'd like to avoid building the entire framework if
possible. Can I simply take the official binaries and replace
Qt5Core.dll? Or do I need to ship custom versions of other Qt DLLs
too? (Assume that my compiler is compatible, and I won't ship WebKit)

Thanks!


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Audio file metadata?

[Sze Howe Koh]

Hi,

On 4 June 2015 at 07:13, John Weeks j...@wavemetrics.com wrote:
 Does anyone know if it's possible to use QAudio to get metadata from an audio 
 file? Info like the channel layout or embedded comments?

 -John Weeks

Not QAudio. See QMetaDataReaderControl instead:
http://doc.qt.io/qt-5/qmetadatareadercontrol.html


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Finding the root QQuickItem in a QQml(Application)Engine

[Sze Howe Koh]

Hello,

Is there an analogue of QQuickView::rootItem() for QQml(Application)Engine?

The shortest way I could think of involves jumping through a few hoops,
e.g.:

QQmlApplicationEngine engine;
// ...
auto window = engine.rootObjects().first();
auto aQuickItem = qobject_castQQuickItem*(window-children().first());
auto rootItem = aQuickItem-parentItem();


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Finding the root QQuickItem in a QQml(Application)Engine

[Sze Howe Koh]

On 11 May 2015 at 23:47, Ben Lau xben...@gmail.com wrote:

 On 11 May 2015 at 21:06, Sze Howe Koh szehowe@gmail.com wrote:

 Hello,

 Is there an analogue of QQuickView::rootItem() for QQml(Application)Engine?

 The shortest way I could think of involves jumping through a few hoops, e.g.:

 QQmlApplicationEngine engine;
 // ...
 auto window = engine.rootObjects().first();
 auto aQuickItem = qobject_castQQuickItem*(window-children().first());
 auto rootItem = aQuickItem-parentItem();


 Regards,
 Sze-Howe

 Hi,

 I use this piece of code to find the root QQuickItem (part of my test suite):

 engine.load(url);

 QObject *rootObject = engine.rootObjects().first();


 QQuickWindow *window = qobject_castQQuickWindow*(rootObject);

 if (window) {

 setTestableRootObject(window-children().first());


Thank you for your suggestions, Ben and Gunnar!

To clarify, I was after the invisible root item that a QQuickWindow
creates. Currently, this is implemented (privately) as a
QQuickRootItem:
http://code.woboq.org/qt5/qtdeclarative/src/quick/items/qquickwindow_p.h.html#QQuickRootItem

If the top-level item is a Window/ApplicationWindow which has
contents, then engine.rootObjects().first()-children().first()
returns the first QQuickItem inside the Window/ApplicationWindow.
However, this is actually not the root item. You can find the true
root by calling

qDebug() 
qobject_castQQuickItem*(engine.rootObjects().first()-children().first())-parentItem()


My use-case is to dynamically add items from C++, as siblings of the
existing QQuickItems.


 } else {

 setTestableRootObject(rootObject);

 }

Is this case valid? IIRC, QQmlApplicationEngine requires a
Window/ApplicationWindow at the top-level in order to display
anything.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Again this problem but now on Linux

[Sze Howe Koh]

On 4 May 2015 at 11:43, Hamish Moffatt ham...@risingsoftware.com wrote:

 On 04/05/15 13:08, Nikos Chantziaras wrote:
  On 03/05/15 13:54, Igor Mironchik wrote:
  Hi guys,
 
  I asked before about similar problem on Windows but now I have the same
  problem on Linux.
 
  I have messagebox.cpp file that should be moced, and in the end of the
  file I do #include messagebox.moc
  Since you're using qmake, you shouldn't include that. Manual inclusion
  of moc files should only be done when using build systems that are
  unable to do the moc'ing and building on their own. qmake does not need
  that.
 
 Oh, is that documented somewhere? We #include moc_foo.cpp for almost
 everything (though they get forgotten occasionally), but we're compiling
 with VS, Xcode and gnu make and none of those should need it. Is there a
 benefit to changing?

The documentation doesn't say that you *shouldn't* do something, but
see http://doc.qt.io/qt-5/moc.html -- it says that moc processes
*header* files.

If you define your classes in .h files (not .cpp files) and run qmake,
then you don't need to #include anything that moc produces.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QJSEngine and error line

[Sze Howe Koh]

On 7 April 2015 at 17:31, Joerg Bornemann
joerg.bornem...@theqtcompany.com wrote:

 On 07-Apr-15 09:59, Dominique Fober wrote:

  I'm using the new QJSEngine and I'm trying to get the error line number (in 
  case of error of course).
  Currently I'm handling errors as documented:
 
if (result.isError()) result.toString().toUtf8() ...
 
  but actually, the string is very poor: e.g. SyntaxError: Syntax error
  I would like to get at least a line number. Contextual information would be 
  also welcome.
  Is it possible with the QJSEngine? (I'm using Qt 5.3.0)

 Try to access the properties message, fileName and lineNumber.

 if (result.isError())
  qDebug()  result.property(fileName).toString();

Ooh, this is news to me.

I think we should document this somewhere, if it isn't already done (I
searched but couldn't find anything). I'm happy to volunteer if
necessary. Could you please provide a list of built-in properties of
various QJSValue types?

Also, what do you think of some API that returns a list of available
properties? (similar to QObject::dynamicPropertyNames() )


 result is a JavaScript Error object iff isError returns true.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Can't login to new forum

[Sze Howe Koh]

Hi,

On 3 April 2015 at 01:27, Jason H jh...@gmx.com wrote:
 To create a Qt Account, you can go to the Qt Forum login page, click on the 
 Qt Account check mark and get directed to the Qt Account login page. There at 
 the bottom of the page, you will find a ‘Create new account’ link.

 Nope.

 I click the check and get Welcome
 This is your first login, please set a username. Continue

 I enter in my Public name...

 Public name
 Name already in use.

 I can't find a way to recover my password either.

Go to https://login.qt.io/login -- there is a Forgot password? link.

You old email+username combo is copied from the old forums. If you
have created a new account with a different email, contact Tero Joko
(our Community Manager) and he'll merge your accounts for you.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Deploying QMultimedia

[Sze Howe Koh]

On 28 March 2015 at 16:31, Bernhard priv...@bernhard-lindner.de wrote:
 Yes that quick and dirty way is what I did. Aka try-and-error. But apart
 from the that it is kind of unprofessional there may arise compatibility
 problems. The fact that the software runs on my system with the chosen
 plugins does not make sure that it runs on other systems too.

Did you follow Step #3 in the wiki? If not, your application most
likely loaded DLLs from your dev folder which were missing from your
app folder.


 Maybe it needs different plugins in different situations?

As long as you distribute the same executable and DLLs to all of your
users, your application will always try to load the same Qt plugins.
The requirements on the Qt side won't change.

However, the multimedia plugins are a bit complicated because some
features are OS-dependent. For example, Microsoft didn't provide XP
support in Windows Media Foundation, so you can't deploy wmfengine.dll
to XP machines. And if I'm not mistaken, WMF only partially supports
Vista too.


 I refuse to include them all only for being on the safe side.

Agreed, that's a bad way to do things.


 It would be nice to know more about the plugins.

You might be interested in https://wiki.qt.io/Qt_Multimedia_Backends


Regards,
Sze-Howe


 -Ursprüngliche Nachricht-
 Von: interest-bounces+private=bernhard-lindner...@qt-project.org
 [mailto:interest-bounces+private=bernhard-lindner...@qt-project.org] Im
 Auftrag von Sze Howe Koh
 Gesendet: Samstag, 28. März 2015 01:11
 An: Nikos Chantziaras
 Cc: interest@qt-project.org
 Betreff: Re: [Interest] Deploying QMultimedia

 On 28 March 2015 at 03:22, Nikos Chantziaras rea...@gmail.com wrote:
  On 27/03/15 15:02, Bernhard wrote:
  Hi!
 
  Is there some document that explains which files (plugins, DLLs)
  needed to deployed when using Qt Multimedia (more precisely playing
  sound files using QMediaPlayer)?
 
  I'm not aware of a documented list, but I've found out here is that
  the Qt plugin for this is named dsengine (I think that stands for
  DirectShow Engine).

 Yes, dsengine stands for DirectShow Engine. There are other possible
 backends though, like the Windows Media Foundation Engine.

 Look inside Qt/plugins/mediaservice/ and possibly Qt/plugins/audio/.

 I don't think there's an official list, but here's a quick and dirty way
 to find out
 which ones you need:
 https://wiki.qt.io/Deploy_an_Application_on_Windows


 Regards,
 Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Deploying QMultimedia

[Sze Howe Koh]

On 28 March 2015 at 03:22, Nikos Chantziaras rea...@gmail.com wrote:
 On 27/03/15 15:02, Bernhard wrote:
 Hi!

 Is there some document that explains which files (plugins, DLLs) needed to
 deployed when using Qt Multimedia (more precisely playing sound files using
 QMediaPlayer)?

 I'm not aware of a documented list, but I've found out here is that the
 Qt plugin for this is named dsengine (I think that stands for
 DirectShow Engine).

Yes, dsengine stands for DirectShow Engine. There are other possible
backends though, like the Windows Media Foundation Engine.

Look inside Qt/plugins/mediaservice/ and possibly Qt/plugins/audio/.

I don't think there's an official list, but here's a quick and dirty
way to find out which ones you need:
https://wiki.qt.io/Deploy_an_Application_on_Windows


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Executing a small function as a thread

[Sze Howe Koh]

Hi,

On 17 March 2015 at 23:06, Syam Krishnan sya...@gmail.com wrote:
 On 03/17/2015 08:03 PM, André Somers wrote:
 Might I suggest a third method? Use QtConcurrent::run(yourFunction)
 instead.

 The documentation on QtConcurrent::run() says
 Note that the function may not run immediately; the function will only
 be run when a thread is available.

These threads are part of the global thread pool. The documentation
means, *if you are currently using all available threads in the pool*,
then QtConcurrent::run() will wait until one of those threads finish
before running. However, since you only want one instance running at a
time, then it's not a problem -- your function will run immediately.


 That is not acceptable to me. I am looking for the simplest solution
 that has the least overhead.

QtConcurrent::run() is the simplest solution available.

QtConcurrent uses QThreadPool internally. One of the reasons
QThreadPool was created was to reduce the overhead of starting new
threads.


 And I should have mentioned that only one instance of do_something()
 must be executing at any time.
 I am using QAtomicInt to control calls to this function. So when a
 second event is raised, it will check if
 the thread is already executing. If it is, it will wait till the thread
 execution is complete.

Yes, that is compatible with QtConcurrent::run().


 And I'm using Qt 4.8 on Linux.

 Syam

Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Executing a small function as a thread

[Sze Howe Koh]

On 17 March 2015 at 23:39, Syam Krishnan sya...@gmail.com wrote:
 On 03/17/2015 08:51 PM, André Somers wrote:
 Well, in any multi-threaded programming, you basicaly have no control
 over when something runs. That's up to the OS, not you. It will usually
 be soonish, but...

True. The only time when I've experienced non-soonish behaviour
though is when a non-real-time OS is under heavy load, which means
everything gets significantly delayed anyway.

snip

 Well, my situation already needs me to poll objects periodically.
 The following is indicative of my problem:

 while(1)
 {
for(all_objects)
{
   ret = object[i]-execute()
   if(ret == complete) all_objects.remove( object[i] );
}

sleep(1ms);
 }

 Now, object::execute() is supposed to get its work done by calling
 do_something().
 execute() should not block but do_something() is blocking. That's why I
 need to call it in a separate thread.
 Till do_something() completes, subsequent calls to execute() shall
 return a value indicating that it's execution
 is not complete, so that it will not be removed from the list of objects
 (all_objects).

Does execute() do anything else besides call do_something(), and does
your while-loop do anything else before sleeping? If not, what you
really want is for QtConcurrent::map() to call
execute()/do_something() on every object in your container.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Kicking out QtScript completely

[Sze Howe Koh]

Hi,

On 17 March 2015 at 23:50, Frank Hemer fr...@hemer.org wrote:
 On Tuesday 17 March 2015 15:17:31 Koehne Kai wrote:
  -Original Message-
  From: interest-bounces+kai.koehne=theqtcompany@qt-project.org
  Subject: Re: [Interest] Kicking out QtScript completely
 
  Hi,
 
   So am I the only one who cares about QtScript?
   Am I the only one who still doesn't use (and even want) QML?
 
  I also support an application that I will have to maintain for years
  (health care - 15 years min.) - and yes - it depends on QtScript and I
  don't see the new QJSEngine API support all my needs.

 Have you already filed the features you miss (either to Qt Support, or to
 the bugtracker)?

 Last time I seeked the tracker, I didn't find the right place - I've been told
 on dev days that there is a report being used for this but didn't manage to
 find it:-(

1. Sign in to https://bugreports.qt.io/
2. Click Create
3. Select Project: Qt, Issue Type: Suggestion, Components: QML
Engine (there's no dedicated category for QJSEngine, but it's
developed by the same folks who work on the QML engine)
4. Enter your other details and submit
5. Post a link to your report back here, to get votes from others who
are interested


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] [Development] New Qt Wiki Now Available

[Sze Howe Koh]

On 26 February 2015 at 23:05, Kojo Tero tero.k...@theqtcompany.com wrote:
 Hello,



 We just opened the new Qt Wiki at http://wiki.qt.io



 You can find the details in the blog post:

 http://blog.qt.io/blog/2015/02/26/new-qt-wiki-now-available/



 In short, it’s a mediawiki instance, you use Qt Account to log in for
 editing,

 and the content has been migrated from the old wiki.

 And as a the content is imported, it needs cleaning up. Please help us out
 in going through the content and fixing it.

I notice there's an Updated Pages page to track cleanup progress:
https://wiki.qt.io/index.php?title=Updated_pages

May I suggest doing the other way round? Apply a cleanup required
tag to every page, and have people remove the tag after cleanup. That
way, people who want to help with the cleanup can quickly see where to
direct their efforts.

Something like http://en.wikipedia.org/wiki/Template:Cleanup , tied to
a Tracking Category:
http://en.wikipedia.org/wiki/Category:All_pages_needing_cleanup


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] question about moveToThread docs

[Sze Howe Koh]

Hi,

On 11 February 2015 at 06:48, Alan Ezust alan.ez...@gmail.com wrote:
 from the documentation of QObject::moveToThread():

 \note A QObject's member variables \e{do not} automatically become
 its children. The parent-child relationship must be set by either
 passing a pointer to the child's \l{QObject()}{constructor}, or by
 calling setParent(). Without this step, the object's member variables
 will remain in the old thread when moveToThread() is called.

 Is this talking about member variables of type QObject ?
 As in, subobjects ?

It is talking about member variables of type QObject* -- pointers to
QObject. I believe that's the recommended practice.


 subobjects of type QObject that also have a parent set, might get destructed
 twice, but is that what this above paragraph is recommending?

They won't get destructed twice if your member variable is a pointer,
rather than the full object.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] question about moveToThread docs

[Sze Howe Koh]

On 11 February 2015 at 07:34, Sze Howe Koh szehowe@gmail.com wrote:
 Hi,

 On 11 February 2015 at 06:48, Alan Ezust alan.ez...@gmail.com wrote:
 from the documentation of QObject::moveToThread():

 \note A QObject's member variables \e{do not} automatically become
 its children. The parent-child relationship must be set by either
 passing a pointer to the child's \l{QObject()}{constructor}, or by
 calling setParent(). Without this step, the object's member variables
 will remain in the old thread when moveToThread() is called.

 Is this talking about member variables of type QObject ?
 As in, subobjects ?

 It is talking about member variables of type QObject* -- pointers to
 QObject. I believe that's the recommended practice.


 subobjects of type QObject that also have a parent set, might get destructed
 twice, but is that what this above paragraph is recommending?

 They won't get destructed twice if your member variable is a pointer,
 rather than the full object.

Assuming that you don't try to manually delete it, of course.

And actually, if a member variable is set as the child of the outer
QObject, then it's safe to store the full object instead of a
pointer, because of the destruction order is well-defined. (i) Member
variables get destroyed first, and only after that does (ii) the
outer QObject get destroyed.

When a QObject is destroyed, it removes itself from its parent's list
of children. That's what happens in (i). So, when (ii) happens, the
outer QObject does not call its children's destructors a second
time.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Tabbed toolbar

[Sze Howe Koh]

Hi,

On 30 January 2015 at 13:20, Christian Gagneraud chg...@gna.org wrote:
 Hi,

 I would like to manage tool/actions using an advanced toolbar system,
 on this visual [1] they call it tabbed command manager
 The issue is not much the tabification of the toolbars, but instead the
 layout of the tool buttons as QToolBar doesn't support displaying
 buttons in a grid (multi-line)

 Does anyone knows of open source implementations of such tabbed command
 manager? Or maybe any tips on how to achieve this?

 Thx,
 Chris

 [1] http://www.solidsmack.com/wp-content/uploads/2007/06/sw08-018.jpg

That's commonly called a Ribbon:
http://en.wikipedia.org/wiki/Ribbon_%28computing%29

I don't know of any open-source implementations, but QtitanRibbon is a
mature commercial package:
http://www.devmachines.com/qtitanribbon-overview.html


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] porting to Qt 5.4 - MOC very slow on Windows

[Sze Howe Koh]

On 15 January 2015 at 14:33, Hamish Moffatt ham...@risingsoftware.com wrote:

 I'm trying to port our app from Qt 4.8 to 5.4. Currently working in MSVC
 2013, and using the pre-built Qt binaries for that environment.

 We have about 440 files being MOCed during build. On 5.4, each file is
 taking 2-3 seconds meaning the overall build is significantly longer
 than in 4.8.

 I found a reference to a similar problem here -
 http://qt-project.org/forums/viewthread/47901 - which was due to using
 MOC on a network drive. In my case everything is on local SSD.

 Any suggestions?

What happens if you disable your antivirus?


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Testing new QML QtWebView 1.0

[Sze Howe Koh]

Hi,

On 6 January 2015 at 16:44, Harri Pasanen ha...@mpaja.com wrote:

 On 06/01/2015 08:35, Harri Pasanen wrote:

 Hi,

 I'm looking at Qt5.4.0/Examples/QtWebView/1.0/webview
 example on Android.

 It seems that documentation for it is wrong.
 http://doc.qt.io/qt-5/qml-qtwebkit-webview.html
 mentions

 Import Statement: import QtWebKit 3.0

 yet the example has

 import QtWebView 1.0

 (note that QtWebView has a red underline in editor)

 Also the doc promises loadHtml() method, but that does not seem to exist.

 I'm not sure what is going on, perhaps some confusion with QtQuick1 WebView 
 which I believe was completely different, based on WebKit?

 Also, I believe I saw something go by looking like on desktop WebEngine would 
 be used to implement WebView?

I don't think so. Qt WebEngine provides a full web engine based on
Chromium, and is only available .

Qt WebView provides a wrapper for the native web engine on mobile
platforms. This module was introduced mainly because mobile platforms
have security restrictions that prevent Qt WebEngine from running, so
it doesn't make sense to implement Qt WebView in terms of Qt
WebEngine.


 Searching in bugreports is a bit tedious as the name has been recycled, 
 adding to the confusion.

Yeah, recycling the name wasn't such a bright idea... Is it too late
to change this??


 Any guidance?

 Harri


 Ok, I think the correct documentation is here:

 http://doc.qt.io/qt-5.4/qml-qtwebview-webview.html

 (note that pressing F1 in QC will give you the wrong doc)

Bummer. I'm guessing that's happening because there are two separate
things called WebView in Qt, so the F1 just gives you the first one
that it finds. (WebKit comes before WebView alphabetically).


 I have a question on a note in the docs:

 Note: Due to platform limitations overlapping the WebView and other QML 
 components is not supported.

 I guess the above means it cannot be in an Item?
 Which means it cannot be in a StackView page, at least if there is anything 
 else on the page besides the WebView, correct?
 Can it be instantiated by Loader?

I'm not sure, as I haven't used this module before. You can test it
quite easily though.


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest