Strange behaviour when the touch event calls a scroller

Thanks for the report @Pologram, and for tracking this down @Ganblejs! That's a bit of a pain. The change in event handling was to fix some errors other apps/people were having (which made things behave differently depending on whether there was a pre-existing event handler or not).

I was trying to make a very basic proof of concept for this, and:

var inMenu = false;
Bangle.on('touch', function (zone, e) {
  if (inMenu) return;
  inMenu = true;
  E.showMenu({
    A : ()=>print("A"),
    B : ()=>print("B"),
    C : ()=>print("C"),
    D : ()=>print("D"),
    E : ()=>print("E"),
    F : ()=>print("F"),
  });
});

or just

Bangle.on('touch', function (zone, e) {
  E.showMenu({
    A : ()=>print("A"),
    B : ()=>print("B"),
    C : ()=>print("C"),
    D : ()=>print("D"),
    E : ()=>print("E"),
    F : ()=>print("F"),
  });
});

don't seem to trigger it for me on latest firmwares. I even tried with an extra Bangle.on('touch', ()=>{}) just in case. I can't even seem to get your Elapsed Time app to fail the way you show it? Can anyone reproduce on 2v24.128 or later?

As an easy fix I think just changing showMainMenu(); to setTimeout(showMainMenu,0); should fix it, but it seems odd it can't be reproduced now?

Date

Interesting! (new Date()) + (new Date()) produces Thu Oct 24 2024 13:09:57 GMT+00001729775397865.07299804687

So on one call it's producing a string, and the other a number. The actual change at fault was a seemingly unrelated https://github.com/espruino/Espruino/commit/f09330e7baf42cb8f7fda2c8fec5fd9be11991df but I've managed to get a fix in now!