Thanks! Yes, that's what was happening. I did a force-reload on both browsers and now it's working.
Is there a simpler way to get apps into the emulator which don't have an emulator button in the loader? Unfortunately, one of the first apps I wanted to tinker with seemed to turn out being one of the more complex ones out there (unbeknownst to me at first). It took a while, but I eventually worked out how to manually load each of the app's files into storage with the proper name prefixes, but then it used a module and I had to figure out exactly where that should be stored. To be fair, that turned out being in the documentation somewhere, but for some reason I had some trouble finding the correct info with Google, so it was a little frustrating. In the end, I got it working, though to reload the app I had to use a manual command in the debugger window as it gets stuck on a “Loading…” screen with no error messages if it tries to reload itself—haven't worked that part out just yet. Maybe something to do with the emulator defaulting to not having any of the usual apps installed that the physical Bangle.js ships with?
Anyway, it makes me wonder if I'm missing something more obvious, as this workflow seems a bit more clumsy and long-winded than I was expecting. On the upside, I think in the process I'm starting to get a better context of how the Bangle.js system and apps are structured, so that should help. :)
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Thanks! Yes, that's what was happening. I did a force-reload on both browsers and now it's working.
Is there a simpler way to get apps into the emulator which don't have an emulator button in the loader? Unfortunately, one of the first apps I wanted to tinker with seemed to turn out being one of the more complex ones out there (unbeknownst to me at first). It took a while, but I eventually worked out how to manually load each of the app's files into storage with the proper name prefixes, but then it used a module and I had to figure out exactly where that should be stored. To be fair, that turned out being in the documentation somewhere, but for some reason I had some trouble finding the correct info with Google, so it was a little frustrating. In the end, I got it working, though to reload the app I had to use a manual command in the debugger window as it gets stuck on a “Loading…” screen with no error messages if it tries to reload itself—haven't worked that part out just yet. Maybe something to do with the emulator defaulting to not having any of the usual apps installed that the physical Bangle.js ships with?
Anyway, it makes me wonder if I'm missing something more obvious, as this workflow seems a bit more clumsy and long-winded than I was expecting. On the upside, I think in the process I'm starting to get a better context of how the Bangle.js system and apps are structured, so that should help. :)