On Aug 19, 2011, at 9:28 PM, ext Will Stokes wrote: > I recently noticed QPainterPath's "set" operation were being deprecated in > Qt4.8. > > QPainterPath’s “set” operations > State: Deprecated > Reasoning: flawed design, we don’t recommend taking maintainership of this > code. > http://labs.qt.nokia.com/2011/05/12/qt-modules-maturity-level-the-list/ > > Obviously these functions must remain in the 4.* series for binary > compatibility but I'm concerned that going forward (aka Qt5) these functions > will be removed.
I doubt we'll remove them completely regardless of what happens. What we have typically done for deprecated and "old" classes in the Qt 5 repository is to separate them out to a new repository so that keeping code compiling and working is mostly about adding another QT+=some_module to your .pro file. Because they are member functions of a class we intend to keep, this is not as straight forward though. I'm open to ideas. > Specifically, I'd like to make a plug for keeping: > void QPainterPath::setElementPositionAt ( int index, qreal x, qreal y ) Hi Will, There is no plan to remove setElementPositionAt(), so you don't have to worry about that :) best regards, Gunnar _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
