glemco

Most recent activity

• clock_info - support

  in Bangle.js • 3 months

  

  Right, good point.
  Just out of curiosity, is BW clock really working so different or could it eventually use addInteractive too?
  If that's the case I'd wait for them to be unified before checking this update on the agenda clkinfo.

• clock_info - support

  in Bangle.js • 3 months

  

  Thanks, I guess I'm starting to grasp it better!
  I think at this point a couple of other clkinfo would need an update then:

  • the agenda should drop passed events as they are over
    
  • the weather should trigger an update once the old data is expired and when up to date data is available
    
  • I think the alarms are fine, since once one fires the screen is changing and going back to the clock would refresh anyway (does it always happen?)
    
    

  Does it make sense?

• clock_info - support

  in Bangle.js • 3 months

  

  So now the right way to handle the show for items that are always ready is to do nothing at all?
  Are we both drawing manually (also the non-ready ones) and redrawing once data is ready/changing?
  I see that the function menuShowItem is indeed triggering a redraw after calling the show, isn't it the same old story then? (Well I assume the idea is to keep it more under control)

• clock_info - support

  in Bangle.js • 3 months

  

  By the way, I'm not quite sure I fully understand the use of show (as it is right now).
  Clocks are supposed to call show, most of the times emitting a redraw, which eventually clocks are handling (on) while drawing. Isn't this equivalent to just calling a redraw on the first place (assuming no one else emits another redraw, which is the case for some clkinfos, like calendar date and battery).

  If I understood correctly, the simple this.emit("redraw"); lets the clock decide when to update (in a convoluted but standard way), while other ways can force redrawing on some events or timers. Am I missing something?

• clock_info - support

  in Bangle.js • 3 months

  

  In the reference Implementations I have always seen something like this.emit("redraw"); as only content of the show.
  You are right as probably yours wouldn't really change, but emitting a redraw won't hurt (say one day you want to show something else, it shouldn't be called that often anyway).

• 2-way communication with Android app (through intent?)

  in Bangle.js • 3 months, 1 week

  

  Good to know, looks promising!

• Corrosion on new charger point

  in Bangle.js • 3 months, 1 week

  

  Well, thanks, I'll keep the tape then! Don't want to mess up with the watch

• clock_info - support

  in Bangle.js • 3 months, 1 week

  

  Well, didn't mean to criticize your method (very neat, by the way). Just the clkinfo (and modules in general) are quite hard to track as they aren't versioned, so I first thought it could be that.
  If it's about pretokenisation, I should see it soon, perhaps it gets triggered with some state of the weather file, which I didn't get yet. Let's see.

• clock_info - support

  in Bangle.js • 3 months, 1 week

  

  Do you mean the problem is there just on 1 bangle out of 2?
  It could be anything, different versions of the clkinfo module (which gets pulled on install), some outdated file/app roaming around for whatever reason, or anything else.
  A better error log could help narrow it down.
  Anyway I have pretokenised all of my apps and have no errors, so reinstalling might have fixed.

• clock_info - support

  in Bangle.js • 3 months, 1 week

  

  I couldn't reproduce the error with clkinfos on my setup, however I found that the code printing that warning isn't exactly helping out with the problem..
  Could you trigger the exception while adding something like

  console.log(e);
  

  in the same catch box where that is printed (should be clock_info:133).
  After that, the result might tell something more meaningful.
  (For simplicity I can try to set up a branch with that modification on my fork, stay tuned)

  EDIT
  Here you go, by uninstalling and reinstalling the offending clock (slopeclockpp) with my app loader's fork (https://glemco.github.io/BangleApps/) you should be able to use this modified version of the clock_info module. You can check the only new commit in my master branch is adding that line.