Figure 1: Single landmark Selector
Figure 2: Multiple landmark Selector
Landmarks UI Selector API is typically used by applications based on S60 that need to provide landmarks/categories listing or selection functionality that exist in the landmarks database.
The following are snap-shots of single and multiple landmarks selector dialogs.
|
Figure 1: Single landmark Selector |
Figure 2: Multiple landmark Selector |
The following are snap-shots of single and multiple categories selector dialogs.
|
Figure 3: Single Category Selector |
Figure 4: Multiple Category Selector |
The main use cases of Landmarks UI Selector API are as follows
This section describes the Landmarks UI Selector API class structure.
Figure 5: Landmarks UI Selector API class diagram
Landmarks UI Selector API consists of the classes TLmkItemIdDbCombiInfo,CLmkLandmarkSelectorDlg, and CLmkCategorySelectorDlg.
The CLmkLandmarkSelectorDlg class provides methods for
creating and launching a dialog for listing and selecting the landmarks in
the landmark database. The methods of this class return the ID of the selected
landmark and the database to which the selected landmark belongs. This class
provides methods for selecting a single landmark or multiple landmarks.
The CLmkCategorySelectorDlg class provides methods for
creating and launching a dialog for listing and selecting the categories in
the landmark database. The methods of this class return the ID of the selected
category and the database to which the selected category belongs. This class
provides methods for selecting a single category or multiple categories.
The TLmkItemIdDbCombiInfo class provides methods for getting
the ID of a landmark or category and the database handle to which the selected
landmark or category belongs. The client application executes these methods
to get the ID of a landmark and the database handle and then uses those for
its internal usage, such as for modifying the landmark attributes. The client
takes the ownership of the database handle which is returned. The database
handle returned to the client will be the same for all landmarks from the
same database.
