MicroPython Forum (Archive)

Re the LCD the driver doesn't maintain a cursor position. This is to keep it simple: these displays have only a few characters on each line. They refresh very fast. So a line update requires a string comprising all the text. Your options are either to adapt the driver to maintain a text cursor for e...

I hit the same issue. It doesn't appear to have been implemented. The Loboris port supports it.

The solution I use in my LCD160CR touch GUI is to use uasyncio. An interrupt is really overkill in this type of application: latency of a few tens of ms is never going to be noticed in touch applications. This coroutine is how I handle checking for touch events.

Looks kinda familiar ;) If you look at my source you'll see that I have a policy of referencing sources when I adapt the code of others. No beef - just saying. The above repo now includes a cross-platform version of this driver for those wishing to endow their ESP8266 with a decent RTC. The old Pybo...

...I'm not going to add MIT license header and just bloat the file... IANAL but I've noticed that many developers have a 2-line comment of the form # Copyright Guy Carver 2018 # Released under the MIT license with the full text in LICENSE.md. I'd be interested to hear from anyone who does have lega...

The problem here is that Viper likes to know the type of variables. Where variables are passed as function arguments you can use Python type hinting to solve this, but this isn't an option in a timer ISR. One solution is to use the Native decorator, but the code won't be as fast. You could do def ti...

Good luck! In my view this would be a great enhancement to the firmware so I hope you'll submit a PR when you've got it working.

OK, we need to figure out what is being returned. Try this: def I2C_ReadRegister(Rd_Addr): global i2c, sensor result = i2c.mem_read(1, sensor[0], Rd_Addr, timeout=1000) if isinstance(result, bytes): if len(result) > 0: return result[0] # Return a single byte else: print('Zero length bytes object ret...

I have now tested this fairly thoroughly. It's an impressive upgrade in terms of task switching performance and there seems to be no downside. The only API change is to the initial call to get_event_loop() which needs adapting to set the queue sizes if an application runs more than 16 concurrent cor...

I have updated this repository to reflect the release of uasyncio V2.0 , which is on PyPi and supported by official firmware dated 22nd Feb 2018 or later. uasyncio V2.0 brings no API changes unless your application runs more than 16 concurrent coroutines; in this case you need to adapt the initial c...