<https://lh6.googleusercontent.com/-sn5rSQZIjm4/TfuWWyZb2kI/AAAAAAAAABE/LbHWjdT_OWM/widget_main_4x1_play_normal.png>
<https://lh3.googleusercontent.com/-Om6UM0oMmP0/TfuWaR32U9I/AAAAAAAAABM/Gae3RaayvQ4/widget_main_4x1_play_normal.png> <https://lh4.googleusercontent.com/-eKfgw6psc-w/TfuV9qta1GI/AAAAAAAAAA4/NZkwGZ5EFy8/device-2011-06-17-135746.png> After a lot of testing this is what I found out. The widget did not get confused about picking up the correct image, the problem was actually the image got shifted to the side so it seemed like it was using the wrong image but it wasn't. Since the two images land and port are a bit different in dimensions that is causing the ImageButton to go crazzy. See the attached image and also the two sample images I use. I'm not sure why there are now two images. It seems like setImageViewResource doesn't update the background image but the source image. -- 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
