Hi,
Our aim was to get new platforms in immediately after the previous platforms
branched away from dev branch. Meaning, when 5.7 branch was created and it
branched away from dev branch, all new platforms aiming for 5.8 should have
been put into dev branch. However, in practice it didn't quite
Kevin Funk wrote:
> To come to the point: We'd like to be able to use QtSingleApplication,
> without having to copy it to every KDE application's repository out there
> and building it ourselves. Several KDE applications (KDevelop, Krita,
> Kate) already do so.
Why can't you simply require it as a
On quinta-feira, 16 de junho de 2016 00:19:10 PDT Kevin Funk wrote:
> Is there an interest in having QtSingleApplication in Qt proper? Say
> qtbase? We'd love to do the work if there's a chance for it being
> accepted.
I'd like it in QtCore, without being a derivation of QCoreApplication, and
w
Heya,
"We" as in the KDE developers now focus on bringing KDE software towards more
platforms such as Mac OS X & Windows nowadays. We have discussed various ideas
to ensure unique application instances on these platforms.
Traditionally, KDE software is Linux focused and uses classes such as
KU
Hi Prashant,
Can you provide the output for a ³pidin -p ² and a "pidin
-p screen² when the system is in this state?
James
On 2016-06-15, 1:54 PM, "Development on behalf of Thiago Macieira"
wrote:
>On quarta-feira, 15 de junho de 2016 23:11:24 PDT Prashant Purohit wrote:
>> Hi all,
>>
>> I am
On quarta-feira, 15 de junho de 2016 23:11:24 PDT Prashant Purohit wrote:
> Hi all,
>
> I am new to QT and using QT with QNX.
> I am using two different windows in my application (It is not possible
> for me to use single window).
>
> When I switch from one window to another window, My screen is
Hi all,
I am new to QT and using QT with QNX.
I am using two different windows in my application (It is not possible
for me to use single window).
When I switch from one window to another window, My screen is not
responding due to deadlock. Though there is no crash observed.
My situation is simi
15.06.2016, 18:02, "Thiago Macieira" :
> On quarta-feira, 15 de junho de 2016 15:44:09 PDT Giuseppe D'Angelo wrote:
>> Il 14/06/2016 19:01, Sune Vuorela ha scritto:
>> > You can pass your own classes as handlers, provided that they have a
>> > public static function void cleanup(T *pointer).
>
On quarta-feira, 15 de junho de 2016 15:44:09 PDT Giuseppe D'Angelo wrote:
> Il 14/06/2016 19:01, Sune Vuorela ha scritto:
> > You can pass your own classes as handlers, provided that they have a
> > public static function void cleanup(T *pointer).
> >
> > - from the documentation.
>
> However,
Hi,
Another option might be to do it the same way like we do for UWP currently due
to limited resources on the CI system. There we have at least a compile check
every time qt5.git integration is supposed to happen.
This is bare minimum, but at least guarantees that compilation will work for
re
Il 14/06/2016 19:01, Sune Vuorela ha scritto:
You can pass your own classes as handlers, provided that they have a
public static function void cleanup(T *pointer).
- from the documentation.
However, you can't pass a per-QScopedPointer unique deleter object,
which also makes this part of the
Hi,
That page is only for adding OpenSSL support to Qt SDK. If you're building Qt
yourself, then you need to add "-openssl -I /path/to/openssl/headres" to
configure params.
Yours,
BogDan.
On Wednesday 15 June 2016 13:28:39 Fabrice Salvaire wrote:
> Dear All,
>
> I tried to follow http://doc.q
Dear All,
I tried to follow http://doc.qt.io/qt-5/opensslsupport.html but I
couldn't succeed to have https working on Android.
It seems this note is not up to date for 5.6 and later.
Apparently Qt configure disables the OpenSSL Qt code due to the
cross-compilation environment and if I try to
Hi,
Perhaps we could do without CI for tvOS for Qt 5.8 and fix issues when
breakages happen. We are still quite stretched with the CI and adding tvOS
increases the load of the CI and also risk of breakages for everyone. That of
course is the role of CI, but since tvOS is not at the moment so c
+1. I requested this earlier as well.
On Jun 15, 2016, at 1:51 AM, Mike Krus
mailto:mike.k...@kdab.com>> wrote:
Hi
would it be possible to have CI for tvOS in time for this too?
Cheers,
Mike
On 15 Jun 2016, at 08:15, Tuukka Turunen
mailto:tuukka.turu...@qt.io>> wrote:
Hi,
I would also
Hi
would it be possible to have CI for tvOS in time for this too?
Cheers,
Mike
> On 15 Jun 2016, at 08:15, Tuukka Turunen wrote:
>
>
> Hi,
>
> I would also like to have all new modules (if any) of Qt 5.8 as well as
> implement all (feasible) platform and compiler versions well before t
Hi,
I would also like to have all new modules (if any) of Qt 5.8 as well as
implement all (feasible) platform and compiler versions well before the feature
freeze. Is it possible to agree that latest by 1.8. all these are completed?
Preferably earlier, if possible.
Yours,
17 matches
Mail list logo
