On Thu, Oct 31, 2013 at 1:42 AM, Thiago Macieira
wrote:
> > Should we consider so, how about undeprecating API before Qt 6.0
> deprecated
> > in Qt 5.X?
>
> Undeprecating API is fine.
>
Thanks.
___
Development mailing list
Development@qt-project.org
htt
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
>
> wrote:
> > 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, not *want* to. As in
On Tue, Oct 29, 2013 at 6:16 PM, Thiago Macieira
wrote:
> 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 list
Development@qt-projec
Maybe simply deprecate that API with a respective macro?
Regards,
Konstantin
2013/10/29 Thiago Macieira
> On terça-feira, 29 de outubro de 2013 18:01:34, Laszlo Papp wrote:
> > Hi,
> >
> > I am about to deprecate some API in QtSerialPort after some discussion
> with
> > others. The target is 5
On terça-feira, 29 de outubro de 2013 18:01:34, Laszlo Papp wrote:
> Hi,
>
> I am about to deprecate some API in QtSerialPort after some discussion with
> others. The target is 5.2 for this, but I would like to know if we can
> remove that API or revamp it without considerations in 5.3 and later.
Hi,
I am about to deprecate some API in QtSerialPort after some discussion with
others. The target is 5.2 for this, but I would like to know if we can
remove that API or revamp it without considerations in 5.3 and later.
It is not a common API, and I bet based on the users' feedback that this is
