View Single Post
Old 02-22-2010, 07:05 PM   #15
Sonist
Apeist
Sonist ought to be getting tired of karma fortunes by now.Sonist ought to be getting tired of karma fortunes by now.Sonist ought to be getting tired of karma fortunes by now.Sonist ought to be getting tired of karma fortunes by now.Sonist ought to be getting tired of karma fortunes by now.Sonist ought to be getting tired of karma fortunes by now.Sonist ought to be getting tired of karma fortunes by now.Sonist ought to be getting tired of karma fortunes by now.Sonist ought to be getting tired of karma fortunes by now.Sonist ought to be getting tired of karma fortunes by now.Sonist ought to be getting tired of karma fortunes by now.
 
Sonist's Avatar
 
Posts: 2,126
Karma: 381090
Join Date: Oct 2008
Location: The sunny part of California
Device: Generic virtual reality story-experiential device
Quote:
Originally Posted by Jim Lester View Post
The original article was missing some details. Hover states (more correctly mouse over and mouse out events) are fully supported by flash even on touch devices. For more details set this blog post by Mike Chambers (with demonstration of Flash app on the iPhone)

The difference is in the interaction model of mouse vs. touch requires you to be careful in the design (am I really going to get a mouse over before I get a mouse down, maybe not), so yes it is quite possible to make a flash based app that won't work well on a touch device.

BTW this isn't a strictly flash based issue as there are any number of websites (eBay for instance - hover on the categories menu) that use Javascript to handle hover states on menus. It takes careful coding and consideration (regardless of platform and programming language) to handle the differences in touch vs mouse control.
+1

Excellent points. Nice to see some informed sanity among all the FUD.

Sonist is offline   Reply With Quote