I used this code:
scr = lv.obj()
btn = lv.btn( scr )
lbl = lv.label( btn )
lbl.set_text( "BTN" )
lv.scr_load( scr )
On v7 works ok. On v8, without label works and I can see a correct button drawn on framebuffer, but with the label, code is halted before flush callback.
Yes, I called gc.collect()…Now Im wondering, maybe it wasnt a problem with gc. I used thonny and call few times to gc.mem_alloc() from terminal and got results that I didnt expected. I tried to reproduce again but now looks normal so maybe the “crazy” values I saw where related to the “automatic variable inpection” feature that thonny ide has. ( Thonny IDE adds some code to every REPL command to visualize variables on the ide, like a light debugger)
Here I executed above script and then (without reset) called few times to gc funtions. The values returned from gc.mem_free() move from 70k, 100k, 100k, 25k…its not what you should expect
Yes, any ILI9xxx with an SPI interface cause PICO hasent too many pins. But I will write on python side, so it dosent affect to LVGL build.
I like how v8 looks, and today I came back to v7 cause that “gc problems”. Tomorrow I will check again better to understand if its really a problem or not…but another problem with v8 is that API has too many changes so I need to learn again how todo too many things, even python demos dosent works or API doc is not available…