You Are Here:

Community: Blogs

Dale Rankine's Forum Nokia Blog

Disabling the Virtual Keypad in Flash Lite 3 on Touch Screen Devices

drankine | 09 April, 2009 13:19

Just a quick tip for those Flash mobile developers out there playing with Flash Lite 3.0 and the Nokia 5800 XpressMusic touch screen device. By default the 5800 (and presumably other future S60 5th Edition touch screen devices such as the N97) displays a virtual keypad in the Flash Lite 3.0 standalone player. Even if you have included the ActionScript for playing the SWF at fullscreen [ fscommand2("FullScreen", true"); ], the virtual keypad will break full screen and take up screen real estate in the player, as you can see in the image below.

Virtual keypad in Flash Lite 3 standalone player on the Nokia 5800

The way to avoid this is to add another line of ActionScript immediately before the fullScreen command -

fscommand2("DisableKeypadCompatibilityMode");

I personally don't think this is an ideal solution for Flash Lite on touch screen devices. I understand the use case for where a virtual keypad (which includes the 4-way directional keys, enter key and 2 soft keys) might be required with touch-based apps, but why not have it so that you can toggle it on an off, and also have it float over the top of the full screen content rather than making it look broken?

Anyway, in the meantime, if you're developing cool touch-based Flash Lite 3.0 apps for the Nokia devices then keep this code snippet in mind and don't get caught out.
 
 

Rate This

 
 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZidentifierQSxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fblogE2fpaulE2dcoultonsE2dforumE2dnokiaE2dblogE2farchivesE2f2009E2f04E2fX qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZBlogContentQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qfnZtypeQUqfntypeZBlogContentQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZWebpageQ qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZBlogContentQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ