Mandatory changes for custom components
This section addresses the mandatory changes required for porting
applications written for S60 3rd Edition to S60 5th Edition.
- Changing
the platform UID
When porting applications from S60 3rd Edition to S60 5th Edition,
you must include the S60 5th Edition platform UID in your application's .pkg file
and create a new .sis installation package using the modified .pkg file.
- Handling
pointer events in custom controls
The S60 platform passes touch events to applications by calling CCoeControl::HandlePointerEventL.
The application that receives these events is the one that owns the window.
- Implementing
support for scalable UI
In order for the correct control to receive touch events, you must
implement support for scalable UI.
- Listening
for scrollbar touch events
If your custom control contains a scrollbar, you need to listen
for touch events in the scrollbar.