Complete
over 4 years ago

When is it not ok to call WatchUi.requestUpdate();?

Hi,

This one is a new one on me!

I saw an ERA log from onSettingsChanged that crashed out on my DataField onSettingsChanged handerl:

    function onSettingsChanged() {
        if(view) {
            view.onSettingsChanged();
            WatchUi.requestUpdate(); // CRASHES HERE
        }
    }

There is nothing contentious that I can see in onSettingsChanged (except a slightly annoying Attention.playTone that I had decided to remove on account of it being annoying in any case) - just some maths that is null checked, valid and safe.

So:

1. Is there any time that it is either illegal or unwise to call WatchUi.requestUpdate()

2. How does one test for that?

Thanks,
G

Parents
  • It’s a single ERA report, so can’t flesh it out much. What I can confirm: 1. This is a pretty basic DataField and onSettingsChanged in the app is as per OP 2. The onSettingsChanged in the DataField does a few simple calculations and also called (it was annoying, so it doesn’t any more) Attention to play tone, buzz or vibrate depending on what’s available.  That’s about it really...
Comment
  • It’s a single ERA report, so can’t flesh it out much. What I can confirm: 1. This is a pretty basic DataField and onSettingsChanged in the app is as per OP 2. The onSettingsChanged in the DataField does a few simple calculations and also called (it was annoying, so it doesn’t any more) Attention to play tone, buzz or vibrate depending on what’s available.  That’s about it really...
Children
No Data