guess.
This is not specific to QImage, it's affecting many classes
Sent: Monday, December 17, 2018 at 6:53 AM
From: "Sze Howe Koh"
To: "Qt development mailing list"
Subject: [Development] Missing documentation in Qt 5.12
Significant chunks are missing from t
On Wed, Dec 19, 2018 at 12:38:48PM +, Martin Smith wrote:
> I found the problem.
>
> There are a few ways I can fix it. Which is preferred.
>
> 1. Simply merge the inherited members into the list that is already there.
> 2. Merge the inherited members into the list but qualified with their ba
QPaintDevice members
> ...
> QObject members
> ...
>
>
> From: Development on behalf of André
> Pönitz
> Sent: Tuesday, December 18, 2018 8:43:43 PM
> To: Eike Ziller
> Cc: Qt development mailing list
> Subject: Re: [Development] Missing documentatio
On 2018-12-19 19:26, Thiago Macieira wrote:
On Wednesday, 19 December 2018 04:38:48 PST Martin Smith wrote:
1. Simply merge the inherited members into the list that is already there.
2. Merge the inherited members into the list but qualified with their base
class name. 3. list the inherited memb
On Wednesday, 19 December 2018 04:38:48 PST Martin Smith wrote:
> 1. Simply merge the inherited members into the list that is already there.
> 2. Merge the inherited members into the list but qualified with their base
> class name. 3. list the inherited members from each base class all on the
> sam
each base class.
>
> QWidget members
> ...
> QPaintDevice members
> ...
> QObject members
> ...
>
>
> From: Development on behalf of André
> Pönitz
> Sent: Tuesday, December 18, 2018 8:43:43 PM
> To: Eike Ziller
> Cc: Qt develop
Subject: Re: [Development] Missing documentation in Qt 5.12
On Tue, Dec 18, 2018 at 11:49:22AM +, Eike Ziller wrote:
>
>
> > On Dec 18, 2018, at 11:25, Konstantin Shegunov
> > wrote:
> >
> > On Tue, Dec 18, 2018 at 9:39 AM Martin Smith
> > wrote: I'll a
On Tue, Dec 18, 2018 at 11:49:22AM +, Eike Ziller wrote:
>
>
> > On Dec 18, 2018, at 11:25, Konstantin Shegunov
> > wrote:
> >
> > On Tue, Dec 18, 2018 at 9:39 AM Martin Smith
> > wrote: I'll argue with you about it being a p1. If the problem is
> > confined to the all-members list, it's n
> On Dec 18, 2018, at 11:25, Konstantin Shegunov wrote:
>
> On Tue, Dec 18, 2018 at 9:39 AM Martin Smith wrote:
> I'll argue with you about it being a p1. If the problem is confined to the
> all-members list, it's not a p1 problem because the information is still
> there via the inherits lin
On Tue, Dec 18, 2018 at 9:39 AM Martin Smith wrote:
> I'll argue with you about it being a p1. If the problem is confined to the
> all-members list, it's not a p1 problem because the information is still
> there via the inherits links, which are more useful for seeing what is
> inherited anyway.
_
From: André Hartmann
Sent: Tuesday, December 18, 2018 9:19:07 AM
To: Martin Smith; Konstantin Shegunov
Cc: Qt development mailing list
Subject: Re: [Development] Missing documentation in Qt 5.12
Hi Martin,
the all-members list is very useful to get an overview about a class.
You're
ld and
cannot do its magic. :)
Cheers
Frederik
>
> From: André Hartmann
> Sent: Tuesday, December 18, 2018 9:19:07 AM
> To: Martin Smith; Konstantin Shegunov
> Cc: Qt development mailing list
> Subject: Re: [Development] Missing docu
Smith; Konstantin Shegunov
Cc: Qt development mailing list
Subject: Re: [Development] Missing documentation in Qt 5.12
Hi Martin,
the all-members list is very useful to get an overview about a class.
You're searching for a function to perform a specific task, that you
assume to be in a class. Searchi
l for seeing what is inherited
anyway. My own opinion is that the all-members list should be removed.
martin
From: Konstantin Shegunov
Sent: Monday, December 17, 2018 11:03:50 PM
To: Martin Smith
Cc: Sze Howe Koh; Qt development mailing list
Subject: Re: [
should be removed.
martin
From: Konstantin Shegunov
Sent: Monday, December 17, 2018 11:03:50 PM
To: Martin Smith
Cc: Sze Howe Koh; Qt development mailing list
Subject: Re: [Development] Missing documentation in Qt 5.12
Not only are members missing, but
Not only are members missing, but links lead noplace. For example in the
mentioned page metaObject() goes to
http://doc.qt.io/qt-5.12/qwidget.html#metaObject which naturally doesn't
exist. From what I can tell nothing that is inherited, beside the things
explicitly overriden, appear in the list. Al
__
> From: Development on behalf of Sze
> Howe Koh
> Sent: Monday, December 17, 2018 12:53:36 PM
> To: Qt development mailing list
> Subject: [Development] Missing documentation in Qt 5.12
>
> Significant chunks are missing from the Qt 5.12 documentation:
>
From: Development on behalf of Sze Howe
Koh
Sent: Monday, December 17, 2018 12:53:36 PM
To: Qt development mailing list
Subject: [Development] Missing documentation in Qt 5.12
Significant chunks are missing from the Qt 5.12 documentation:
https://bugreports.qt.io/browse/QTBUG-72357
Could we
Significant chunks are missing from the Qt 5.12 documentation:
https://bugreports.qt.io/browse/QTBUG-72357
Could we please have a prominent notice on the website informing users of
this issue (and suggest viewing the Qt 5.11 version as a workaround) until
a fix lands?
Regards,
Sze-Howe
_
On Tuesday 04 March 2014 12:38:29 Samuel Gaist wrote:
> Hi,
>
> On 4 mars 2014, at 10:16, Marc Mutz wrote:
> >>QWidget::macCGHandle()
>
> Currently not implemented, used to return the Core Graphics Handle for the
> widget
>
> >>QWidget::macQDHandle()
>
> Also not implemented, used to r
On Thursday 20 February 2014 15:32:35 Sze Howe Koh wrote:
> QApplication::palette()
Fixed in https://codereview.qt-project.org/79605
> QGraphicsScene::focusItemChanged()
Fixed in https://codereview.qt-project.org/79604
> QtConcurrent::Exception
> QtConcurrent::UnhandledException
On 22 February 2014 16:04, Jason McDonald wrote:
> On Fri, Feb 21, 2014 at 12:32 AM, Sze Howe Koh
> wrote:
>>
>> The following functions/types need documenting. (This list excludes
>> constructors, destructors, and operators). Could those who are
>> familiar with these functions/types please add
On Saturday 22. February 2014 18.04.01 Jason McDonald wrote:
> On Fri, Feb 21, 2014 at 12:32 AM, Sze Howe Koh wrote:
> > The following functions/types need documenting. (This list excludes
> > constructors, destructors, and operators). Could those who are
> > familiar with these functions/types ple
On Fri, Feb 21, 2014 at 12:32 AM, Sze Howe Koh wrote:
> 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?
>
Thanks for the info. The QTest items are genuine er
On 21 February 2014 01:15, Thiago Macieira wrote:
> 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
On 21 February 2014 06:22, Samuel Gaist wrote:
> 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
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 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
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
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
>
> No. ListView is designed to support many interaction methods, not a
> specific interaction method with others being "custom things". Aside
> from the case where you want more than click-to-select in your
> MouseArea (which is probably the most common case, and would require
> overriding any de
On Mon, Jan 28, 2013 at 11:56 PM, Rainer Keller wrote:
> Hi,
>
>> Having
>> a MouseArea "by default" would most likely lead to it being disabled
>> in the majority of cases, on all platforms except desktop.
> I agree. But this doesn't this affect mobile touch devices too?
Some mobile UIs have tap
Hi,
> Having
> a MouseArea "by default" would most likely lead to it being disabled
> in the majority of cases, on all platforms except desktop.
I agree. But this doesn't this affect mobile touch devices too?
> This is a different problem (probably easiest solved with a link to
> the examples, li
On Mon, Jan 28, 2013 at 12:36 AM, Rainer Keller wrote:
> Hi,
>
>
>
> I tried to use a QML ListView and wondered why it does not react to mouse
> clicks. After looking into the examples I found out that you need to add a
> MouseArea in the delegate. Without this code the ListView is unusable
> beca
On Mon, Jan 28, 2013 at 8:36 AM, Rainer Keller wrote:
> **
>
> Hi,
>
>
>
> I tried to use a QML ListView and wondered why it does not react to mouse
> clicks. After looking into the examples I found out that you need to add a
> MouseArea in the delegate. Without this code the ListView is unusable
Hi,
I tried to use a QML ListView and wondered why it does not react to mouse
clicks. After looking into the examples I found out that you need to add a
MouseArea in the delegate. Without this code the ListView is unusable because
the user can not select anything using the mouse.
Shouldn't the
38 matches
Mail list logo