Search results for:

The reason it didn't work without the connect function (the not defined error) is you weren't assigning the result of the require anywhere. You wanted

var AT6558 = require("AT6558");

Would removing that widget from the global.WIDGETS in your clock app do the trick? Then that would be the only app that needs modifying.

I don't know. This time of year I often wish to stop the clock ;).

From the datasheet @fanoush provided in another thread:

It definitely could do.
You could follow the gestures tutorial, but as you say if you only care about the shaking and not any specific direction etc., you probably could do it without any machine learning involvement just by looking for a sudden burst of accelerometer "noise" (for want of a better word).

Ah that link is useful. I had trouble installing EspruinoHub on a Pi Zero W recently. The issue was related to nodejs in Raspberry Pi OS stable. I might have another go with Legacy before going down the AlpineLinux route.

Maybe having pre-prepared images for raspberry pi's would be useful?

Don't forget there are more options than physical button and touchscreen. There are also gestures and taps on the watch body.

Ah I haven't paid enough attention to know about the subversions. No problem. I am just lurking about, gleaning information for when I get one. Sometimes someone asks something I think I already know the answer to xD

https://github.com/espruino/Espruino/blob/master/ChangeLog

Thanks. Was vaguely aware of pebbles for a long time but not enough to recognise them. Only became interested in watches at all recently when I started doing exercise.

Out of curiosity, what are the other two watches?

Oh interesting. I guess I just didn't hit that when trying it out.

This is a really sad thread. Sorry to hear about your watch. It isn't completely dead, so there might be hope once things are fully dried out.

I was doing a lot of looking about for a watch earlier this year* and the ones with IP67 ratings often specifically warn that they aren't suitable for swimming or showering (I think showers the temperature was specifically mentioned somewhere). The ones that advertise being swim suitable specify 5ATM waterproofness.

Fingers crossed for you.

*but still missed the Bangle kickstarter :(

You don't even need to wipe the draw functions. I played with this in the emulator last week. I was entertaining the idea of clock/health stats taking full screen, then swipe for the widgets displayed in a grid.

Yes, this is normal.
This looked right to me when I read your question, but didn't really know why so I looked it up. I think this explains it better than I can: https://developer.mozilla.org/en-US/docs/Web/API/setTimeout#the_this_problem

I think it could be useful. I wouldn't be worried about devs closing issues prematurely - there is nothing to gain unless Bangle app devs start monetising the apps somehow.

I think the question about how they'll be counted is sensible though. Issues in the BangleApps repo could be tagged. As @andrewg_oz says it is easier to keep track of bugs on a separate issue tracker per app, but not all apps have separate repositories (not sure if it is even the majority, and I understand why).

I'd personally love to see more screenshots in the app loader, more detailed descriptions, and more apps with an upload to emulator button (not sure what decides that currently, and I probably won't care as much when I can access the real thing).

Is there a heuristic command you can try running before upload to detect that it is a Bangle and display a warning only if so? It might not cover the Bangle in all its possible states, but I think the one where people are most likely to be hitting the "to flash" button by mistake.

OK that's fair enough, I hadn't considered that but can see how it could cause unnecessary tension. I'm on the email list so I'll just keep my eyes out after the holidays.

Upload one to the font converter. It looks like a URL is no longer required.

They're all font formats. Open Type Font, True Type Font, and WOFF the acronym escapes me but it is web something font, and is based on the other two but with a few web specific changes.

@gordon

I can't find where I read it but I think I saw somewhere that you are expecting new stock mid January? If so, will you be doing preordering so they can be presented as (belated) Christmas presents?

https://www.espruino.com/Bangle.js2#deleting-all-code

If set from GPS, will it update automatically, or does the wearer need to go back into the settings menu? It looks like the latter, but the former strikes me as more desirable. Obviously the idea is to not be checking GPS all the time, but is there a middle ground between actual current location and the home location?

I decided to have a go at writing something for the Bangle2 (at least, for the emulator until they go on sale properly). I started with the tutorial and ended up creating a very basic analogue clockface.

The docs for the graphics API say for the AA versions of methods:

Note: This is only available in devices with Antialiasing support included (Bangle.js or Linux)

but it isn't clear whether this should include Bangle.js 2, or just the original. The methods don't work in the Bangle 2 emulator. My guess is that they aren't intended to (it is a different screen, lower res, fewer colours, etc), but in that case maybe the docs should be more explicit about Bangles now there are two of them?

Working non-antialiased clock just in case anyone is interested:

function draw() {
  // work out how to display the current time
 var d = new Date();
//  var h = d.getHours(), m = d.getMinutes();
//  var time = (" "+h).substr(-2) + ":" + ("0"+m).substr(-2);
//  // Reset the state of the graphics library
  g.reset();

  var base = 85;
  var rad = 50;
  g.clearRect(base - rad, base - rad, base + rad, base + rad);
  g.drawCircle(base, base, rad);
  g.drawString("12", base - 2, base - 40, false);
  g.drawString("6", base - 2, base + 40, false);
  g.drawString("3", base + 40, base -2, false);
  g.drawString("9", base - 40, base -2, false);
  var handLength, hour, minutes, seconds, ang;

  handLength = 20;
  hour = d.getHours();
  ang = ((hour % 12 * 30) - 90) * 0.01745329;
  g.drawLine(base, base, base + (handLength * Math.cos(ang)), base + (handLength * Math.sin(ang)));

  g.reset();
  handLength = 35;
  minutes = d.getMinutes();
  ang = ((minutes * 6) - 90) * 0.01745329;
  g.drawLine(base, base, base + (handLength * Math.cos(ang)), base + (handLength * Math.sin(ang)));

  g.reset();
  g.setColor(255, 0, 0);
  handLength = 40;
  seconds = d.getSeconds() + d.getMilliseconds() / 1000;
  ang = ((seconds * 6) - 90) * 0.01745329;
  g.drawLine(base, base, base + (handLength * Math.cos(ang)), base + (handLength * Math.sin(ang)));
}

// Clear the screen once, at startup
g.clear();
// draw immediately at first
draw();
var secondInterval = setInterval(draw, 10);
// Stop updates when LCD is off, restart when on
Bangle.on('lcdPower',on=>{
  if (secondInterval) clearInterval(secondInterval);
  secondInterval = undefined;
  if (on) {
    secondInterval = setInterval(draw, 10);
    draw(); // draw immediately
  }
});
// Show launcher when middle button pressed
Bangle.setUI("clock");
// Load widgets
Bangle.loadWidgets();
Bangle.drawWidgets();

Maybe try setting a beep off in the IDE as @Tx described?