Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.

Using Symbian Access points settings dialog in 3rd-party applications

From Wiki
Jump to: navigation, search

Archived.pngArchived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

The article is believed to be still valid for the original topic scope.

Article Metadata
Platform(s): S60 2nd Edition
S60 2nd Edition (initial release)
Created: User:Technical writer 2 (21 Sep 2006)
Last edited: lpvalente (27 Jun 2014)



Using S60 Access points settings dialog in 3rd-party applications


Sometimes 3rd-party applications would want to provide the end users the ability to change the settings for access points. Instead of creating a custom dialog, the existing S60 CApSettingsHandler class can be used.


The CApSettingsHandler class in ApSettingsHandlerUI.h can be used to launch the standard access point settings dialog.
    CApSettingsHandler *settings =
        EFalse, // aStartsWithSelection
        EApSettingsSelListIsListPane, // aListType
        EApSettingsSelMenuNormal,  // aSelMenuType
        0,  // aIspFilter
        0,  // aBearerFilter
        0); // aSortType
    // id (TUint32) is the AP Id to launch for editing
    // RunSettingsL returns after completion
    settings->RunSettingsL(id, id);
    CleanupStack::PopAndDestroy(); // settings


Capabilities required to run CApSettingsHandler in S60 3rd Edition:
ReadUserData, WriteUserData, ReadDeviceData, WriteDeviceData
RunSettingsL() may panic with KERN-EXEC 3 if stack size is low. The stack size for the application can be increased by adding the following line to MMP:
EPOCSTACKSIZE   0x5000 // use 20kB stack (default: 8kB)

This page was last modified on 27 June 2014, at 21:27.
31 page views in the last 30 days.