Hi, I've just responded to Sergey on the same issue, I've copied and pasted my resonse here for convenience
1) These are currently not planned to be released due to limitations of some of the platforms. 2) Because of point 1, this issue is moot, but the reasoning was as follows: Attributes were for "official" attributes for a particular landmark provider. All providers would have attributes such as coordinate but some providers may have business hours while others may not. Custom attributes were intended to be application specific attributes, if an application has say housing prices they would be able to save these as custom attributes. Which attributes were provided and whether custom attributes were supported are provider/backend specific and so the attribute() and customAttribute() functions were intended to be a way to handle these non-generic properties. Current limitations of some platforms meant that the default landmark manager/providers wouldn't be able to support these attributes/custom attributes and so the functions were not included on release. If there is enough interest and people who think it is a good idea, the concept of attributes and custom attributes may be revisited and scoped for a future release. Regards, Amos -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext Till Harbaum / Lists Sent: Wednesday, December 29, 2010 6:07 AM To: [email protected] Cc: [email protected] Subject: Re: [Qt-mobility-feedback] QLandmark class, setAttribute() and setCustomAttribute() public functions Hi, argh ... i can't believe it, i _just_ ran into this very same issue. Where is this setAttribute() thing? Also i am not fully confident that i am using/understanding this correctly. I am considering rewriting my geocaching application gpxview for meego/qt. This time of course using all these shiny brand-new mobility things. Assuming i have a bunch of those really complex "landmarks" these have things like "owners", lengthy lists of "attributes", encrypted hints, they maybe related to other waypoints etc etc. Is it really the right idea to use Landmark::attributes for all these things (assuming they really exist)? Regards, Till Am Montag 27 Dezember 2010 schrieb Serhiy Luzan: > 1) I found this functions in online documentation: > http://doc.qt.nokia.com/qtmobility-1.1.0-beta/qlandmark.html > But they are not available in qt-mobility 1.1 release sources. Are such > functions planned to be in release? > > 2) what is the difference between attribute and customAttribute ? > > Best Regards, > Sergey Luzan > _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-mobility-feedback _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-mobility-feedback
