Namespaces
Variants
Actions

Archived:Avkon.mbg IDs do not contain the scalable icons in S60 2nd Edition FP3 alpha (Known Issue)

Jump to: navigation, search
Archived.png
Archived: 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

Compatibility
Platform(s): S60 2nd Edition, FP3

Article
Created: User:Technical writer 1 (21 Jul 2005)
Last edited: hamishwillee (15 Jun 2012)

Contents

Overview

There are changes in Avkon.mbg when going from S60 2nd Edition, FP3 beta to S60 2nd Edition, FP3 alpha. The enumerations previously used for system scalable icons are now used for mbm bitmaps. There is no list of scalable icon IDs in S60 2nd Edition, FP3, and there is no Avkon.mif.

Description

The enum TmifAvkon
{
EMbmAvkonQgn_prop_signal_icon = 16384,

EmbmAvkonLastElement
};
defined the scalable Avkon (system) icons in S60 2nd Edition, FP3 beta. The beta enum would also work with the alpha SDK.
This list is missing from the alpha SDK. Furthermore, some enumerations are there but with a different ID, which results in that most of the application is compiled, but a bitmap is shown instead of a scalable icon.

How to reproduce

Create an application that tries to use system scalable icons, using scalable icon IDs (16384-) and Avkon2.mif in the emulator.

Solution

Use the beta SDK's Avkon.mbg to compile code with scalable icons and use Avkon2.mif in the emulator; meanwhile use Avkon.mif in target to study them.

This page was last modified on 15 June 2012, at 09:53.
314 page views in the last 30 days.
Nokia Developer aims to help you create apps and publish them so you can connect with users around the world.

京ICP备05048969号  © Copyright Nokia 2013 All rights reserved