Details
-
Task
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
None
-
None
Description
These properties are tricky because of the following questions:
- The current implementation reuses the properties of the base class (QQuickPropertyAnimation), but has custom setters and getters, so we can't simply forward the calls to the base implementation.
- The base implementation uses QVariant to store the properties, while QQuickGeoCoordinateAnimation uses QGeoCoordinate. Currently we can't handle such type mismatch.
I suggest to postpone these properties at least until the properties of the base class are updated.
Attachments
Issue Links
- resulted from
-
QTBUG-89874 QtPositioning: migrate to new QProperty system
- Closed