-Original Message-
From: development-bounces+kai.koehne=digia@qt-project.org
[mailto:development-bounces+kai.koehne=digia@qt-project.org] On
Behalf Of Felipe Crochik
Sent: Tuesday, October 29, 2013 7:13 PM
To: Hausmann Simon
Cc: development@qt-project.org
Subject: Re:
On 29.10.2013 17.18, Thiago Macieira thiago.macie...@intel.com wrote:
On quarta-feira, 14 de agosto de 2013 13:15:42, Jonathan Liu wrote:
Hi,
Are there any plans for a Qt 4.8.6 release in the near future?
Qt 4.8.5 was unfortunately released with a critical graphics drawing
regression
On 25.10.13 09:57, Thiago Macieira thiago.macie...@intel.com wrote:
On sexta-feira, 25 de outubro de 2013 07:49:47, Koehne Kai wrote:
I think we should have only:
+ Reference Platforms
+ Supported Platforms
+ Platforms Reportedly Working
Makes sense to me.
Yes, that sounds actually good.
On 10/30/2013 1:45 AM, Sandy Martel wrote:
Le 2013/10/30 à 11:06, Nicolás Alvarez nicolas.alva...@gmail.com a écrit :
2013/10/29 Calogero Mauceri mauc...@actgate.com:
...
The Qt documentation states that QDir::currentPath() returns The
application working directory. Shouldn't the workind
I think i know whats the issue if its still not fixed.
My guess is that you don't use the resource system of Qt but the android
application assets to store your components, the last time i had issues
with this all the time was lost in the horrible slow fileengine for assets on
android. It looked
Hi,
On Wednesday 30 October 2013 00:58:05 Calogero Mauceri wrote:
The Qt documentation states that QDir::currentPath() returns The
application working directory. Shouldn't the workind directory be
initialized with the path the application was launched from? If that's
not the case, which is
Hi,
Android's assets are indeed slower (~2X) than Qt's resource system,
but not that slow ! :)
If I recall correctly in the beginning of this thread Kai said that using
Necessitas SDK it was ok, and I don't think he is using another technique
to store the qml files than he is using for
Hi All,
I'm was working on small feature for specifying custom DNS server to
QDnsLookup (QTBUG-30166).
I wanted to test out the feature on OSX, but I don't have a machine handy.
Can someone with a working OSX setup test the following patches for
build failures?
On 10/30/2013 8:59 AM, Konrad Rosenbaum wrote:
Hi,
On Wednesday 30 October 2013 00:58:05 Calogero Mauceri wrote:
The Qt documentation states that QDir::currentPath() returns The
application working directory. Shouldn't the workind directory be
initialized with the path the application
Hi,
Please write an error report about this issue (with all possible information)
to https://bugreports.qt-project.org
Br,
Jani
-Original Message-
From: development-bounces+jani.heikkinen=digia@qt-project.org
[mailto:development-bounces+jani.heikkinen=digia@qt-project.org]
On 10/30/2013 09:09 AM, BogDan wrote:
Hi,
Android's assets are indeed slower (~2X) than Qt's resource system,
but not that slow ! :)
From our experience the Android assets system is *extremely* slow for
listing large file sets. It's bad to the degree that I suspect it has
exponential
30.10.2013, 03:58, Calogero Mauceri mauc...@actgate.com:
Shouldn't the workind directory be initialized with the path the
application was launched from?
In Unix-like systems children inherit working directory of parent.
If Finder has / as working directory and does not change it
while
On 30.10.2013 9.33, Knoll Lars lars.kn...@digia.com wrote:
On 25.10.13 09:57, Thiago Macieira thiago.macie...@intel.com wrote:
On sexta-feira, 25 de outubro de 2013 07:49:47, Koehne Kai wrote:
I think we should have only:
+ Reference Platforms
+ Supported Platforms
+ Platforms Reportedly
Hi all,
using Qt 5.2 beta on Windows 7 x64, compiled with Visual Studio 2012 update
3 i am getting two annoying reports of memory leaks. First is from using
ICU and not calling u_cleanup() API on module unload and the second is
from QPrinterInfo::defaultPrinter() not cleaning up
OK. You just nailed it! After moving the files into a resource file the
startup went from a little over 4 seconds to less than half second. Just
for context: my application has 18qml files, 2 small javascript files and
20 or so images and not all of them are loaded on startup!
A little
On Wed, Oct 30, 2013 at 1:59 AM, Konrad Rosenbaum kon...@silmor.de wrote:
**
Hi,
On Wednesday 30 October 2013 00:58:05 Calogero Mauceri wrote:
The Qt documentation states that QDir::currentPath() returns The
application working directory. Shouldn't the workind directory be
On Wednesday 30 October 2013 11:36:12 Luka Vilar wrote:
Hi all,
using Qt 5.2 beta on Windows 7 x64, compiled with Visual Studio
2012 update 3 i am getting two annoying reports of memory leaks.
First is from using ICU and not calling u_cleanup() API on module
unload and the second is from
Hi,
I just checked the Qt5 assets implementation and for some reason that I fail
to understand the assets cache mechanism from Qt4 is not there ... that is the
reason why Necessitas is way much faster than Qt5.x :)
I'll add the cache mechanism ASAP.
Thanks!
Cheers,
BogDan.
OK. You just
On quarta-feira, 30 de outubro de 2013 09:47:49, Turunen Tuukka wrote:
On sexta-feira, 25 de outubro de 2013 07:49:47, Koehne Kai wrote:
I think we should have only:
+ Reference Platforms
+ Supported Platforms
+ Platforms Reportedly Working
This type of three tier approach is good for
Hi,
here is a fix for printing: https://codereview.qt-project.org/69686
Regards,
Friedemann
--
Friedemann Kleint
Digia, Qt
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On quarta-feira, 30 de outubro de 2013 11:36:12, Luka Vilar wrote:
Hi all,
using Qt 5.2 beta on Windows 7 x64, compiled with Visual Studio 2012 update
3 i am getting two annoying reports of memory leaks. First is from using
ICU and not calling u_cleanup() API on module unload and the second
Hey all,
quick summary of the meeting that we had today, discussing the future of the
QObject - HTML bridging efforts.
# QWebChannel
The KDAB fork of the QWebChannel will be merged back into the official Qt-
Labs repository.
It will stick around and I'll work on improving it. It solves the
Hi,
and thanks for the info.
Regards,
Luka
On 30 October 2013 15:21, Friedemann Kleint friedemann.kle...@digia.comwrote:
Hi,
here is a fix for printing: https://codereview.qt-project.org/69686
Regards,
Friedemann
--
Friedemann Kleint
Digia, Qt
On Tue, Oct 29, 2013 at 6:16 PM, Thiago Macieira
thiago.macie...@intel.comwrote:
You can remove in Qt 6.0.
Hmm, that is unfortunate ...
Should we consider so, how about undeprecating API before Qt 6.0 deprecated
in Qt 5.X?
___
Development mailing
On quarta-feira, 30 de outubro de 2013 20:45:18, Laszlo Papp wrote:
On Tue, Oct 29, 2013 at 6:16 PM, Thiago Macieira
thiago.macie...@intel.comwrote:
You can remove in Qt 6.0.
Hmm, that is unfortunate ...
As I said, it's possible to do it before, if you really need to. Note: *need*
to,
2013/10/31 Jiergir Ogoerg f35f22...@gmail.com:
so the idea is to cache the locale file in binary format in the
home/.kde directory (the binary file is also smaller than the other one),
Why would Qt store stuff into home/.kde?
Since I don't represent any company and the changes are simple
Why in home/.kde? - since it's easy to choose another location and I didn't
want to
bother (ask) the devs before I come up with a working solution - I just
chose it, if needed
it can be easily changed to the right directory - whichever you tell me.
On Thu, Oct 31, 2013 at 5:13 AM, Nicolás
27 matches
Mail list logo
