Topics created by rodrigob

@rodrigob This issue has been fixed in uiflow 2.1.6.

Hello @IAMLIUBO

thank you for confirming, much appreciated.

In the past I worked on projects which had similar restrictions - for various reasons some parts had to stay close - so I fully understand.

BTW: no need to be sorry. I am very glad most of UIFlow2 firmware is open source, so thank you for that.

Thanks
Felix

@rodrigob For info I managed to get things going by patching https://github.com/m5stack/uiflow-micropython/ to add the Unicode font from examples/Advanced/Display/Display_Unicode in the firmware.

The only information I found is the post from
https://namakeguma.com/?p=93

Which indicates some inconsistent behaviour across devices, but that setShowLock(True) as expected batches the led update until the next show() (or setShowLock(False); show() ) call. (thanks Google translate!)

Official documentation or source code instead of random japanese online blog posts would be welcome.

it's possible that this difference is due to the hardware capabilities of the two controllers. The Core2 may have a built-in audio module that allows it to play WAV files, while the Fire controller may not have the necessary hardware to support this feature.

It's also possible that the developers of UIFlow simply haven't had the time or resources to implement the "play WAV file" function for the Fire controller yet, but it may be added in a future update. You can also check different services provided by us.