On Macintosh OS X 10.14.5, Qt 5.12.5, and Qt Creator 4.9.2 I keep getting a
crash while stepping through code. I get a stack trace that looks something
like this:
1 _os_unfair_lock_recursive_abort
I'm having a bit of an issue creating a custom window with the
following requirements:
1. Customized window control buttons
a. I want to keep the 'X' button to close the window,but I do not
want the minimize or maximize buttons shown
b. In addition, I then need to add my own custom butt
On Monday, 19 August 2019 00:28:37 PDT Vadim Peretokin wrote:
> Which was actually a very, very bad surprise that was pretty poorly
> documented. Please don't do that again.
We should have made the change before 5.12 come out, since we were already
aware of OpenSSL's timelines at that point. It j
I personnaly use a qt.conf for mobile device and leave the i18n into resources:
[Paths]
Translations = :/i18n
Qml2Imports = :/qml
You can put the qt.conf into your resource file:
qrc:/qt/etc/qt.conf
so it will be used directly.
This work for me.
-Original Message-
From: Interest On Beh
Since you can combine resources, you could either have your resource into a
different repos (this is what I do with Git subModules, my i18n repos get
update on his own, I do another build for now when I release). But you probably
could compile the resource with rcc and dynamically load it by usi
On 8/19/19 5:00 AM, Thiago Macieira wrote:
To start with, there is no version of OpenSSL which is secure. Whoever
is using Qt just because it makes using SSL easy(ier) shouldn't be using
Qt anyway because they are releasing an insecure app they incorrectly
feel is secure.
That's very disingenuo
Ahh... I should use $$[QT_INSTALL_TRANSLATIONS] instead of
$$QT_INSTALL_TRANSLATIONS.
I just know nothing xD
On 8/19/2019 10:48 AM, Alexander Dyagilev wrote:
Filed the bug...
https://bugreports.qt.io/browse/QTBUG-77661
On 8/19/2019 10:35 AM, Alexander Dyagilev wrote:
Hmm This QT_INSTALL
"You can use CONFIG += lrelease to automatically compile the files during
the build, and CONFIG += lrelease embed_translations to make them available
in The Qt Resource System."
Alternatively, you can just add the .qm files to a resource file yourself,
e.g. in the case where you want a different q
Filed the bug...
https://bugreports.qt.io/browse/QTBUG-77661
On 8/19/2019 10:35 AM, Alexander Dyagilev wrote:
Hmm This QT_INSTALL_TRANSLATIONS is empty under Android config.
However, it's defined for Windows/Mac/Desktop Linux Any help?
On 8/19/2019 5:41 AM, Alexander Dyagilev wrote:
S
Hmm This QT_INSTALL_TRANSLATIONS is empty under Android config.
However, it's defined for Windows/Mac/Desktop Linux Any help?
On 8/19/2019 5:41 AM, Alexander Dyagilev wrote:
Something like this?
qt_qm_files.path = /assets/translations
qt_qm_files.files += $$QT_INSTALL_TRANSLATIONS/qt_*
Which was actually a very, very bad surprise that was pretty poorly
documented. Please don't do that again.
We saw the openssl change and didn't think anything big of it - well, it
turned out that a minor upgrade to an TLS release completely broke secure
web downloads, secure TLS connections, and
11 matches
Mail list logo
