02b7ec05d5
Use M_PI (and friends), where possible, in favor of hand-coded approximations of various (in)accuracies. Where that's not available (e.g. fragment shaders), use the same value that qmath.h uses for M_PI, for consistency. Replaced math.h with qmath.h in places that defined a fall-back in case math.h omits it (it's not in the C++ standard, although M_PI is in POSIX); or removed this entirely where it wasn't used. Reworked some code to reduce the amount of arithmetic needed, in the process; e.g. pulling common factors out of loops. Revised an example's doc to not waste time talking about using a six-sig-fig value for pi (which we no longer do) - it really wasn't relevant, or anything to be proud of; nor did the doc mention its later use. Task-number: QTBUG-58083 Change-Id: I5a31e3a2b6a823b97a43209bed61a37b9aa6c05f Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> |
||
|---|---|---|
| .. | ||
| anchorlayout | ||
| basicgraphicslayouts | ||
| boxes | ||
| chip | ||
| collidingmice | ||
| diagramscene | ||
| dragdroprobot | ||
| elasticnodes | ||
| embeddeddialogs | ||
| flowlayout | ||
| padnavigator | ||
| simpleanchorlayout | ||
| weatheranchorlayout | ||
| graphicsview.pro | ||
| README | ||
Qt is provided with a comprehensive canvas through the GraphicsView classes. These examples demonstrate the fundamental aspects of canvas programming with Qt. Documentation for these examples can be found via the Examples link in the main Qt documentation.