Hi,
I found out that onAnimationComplete() is called on a very high frequency althogh WatchUi.animate() was not called. This happens only in the main view.
Background: I have an user option to deactivate animations. As soon the user deactivates it, the WatchUi.animate() is not called any more by code. Saying this, the onAnimationCompleted is called anyway on a high cyclic basis. I assume as fast as it can repeatedly start. The problem now is, that the onAnimationCompleted hosts a requestUpdate command causing my PC to activate it's fans but the simulator has no problem to resolve this situation correctly (due to the processor performance). As soon as I try this on my watch, the main view hangs since there isn't that processor performance.
I used the very same code on other (sub) views. Here I haven't got the problem. Therefore I assume that this is a bug. Can someone confirm?