2012/9/21 Alessandro Portale
> On Fri, Sep 21, 2012 at 12:01 PM, Fred Fung wrote:
> > Hi all,
> >
> > I want to know how to turn off caching mechanism of Qt?
> > Including font cache, pixmap cache and so on.
> >
> > Or, how can I set the limit of memory cache?
>
> The Pixmap cache ca
On sexta-feira, 21 de setembro de 2012 18.01.28, Thiago Macieira wrote:
> qt5/ - arch-specific support files:
> bin/ or libexec/
> - executables not run by the user, like syncqt, lrelease,
> lupdate imports/
> - QtDeclarative imp
This is the right mailing list :-)
The Qt Developers Conference Call for Papers is still open. If you haven't
yet, please submit your presentation proposal for the conference. We're
looking for topics by developers, for developers, about Qt: developing with
it, developing it; what's coming, what's
On Friday, September 21, 2012 06:01:28 PM Thiago Macieira wrote:
> The Qt 5 file hierarchy upon installation should be:
>
> bin/ - executables run by the user
> - unversioned applications, like assistant, linguist, qdbus,
> qdbusviewer
> - versi
On 21/09/12 21:00, Knoll Lars wrote:
> On Sep 21, 2012, at 7:52 AM, ext Lorn Potter
> wrote:
>
>>
>> On 31/08/2012, at 3:45 AM, Lorn Potter wrote:
>>
>>>
>>> On 14/08/2012, at 6:12 PM,
>>> wrote:
>>>
On Aug 14, 2012, at 7:35 AM, ext alex.blas...@nokia.com
wrote:
>> -Origi
On sexta-feira, 21 de setembro de 2012 17.45.27, Tony Van Eerd wrote:
> I have no solutions (yet?). I just want to know how to constrain my
> thinking. I basically won't even try going down the DCAS road. Nor the
> LL/SC road, since C++11 has basically shunned that idea, sadly.
>
> Solutions that
I have no solutions (yet?). I just want to know how to constrain my thinking.
I basically won't even try going down the DCAS road.
Nor the LL/SC road, since C++11 has basically shunned that idea, sadly.
Solutions that map to C++11 concepts, with single-sized atomics, would probably
be best. L
On sexta-feira, 21 de setembro de 2012 16.46.44, Tony Van Eerd wrote:
> I'll take that as a 'No'. ie use of DCAS would be limited to the point of
> it not being worth maintaining 2 separate implementations - one with DCAS,
> one without. I think DCAS is only worth using if it could be used
> ever
I'll take that as a 'No'. ie use of DCAS would be limited to the point of it
not being worth maintaining 2 separate implementations - one with DCAS, one
without. I think DCAS is only worth using if it could be used everywhere.
> -Original Message-
> From: development-bounces+tvaneerd
On sexta-feira, 21 de setembro de 2012 18.01.28, Thiago Macieira wrote:
> include/- versioned include dirs:
> QtCore5 or QtCore-5 or QtCore.5 or Qt5Core/
Oops, this won't work, as it breaks source-compatibility completely.
It needs to be:
include/
qt5/
QtCo
On sexta-feira, 21 de setembro de 2012 17.33.01, Stephen Kelly wrote:
> On Friday, September 21, 2012 16:47:11 Thiago Macieira wrote:
> > Rationale:
> > --
> >
> > This is a rewriting of the book in how to name a library.
>
> It seems like it might be something to bring up in a wider scope
The Qt 5 file hierarchy upon installation should be:
bin/- executables run by the user
- unversioned applications, like assistant, linguist, qdbus,
qdbusviewer
- versioned applications, like qmake[35], qdoc5, qmlviewer5,
On Fri, Sep 21, 2012 at 04:47:11PM +0200, Thiago Macieira wrote:
> This is long, so I'll give you my recommendation first. If you agree with me,
> you don't have to read the rest. If you disagree, you have to read my
> arguments.
>
fwiw, this refers to
https://bugreports.qt-project.org/browse/QT
On sexta-feira, 21 de setembro de 2012 17.24.16, Thiago Macieira wrote:
> Good examples are: qtcreator, assistant, linguist, qmlviewer, qmlscene,
> qmlplugindump, qmlprofiler, xmlpatterns, qdbus, qdbusviewer, qglinfo
Actually, the qml ones are not good examples since they can load plugins.
On Friday, September 21, 2012 16:47:11 Thiago Macieira wrote:
> Rationale:
> --
>
> This is a rewriting of the book in how to name a library.
It seems like it might be something to bring up in a wider scope (with distros
for example). This isn't Qt specific. Has it been an issue before?
On sexta-feira, 21 de setembro de 2012 16.47.11, Thiago Macieira wrote:
> Include the major version number (5) in all library base names, like on
> Windows, on all platforms. On Windows we already have QtCore5.dll and
> QtV85.dll, so I recommend having libQtCore5.so.5. For Mac, I'm not sure of
> th
On sexta-feira, 21 de setembro de 2012 13.42.13, Tony Van Eerd wrote:
> By the way, I assume the intent is to limit the implementation to only using
> int/pointer-sized atomics, not double width atomics?
We can use double-width atomics if necessary. But the only architecture for
which I implemente
This is long, so I'll give you my recommendation first. If you agree with me,
you don't have to read the rest. If you disagree, you have to read my
arguments.
Recommendation:
---
Include the major version number (5) in all library base names, like on
Windows, on all platforms. On Wind
On 21 Sep 2012, at 15:30, P Bai
wrote:
> Thank you, Eike. From what I read in the codereview, a function to get the
> scale factor qt_mac_get_scalefactor() is available as a patch, but
> QPixmap/QImage HiDPI support is still a WIP. Does that mean even if I were
> able to detect HiDPI mode, I
> -Original Message-
>
> Not really, the id can't change.
> The id is only set once when the QMutexPrivate is used for the first
> time.
> (And that change has already been aquired for a long time)
>
> Acquire is uneccessary.
>
> It was added in commit 5bfeab87 when the uses of the ope
Thank you, Eike. From what I read in the codereview, a function to get the
scale factor qt_mac_get_scalefactor() is available as a patch, but
QPixmap/QImage HiDPI support is still a WIP. Does that mean even if I were able
to detect HiDPI mode, I still can't do anything until QPixmap/QImage suppo
On Sep 21, 2012, at 7:52 AM, ext Lorn Potter
wrote:
>
> On 31/08/2012, at 3:45 AM, Lorn Potter wrote:
>
>>
>> On 14/08/2012, at 6:12 PM,
>> wrote:
>>
>>> On Aug 14, 2012, at 7:35 AM, ext alex.blas...@nokia.com
>>> wrote:
> -Original Message-
> From: development-bounces+
Hi all,
I want to know how to turn off caching mechanism of Qt?
Including font cache, pixmap cache and so on.
Or, how can I set the limit of memory cache?
thanks.
Br, FF
___
Development mailing list
Development@qt-project.org
http://li
Another +1 from me.
Cheers,
Lars
On Sep 21, 2012, at 11:14 AM, leandro.m...@nokia.com wrote:
> I certainly second Erik's proposal.
>
>
> Kind regards,
> Leandro T. C. Melo
>
>
> From: development-bounces+leandro.melo=nokia@qt-project.org
> [develo
> However, I've recently decided to follow a different path and I will no
> longer be able to maintain the text editors and C++ language support.
Thanks for all your work. The C++ language/API assistance
implementation in Qt Creator is great to work with.
Regards,
Rob.
On 20 September 2012 22
I certainly second Erik's proposal.
Kind regards,
Leandro T. C. Melo
From: development-bounces+leandro.melo=nokia@qt-project.org
[development-bounces+leandro.melo=nokia@qt-project.org] on behalf of Ziller
Eike (EXT-Digia/Berlin)-Qt
Sent: Friday,
On 21 Sep 2012, at 07:12, Kai-Uwe Behrmann wrote:
> Am 20.09.12, 19:09 -0700 schrieb P Bai:
>> I have a few questions about how to add retina display support to my
>> application. I understand by reading an earlier discuss that you can add a
>> few lines in the info.plist to enable HiDPI rende
Had a chat with Konstantin on IRC today. We agreed to go for a1-a3 for now. In
addition, iteration will start at -1 (ie. an invalid boundary), so that you can
get all info by doing a loop starting with toNextBoundary().
But it needs to go in before beta 2, and all usages of QTBF in qt5.git and
A very strong +1
-Original Message-
From: development-bounces+bill.king=nokia@qt-project.org
[mailto:development-bounces+bill.king=nokia@qt-project.org] On Behalf Of
Ziller Eike (EXT-Digia/Berlin)-Qt
Sent: 21 September 2012 09:49
To: development@qt-project.org
Cc: list
Subject:
I propose Erik Verbruggen as the new maintainer for Editor & C++ Support in Qt
Creator, taking over the responsibilities from Leandro who unfortunately left
us.
Erik has already been working on the language support in Qt Creator for a long
time, including the whole c++ preprocessor in 2.6, work
21.09.2012, 01:08, "leandro.m...@nokia.com" :
> Hi everyone,
>
> it's been an awesome time participating in the development of Qt Creator.
> However, I've recently decided to follow a different path and I will no
> longer be able to maintain the text editors and C++ language support. A new
> m
31 matches
Mail list logo