> On 24 Apr 2015, at 14:33, Marc Mutz <marc.m...@kdab.com> wrote:
> 
> Hi,
> 
> While implementing qHash() overloads for gui/math3d classes,

Why are we doing this? a QHash<QMatrix4x4, T> makes very little sense me..

-
Gunnar

> I found that 
> QQuaternion gained several methods for 5.5 which I don't like:
> 
> *EulerAngles():
> 
> They are missing a QEulerAngles class. Instead, they deal with (float, float, 
> float) and QVector3D. One function even returns three floats as out-
> parameters. I think my (partial) work on QDate/Time has shown just how much 
> compilers don't like out parameters. The question here is how general such a 
> QEulerAngles class should be...
> 
> *AxisAndAngle()/*Axes():
> 
> Same here, to a lesser extent. What bugs me most is the return-by-out-
> parameters, not so much that there's no QAxis3D class.
> 
> There are several steps forward:
> 
> - Create QEulerAngles as a float-only class
> - ditto, but as a template
> - ditto, but also add Q*Angle classes that have DEG/RAD hard-coded as template
>  arguments, with explicit conversions between, then use that in QEulerAngles.
>  [this likely won't happen for 5.5, though]
> - remove the methods in question for 5.5 and try again in 5.6
> 
> Any opinions about which ones to take?
> 
> Thanks,
> Marc
> 
> -- 
> Marc Mutz <marc.m...@kdab.com> | Senior Software Engineer
> KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
> Tel: +49-30-521325470
> KDAB - The Qt Experts
> _______________________________________________
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to