I think there may be some confusion here. Are you talking about an actual AppWidget that sits on the users home screen? I was not aware there was a widget for the market.
I think you might be talking about the view at the top of a the Market application, which is not an AppWidget, but some sort of animated view, maybe an ImageView or collection of ImageViews. As such, they can use the standard animations for views, including fade ins and fade outs. AppWidgets are the special class of widgets you see on the home screen, such as the Clock, Weather, Search, Stocks type, and are hence restricted to the RemoteViews interface due to security. Normal widgets do not use this interface, and so have far greater flexibilty. Am I barking up the wrong tree? Is there actually a Market widget which you can add to the home screen? Regards James On Jul 9, 5:41 am, Matt <[email protected]> wrote: > Hi, I am trying to create a widget which functions in a similar manner > to the new Marketplace widget. > > The Marketplace widget fades between different views (each view being > a sample Marketplace app with a TextView and an ImageView describing > the Marketplace app). I would like to mimic this fading between > different views behavior. Unfortunately, as is clearly stated > inhttp://developer.android.com/guide/topics/appwidgets/index.html#Creat... > a ViewFlipper view is not supported. > > So, how can we mimic this fading behavior? > > 1. RemoteViews requires any view's class that is added to implement > @RemoteView. I tried creating the following class: > @RemoteView > public class MyViewFlipper extends ViewFlipper > { > public MyViewFlipper(Context context) > { > super(context); > } > > public MyViewFlipper(Context context, AttributeSet attrs) > { > super(context, attrs); > }} > > but referencing that class in the layout will cause the widget's view > to fail to load. ("Problem loading widget") So my trick about trying > to use @RemoteView doesn't work. > > 2. Update the widget a LOT (via AlarmManager) for a short period of > time. During this time, we will somehow set the transparency of one > view down while the other's goes up. But I believe this is a very > inefficient way of doing this, because the AlarmManager is not meant > for updates that occur more frequently than a second. > > 3. ??? Someone help me out here :) Could I start an AsyncTask which > will do #2 but without the AlarmManager? Heck, I don't even know > exactly how the fade really works. Any other ideas would help too! > > Thanks for the advice! > -Matt -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
