Actions

[clydebarrow]

Actions

[nagyrobi]

I'd find useful a lvgl.widget.delete action (lv_obj_del_async(obj) or lv_obj_del).
Use case is a bootlogo, which could be fullscreen obj with a centered image, however just hiding it just keeps it uselessly in memory. We could free that resource...

[clydebarrow]

The problem with consolidating all the actions under one is that some things, like text: are only applicable to certain types of widgets. By having a different action for label the schema for that action can include text: as an option, whereas the schema for line: would not points but not text. At the time the schema is parsed the type of the object referenced by id may not be known, so checking that only the appropriate options are used gets complicated, whereas right now it will throw a clear error message if an inappropriate option is used.

[clydebarrow]

I'd find useful a lvgl.widget.delete action (lv_obj_del_async(obj) or lv_obj_del). Use case is a bootlogo, which could be fullscreen obj with a centered image, however just hiding it just keeps it uselessly in memory. We could free that resource...

The image data is stored in flash memory, so deleting the img object won't free much memory. If and when run-time loading of images e.g from urls is supported then memory management can be implemented as part of it, but right now there's very little to be gained.

[nagyrobi]

I see thanks.