kevinjwalters

Performance is mentioned in #7 too

The green wire routing also is unfortunate. A casual/inexperienced observer would think it connected D0 to D2. If you look closely it doesn't follow the same style for pad connections...

Documenting the default frequency/period would be good too.

Based on https://github.com/pimoroni/pimoroni-pico/blob/ac2fa97e9673d0f59ccb0ac2b41eaa2a7283f033/libraries/inky_frame/inky_frame.cpp#L112-L120 I think > In your case 60 * 60 could be: > ``` > rtc.set_timer(60, ttp=TIMER_TICK_64HZ) > ``` should be ``` rtc.set_timer(60, ttp=PCF85063A.TIMER_TICK_1_OVER_60HZ) ``` for 60 minute...

Unrelated, I've not noticed a version number in the specification? That would be useful for anyone making a statement of "library XXX implements all of specification 1.2.3"

I tried [MakeCode beta](https://makecode.adafruit.com/beta#editor) on 28-May-2019 and same issue there. ``` Adafruit Circuit Playground Express version: 1.4.28 Microsoft MakeCode version: 5.13.6 codal-circuit-playground runtime version: v1.5.4-i2c_and_dac.0 ```

Is there any ETA on this?

I saw someone mention a "strange result" from analogue writes to **A0** in [AnalogWrite in MS MakeCode for pins A3, A6, A7](https://forums.adafruit.com/viewtopic.php?f=58&t=166491), I'll ask what this was...

We've just been chatting about some less heinous `format()` peculiarities in CircuitPython land, from 5.0.0-alpha.5 on a new CPB board. An example: ``` >>> "{0:.20f}".format(9.00390625) ### good '9.00390625000000000000' >>> "{0:.20f}".format(10.00390625)...

@jwunderl mentions in latter posts in https://forum.makecode.com/t/display-update-flushing-and-synchronisation-and-light-sensor-peculiarities/443/2 that a likely fix is https://github.com/microsoft/pxt-common-packages/pull/889 associated with #1135