Hi, I'd like to hear more about the use case. Taking heart rate and associating it to a positioninfo object sounds a bit strange. For example you might get heart rate update at a much faster rate than position updates or vice versa. This means you'd loose the contingency of at least one set of data.
Even if you don't care about this couldn't you simply use your own data type which would have a position attribute and a heart rate attribute? -- Alex ________________________________________ From: interest-bounces+alexander.blasche=digia....@qt-project.org [interest-bounces+alexander.blasche=digia....@qt-project.org] on behalf of Marian Beermann [pub...@enkore.de] Sent: Monday, September 15, 2014 12:21 To: interest Cc: Dmitrii Volosnykh Subject: Re: [Interest] Custom user attributes for QGeoPositionInfo I guess not. As it doesn't inherit QObject you also can't add dynamic properties at runtime. Might make sense to add in future release. Could be implemented with UserAttribute and internal QVariantMap or something similar. On 15.09.2014 11:33, Dmitrii Volosnykh wrote: > An object of QGeoPositionInfo class may be supplied with a set of > attributes. I wonder wether this class was designed with the ability to > add custom attributes (i.e. fitness ones like heart rate, cadence, > temperature, etc.)? I can see no enum value similar to Qt::UserRole (as > part of ItemDataRole enum) or QGraphicsItem::UserType. > > Regards, > Dmitrii. > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
