Friday, May 28, 2010

[android-developers] Re: Stalling widget buttons after some time

I just had the issue also on my device. Strangly when I noticed it has
been little longer than 24 hours since I added the widget. And 24
hours is the updateperiod I've set.
Could it really have anything to do with that and if so, what???

Can't I just disable the updatePeriod?

Dirk

On May 29, 12:03 am, Dirk Vranckaert <dirkvrancka...@gmail.com> wrote:
> Hey all,
>
> I'm currently working on a widget/application and I have an issue with
> that.
> Before I get into the issue you could check out the code which is
> available just over here:http://code.google.com/p/workregistrationwidget-android/source/browse/
>
> So my issue... :)
> The widget contains two buttons. The linking of the buttons with an
> activity happens in my widget provider (http://code.google.com/p/
> workregistrationwidget-android/source/browse/trunk/
> WorkRegistrationWidgetAndroid/src/eu/vranckaert/workRegistrationWidget/
> widgetProvider/WorkRegistrationWidgetProvider.java). So far so good.
> Clicking the buttons interacts with my activities and my widget gets
> updated.
> However after some time (and this did not happen with myself but with
> one of my testers) the buttons just didn't work anymore. He had to
> remove the widget from and add it again (no re-install) and it fixed
> the problem.
>
> So I was thinking about two possible places where it might go wrong:
> 1) First off all I was thinking that the linking with the buttons to
> an activity through an intent maybe isn't the right way. Anyone who
> knows?
> 2) And secondly because there is always large period between when it
> was working and when it wasn't anymore (a few hours at least) I was
> wondering if it could have anything to do with the updatePeriod set in
> the widget info xml file (http://code.google.com/p/
> workregistrationwidget-android/source/browse/trunk/
> WorkRegistrationWidgetAndroid/res/xml/
> work_registration_widget_info.xml) altough it is set to 24 hours.
>
> I should mention that I tested it on Android 1.5, 1.6 (only for a
> small amount time in the emulator), 2.1 and 2.2 and I can't reproduce
> the issue he's having.
>
> Anyone who has any idea cause I'm not seeing any solution anymore?!!

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate