UiFlow 2.0 discuss(how-to, bug, feature request or sometings)
-
@riztronic The device includes a 5V to 3.3V power circuit, a built-in three-axis BMM150 geomagnetic sensor,
-
Does anyone know how to connect my m5stack core 2 ?
Im using the raspberry pi 5. Is the m5stackbcore 2 plug and play with raspberry pi or the websites? Ive neen trying to connect this thing for 2 weeks. This is crazy it takes this much trouble -
@Calilov330000
why don't you try a simple laptop/desktop? -
Could you unlock from UIFlow 2 the capability to code in micropython…
-
I am looking for all of the lcd drawing tools that were available in uiflow1.0. I was making some interactive graphics and I was drawing lines or rectangles in a loop and doing that in uiflow2.0 requires you to first drag out 100 lines in the ui builder which just is too slow. Here are the bloacks I am looking for in uiflow 2.0. How can I do something similar in uiflow 2.0
-
Hello,
I have some difficulties to burn UIFLOW on new devices
For ATom lite it seems to work but i get ERROR The device type is unknown! on device manager.
I dont know if it can acces to the wifi. i tried several time to unregister and burn it again, reinstall M5 burner, but it doesn't help.It can't connect to my M5 stamp C3, maybe there is a way to make a factory reset on them?
The previous Atom and Stick set up in february still worked well, and appears with green dot on device manager. when i try to burn it now i get the "unknown type" error and red dot.
it looks like i am not able anymore to have the same atom running when i burn them today.
Did i forgot something ?
Thank you very much,
Charles
-
This post is deleted! -
@charlesRD
i have similar issuesthe Tab5 does not burn UIFlow at all!
-
When Will LVGL be integrated in UIFlow 2 ? I don't see a progress there for many months. The new devices such as Tab5 are useless without LVGL. Programming with UiFlow 2.0 and printing simple lines and squares look very old school.
-
Thanks for sharing the UiFlow 2.0 resources! I appreciate having a dedicated space for bugs, how-tos, and feature requests. Does anyone have tips on avoiding common firmware burning errors, especially with account binding? Also curious if there’s a timeline for the full API docs release. Looking forward to seeing how this evolves!
