Em sex 21 fev 2014, às 07:25:46, Heikkinen Jani escreveu:
> I was thinking that as well and discussed about this with my colleagues. The
> only reason for this additional "official_releases" dir is that it will be
> short list of releases instead of quite long list in Archive -folder. That
> way it
I was thinking that as well and discussed about this with my colleagues. The
only reason for this additional "official_releases" dir is that it will be
short list of releases instead of quite long list in Archive -folder. That way
it is easier for the users to find the latest one; they don't nee
On 21 February 2014 00:52, Giuseppe D'Angelo wrote:
> On 20 February 2014 17:45, Shaw Andy wrote:
>> How was this list created? Because it seems that although some are actually
>> missing it also contains ones that aren't, e.g. QSqlTableModel::record().
>
> I think the "official" list should be
Hi !
On 20 févr. 2014, at 15:32, Sze Howe Koh wrote:
> Hi all,
>
> The following functions/types need documenting. (This list excludes
> constructors, destructors, and operators). Could those who are
> familiar with these functions/types please add them?
>
> qtbase.git
>QWidget::macCGHandl
Em qui 20 fev 2014, às 19:56:42, Oswald Buddenhagen escreveu:
> what are you planning to do?
This is the first step: remove setSharable so we have one fewer state to check
during ref up & down. Keeping isSharedWith is no problem, as it doesn't affect
the refcounting.
The second step will be to
On 20 Feb 2014, at 20:55, Aris Green wrote:
> I can't find any method in the docs about how to disable the user reordering
> TableView columns. I want them to be able to click the header for sorting,
> but I want to disable reordering as it does not work that well.
Hi,
You can set TableViewC
I can't find any method in the docs about how to disable the user reordering
TableView columns. I want them to be able to click the header for sorting,
but I want to disable reordering as it does not work that well.
Thanks
___
Development mailing lis
On Thu, Feb 20, 2014 at 09:12:29AM -0800, Thiago Macieira wrote:
> The others are obscure indeed. As part of my efforts, I want to make QString
> /
> QByteArray / QVector keep a null d pointer for anything that doesn't require
> deallocation and reference counting -- that is, everything that is
>
> I agree on detach(): you can easily trigger a detach() by calling data().
> Well, as long as you ensure that your object is not const.
>
I wouldn't get rid of detach() just because data() can do the same thing. If
it is useful, I'd rather use the proper name for it.
The question is whether
Em qui 20 fev 2014, às 22:32:35, Sze Howe Koh escreveu:
> QAbstractOpenGLFunctions::initializeOpenGLFunctions()
That's an internal function.
> QByteArray::setNum()
Those are documented.
> QString::Data
Internal type, doesn't need documentation.
How did you create the list? In my q
Em qui 20 fev 2014, às 16:45:19, Tony Van Eerd escreveu:
> > -Original Message-
> > On Behalf Of Thiago Macieira
> > Subject: [Development] RFC: Deprecating setSharable / isSharable in our
> > containers and QString
> >
> > ... and removing them in Qt 6
> >
> > Please raise your hand if y
On Monday, 17 February 2014 12:25:44 CEST, Robin Burchell wrote:
> If you have proposals for other changes, I'm open to hearing about
> them. In general, I don't think most of the usability of the API is a
> problem apart from a few occasional trouble points, but different
> perspectives are always
Em qui 20 fev 2014, às 12:14:24, Nowacki Jedrzej escreveu:
> H,
>
> One hand raised.
>
> The original use case is buried in the Qt history, when I was asking /
> digging why we had that, I found that in some really rare and obscure cases
> it may be useful. For example when you want to contro
Em qui 20 fev 2014, às 09:05:57, Heikkinen Jani escreveu:
> - http://download.qt-project.org/official_releases/qt/ would have only
> latest releases( currently 5.2.1 & 4.8.5)
>
> - http://download.qt-project.org/archive/qt/ would have all releases
> (including latest ones)
Why do we need the offi
On 20 February 2014 17:45, Shaw Andy wrote:
> How was this list created? Because it seems that although some are actually
> missing it also contains ones that aren't, e.g. QSqlTableModel::record().
I think the "official" list should be the ones that qdoc outputs when
running "make docs". If qdoc
> The following functions/types need documenting. (This list excludes
> constructors, destructors, and operators). Could those who are
[snip]
How was this list created? Because it seems that although some are actually
missing it also contains ones that aren't, e.g. QSqlTableModel::record().
And
> -Original Message-
> On Behalf Of Thiago Macieira
> Subject: [Development] RFC: Deprecating setSharable / isSharable in our
> containers and QString
>
> ... and removing them in Qt 6
>
> Please raise your hand if you knew we had that feature.
>
They aren't even documented, are they?
On 13 February 2014 18:52, Matthew Woehlke
wrote:
>> Why does the Qt5 QRegExp documentation not mention QRegularExpression?
By the way, feedbacks on the API are welcome. Some API is deliberately
missing from QRegularExpression because I wanted to collect opinions
from real-world users. For instan
On 20 Feb 2014, at 08:32, Thiago Macieira wrote:
> ... and removing them in Qt 6
>
> Please raise your hand if you knew we had that feature.
Never heard of this.
>
> Please raise your hand if you've ever used them in your own code.
So, never ever used it, and never had a need for such function
Hi all,
The following functions/types need documenting. (This list excludes
constructors, destructors, and operators). Could those who are
familiar with these functions/types please add them?
qtactiveqt.git
QAxBase::fallbackMetaObject()
qtbase.git
QAbstractOpenGLFunctions::initializeOpen
H,
One hand raised.
The original use case is buried in the Qt history, when I was asking /
digging why we had that, I found that in some really rare and obscure cases it
may be useful. For example when you want to control the life time of a data in
your container. Imagine QVector::fromRawD
On 20/02/14 10:05, "Heikkinen Jani" wrote:
>What I have discussed here the process has been to move stuff to the
>archive when new minor release is done. From that point of view archive
>is almost up to date, only 5.1.1 is missing.
>
>But it is also OK to put stuff to the archive when new release
Hi Kurt,
On Wednesday 19 February 2014 08:14:21 Kurt Pattyn wrote:
> Hi Martin,
> > On 17 Feb 2014, at 19:39, Martin Koller wrote:
> >
> > Hi,
> >
> > had a quick look into the implementation as I wanted to use it in my
> > existing webserver.
> > However, the API does not provide a way to use
What I have discussed here the process has been to move stuff to the archive
when new minor release is done. From that point of view archive is almost up to
date, only 5.1.1 is missing.
But it is also OK to put stuff to the archive when new release comes out if
that is the wanted behavior.
I
On 20/02/14 08:32, "Thiago Macieira" wrote:
>... and removing them in Qt 6
>
>Please raise your hand if you knew we had that feature.
>
>Please raise your hand if you've ever used them in your own code.
>
>I doubt anyone has raised their hands to the second question and there
>mustn't
>be more t
25 matches
Mail list logo
