When qdoc sees the function declaration, it must be able to mark the qdoc node
for the declaration as deprecated in 5.13, for example, so that it can require
that the deprecation be mentioned in the function documentation.
martin
From: Development on be
On 5 Mar 2019, at 06:56, Christian Ehrlicher
mailto:ch.ehrlic...@gmx.de>> wrote:
Am 05.03.2019 um 00:37 schrieb André Pönitz:
On Mon, Mar 04, 2019 at 03:12:33PM -0800, Thiago Macieira wrote:
On Monday, 4 March 2019 13:48:25 PST André Pönitz wrote:
The proposed model would effectively introduce
I'm mostly going off what JP had in mind, which are the following:
- https://bugreports.qt.io/browse/QTBUG-67062: Add full/public theming support
for QQC2 styles
- https://bugreports.qt.io/browse/QTBUG-73944: Make QQuickControl public
- https://bugreports.qt.io/browse/QTBUG-66829: Add IconImage t
Am 05.03.2019 um 00:37 schrieb André Pönitz:
On Mon, Mar 04, 2019 at 03:12:33PM -0800, Thiago Macieira wrote:
On Monday, 4 March 2019 13:48:25 PST André Pönitz wrote:
The proposed model would effectively introduce another user-visible
level including associated period of time between "alternati
On Mon, Mar 04, 2019 at 03:18:16PM -0800, Thiago Macieira wrote:
> On Monday, 4 March 2019 13:27:42 PST André Pönitz wrote:
> > Truly personally, I'd even go for
> > "no deprecation at all *for purely cosmetical reasons*" as I've seen
> > too many taking route
>
> That's a good point. Often we dep
On Mon, Mar 04, 2019 at 03:12:33PM -0800, Thiago Macieira wrote:
> On Monday, 4 March 2019 13:48:25 PST André Pönitz wrote:
> > The proposed model would effectively introduce another user-visible
> > level including associated period of time between "alternative
> > solution gets introducd" and "ge
On Monday, 4 March 2019 13:27:42 PST André Pönitz wrote:
> Truly personally, I'd even go for
> "no deprecation at all *for purely cosmetical reasons*" as I've seen
> too many taking route
That's a good point. Often we deprecate things because we had a misspelling or
failed to take our own naming
On Monday, 4 March 2019 13:48:25 PST André Pönitz wrote:
> The proposed model would effectively introduce another user-visible
> level including associated period of time between "alternative
> solution gets introducd" and "getting nagged about not using it"
> that is "hopefully" long enough, to co
On Mon, Mar 04, 2019 at 12:21:09PM -0800, Thiago Macieira wrote:
> On Monday, 4 March 2019 10:46:00 PST Christian Ehrlicher wrote:
> > You know what happens in this case - nothing since noone
> > notices... see all the usages of deprecated functions within
> > QtBase which have been unrecognized fo
On Mon, Mar 04, 2019 at 05:51:08PM +0100, Christian Ehrlicher wrote:
> Hi,
>
> I recently introduced some new signals
> (Q(Double)SpinBox::textChanged, QComboBox::textActivated) as
> replacements for old ones to be able to avoid the use of
> QOverload<>::of in Qt6 and to better match their respect
On Monday, 4 March 2019 10:46:00 PST Christian Ehrlicher wrote:
> You know what happens in this case - nothing since noone notices... see
> all the usages of deprecated functions within QtBase which have been
> unrecognized for ages.
I do, but who's to say people will fix warnings? Will they do th
Am 04.03.2019 um 19:28 schrieb Thiago Macieira:
On Monday, 4 March 2019 09:58:40 PST Edward Welbourne wrote:
Christian Ehrlicher (4 March 2019 17:51) wrote
So what's the correct way to deprecate a function and not forgetting
about QT_DEPRECATED later on as it happened with a lot of functions
d
On Monday, 4 March 2019 09:58:40 PST Edward Welbourne wrote:
> Christian Ehrlicher (4 March 2019 17:51) wrote
>
> > So what's the correct way to deprecate a function and not forgetting
> > about QT_DEPRECATED later on as it happened with a lot of functions
> > during Qt4 times?
>
> Isn't that wha
Mitch, do you have plans?
Il giorno gio 14 feb 2019 alle ore 20:12 drwho ha
scritto:
> On 2019-02-14 5:45 a.m., Pier Luigi Fiorini wrote:
> > Hi,
> >
> > I'd like to know if you have plans of making Qt Quick Templates 2 a
> > public API and allow people to write new controls with C++ without
> >
Christian Ehrlicher (4 March 2019 17:51) wrote
> So what's the correct way to deprecate a function and not forgetting
> about QT_DEPRECATED later on as it happened with a lot of functions
> during Qt4 times?
Isn't that what
#if QT_DEPRECATED_SINCE(5, 13)
is for ?
Eddy.
__
Hi,
I recently introduced some new signals (Q(Double)SpinBox::textChanged,
QComboBox::textActivated) as replacements for old ones to be able to
avoid the use of QOverload<>::of in Qt6 and to better match their
respective properties.
Within those changes I also marked the old signals as depreca
And don't let forget excutors:
http://www.vollmann.ch/en/presentations/executors2018.pdf
They will be end in C++ and it would be nice to be fit in.
From: Development on behalf of Denis
Kormalev
Sent: Monday, March 4, 2019 1:05 AM
To: Juan Gonzalez Burgos
Cc: de
17 matches
Mail list logo
