-----Original Message----- From: ext Till Harbaum / Lists [mailto:[email protected]] Sent: Wednesday, December 29, 2010 6:08 PM To: Choy Amos (Nokia-MS-Qt/Brisbane) Cc: [email protected]; [email protected] Subject: Re: [Qt-mobility-feedback] QLandmark class, setAttribute() and setCustomAttribute() public functions
Hi, > To me it seems the current qlandmark is only usable for a pretty limited > number of trivial use cases. > Could you give some insight on how you think complex landmarks should be > stored by a qt application? >My former apps have not used system classes at all for this. Am i supposed to >return to that concept for complex applications like ?>geocaching and raw OSM >data processing? >It would be great if you cound sched some light on how things are supposed to >be done. As you see i am willing to do things "right", but >i am missing >guidance here. For complex applications you may be better off not using the landmarks api. The attributes you wish to use are highly specialized while the landmark api only supports very generic common attributes. I agree that the utility is limited and I'll convey your feedback to the next set of roadmapping discussions. Regards, Amos _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-mobility-feedback
