Scroll down the page you linked. At the bottom it says “Available under certain
Qt licenses. Find out more.”.
--
Kind Regards
Dipl. Ing. (FH) Bernhard Lindner
Von: interest-bounces+private=bernhard-lindner...@qt-project.org
[mailto:interest-bounces+private=bernhard-lindner...@qt-projec
Hi Matthias,
Unfortunately, I only have anecdotal responses for you, but I'm hopeful
that Qt 5.5 will improve the situation for you.
On 03/05/2015 05:34 PM, Matthias Degenkolb wrote:
> Hi again,
>
> update:
> upgraded to Qt 5.4.1 since I had strange TCP/Ip connect issues on
> Windows Phone, but
Hi,
Please let me know if Qtcharts module
http://doc.qt.io/QtCharts/qtcharts-qmlmodule.html available only under Qt
Enterprise license but not in community or opensource?
Thanks and Regards,
Ramakanth
===
Hi all,
I’ve been using the tech preview of QBluetooth that comes with Qt 5.4 with
support for BLE and so far I’ve been able to write to characteristics and
to receive notifications.
However, the thing with readings, and according to documentation, is that
the value is cached and is only updated a
Hi again,
update:
upgraded to Qt 5.4.1 since I had strange TCP/Ip connect issues on Windows
Phone, but now with Qt 5.4.1 situation seems to be pretty unchanged.
- Still having to manually enter UUIDs in appxmanifest and reregister
splash screens when creating vcxprojs (as described in
http://doc-s
On Thursday March 05 2015 12:15:39 Sorvig Morten wrote:
>The leaks are actually not due to incorrect ref counting, but instead due to
>missing autorelease pools (as the warning says).
Of course. That's what I actually meant when writing "not doing any refcounting
at all". My bad.
>The only sol
> On 05 Mar 2015, at 10:02, René J.V. Bertin wrote:
>
> On Thursday March 05 2015 08:50:36 Sorvig Morten wrote:
>
>> This is exactly the use case I have in mind for 32-bit Qt. The tradeoff is
>> the occasional memory leak when we get the ref-counting wrong.
>
> Reminds me of something. As I s
On Thursday March 05 2015 09:26:22 Pocheptsov Timur wrote:
> > And if that doesn't raise warnings on 10.7+ that is probably because one
> > way or another ARC is used?
>
> No, this is because the framework is different.
Are you saying that OS X 10.9 has a framework that simply doesn't warn anymo
Thank you, this looks like a good workaround!
2015-03-05 11:01 GMT+03:00 Gunnar Sletta :
>
> > On 05 Mar 2015, at 08:43, Alexander Ivash wrote:
> >
> > Thank you, but unfortunately such approach disallows changing stroke
> thickness independently of font itself. I'd like to keep font 'normal' an
On Thursday March 05 2015 08:50:36 Sorvig Morten wrote:
>This is exactly the use case I have in mind for 32-bit Qt. The tradeoff is the
>occasional memory leak when we get the ref-counting wrong.
Reminds me of something. As I said, I used the 5.4.0 digia installer on OS X
10.9 (a VM to be exact
> On 04 Mar 2015, at 15:40, Adam Light wrote:
>
>
> Our application allows users to use/write external C/C++ libraries that our
> application loads. On Macintosh, the shipping (non-Qt) version of our
> application has only a 32-bit version. Once we release the new version (using
> Qt), we wi
> On 04 Mar 2015, at 16:49, Thiago Macieira wrote:
>
> On Wednesday 04 March 2015 13:36:14 Sorvig Morten wrote:
>> ARC: Qt does not use ARC because it's not supported for 32-bit builds. It’s
>> not supported on 10.6 either, which is why the topic was brought up when we
>> dropped support for 10.
> On 05 Mar 2015, at 08:43, Alexander Ivash wrote:
>
> Thank you, but unfortunately such approach disallows changing stroke
> thickness independently of font itself. I'd like to keep font 'normal' and
> get 5 pixel stroke around it.
You could use http://doc.qt.io/qt-5/qml-qtquick-text.html#s
13 matches
Mail list logo
