UiFlow 2.0 discuss(how-to, bug, feature request or sometings)

[charlesRD]

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

[yaleman]

This post is deleted!

[sgu]

@charlesRD
i have similar issues

the Tab5 does not burn UIFlow at all!

[sgu]

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.

[hacxx]

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!

[thecuri]

I recently los all my private cloud projects....is there a way to get them back from your servers?

[zhumingqi]

I used UIFlow2 to devleop a simple UI demo, and I monitor the free memory with gc.mem_free(). I found the free memory reduced continiously though I called gc.collect() every loop. Finally, the UI can not update again, but the loop still was running.

[zhumingqi]

I tested more UI design. And I found that the memory leak only happens when I use image component and switch images frequently. Is that a UIFlow2.3.3 bug or my design is incorrect?

[zhumingqi]

Today, I updated the UIFlow to V2.3.4, and burned V2.3.4 firmware as well. Then I tested that image component again with M5GFX in UIFlow 2.3.4. But the issue still exists. After I switch two JPG pics with one image component for sometime, the memory will reduced continiously. Finally, the system will break out. And I try to use gc.collect() after every drawImage(), but it's not useful.
Here is my design and python code:
import os, sys, io, gc
import M5
from M5 import *

ImageSwitchFlag = None

def GcCollectAndPrint():
global ImageSwitchFlag
gc.collect()
print(gc.mem_free())
pass

def btnA_wasClicked_event(state):
global ImageSwitchFlag
if ImageSwitchFlag == 0:
M5.Lcd.drawImage("/flash/res/img/RotaryBGBacklight.jpg", 0, 0)
GcCollectAndPrint()
ImageSwitchFlag = 1
elif ImageSwitchFlag == 1:
M5.Lcd.drawImage("/flash/res/img/RotaryBGBT.jpg", 0, 0)
GcCollectAndPrint()
ImageSwitchFlag = 0

def setup():
global ImageSwitchFlag

M5.begin()
Widgets.fillScreen(0x000000)

BtnA.setCallback(type=BtnA.CB_TYPE.WAS_CLICKED, cb=btnA_wasClicked_event)

ImageSwitchFlag = 0

def loop():
global ImageSwitchFlag
M5.update()

if name == 'main':
try:
setup()
while True:
loop()
except (Exception, KeyboardInterrupt) as e:
try:
from utility import print_error_msg
print_error_msg(e)
except ImportError:
print("please update to latest firmware")******

[Schwibach]

I wrote in another thread about my Sync... 0% problem.

I am pretty sure now that it is a bug. I does not matter which program I use. I can run them from UIFlow 2.0. But as soon as I download a program, I will get the Sync... 0%

Also, if I burn firmware without selecting startup, it will not even connect to UIFlow 2.0.

I would really appreciate any guidance you could give.