Noticed one case where the new MM has some problem...
# kotlin-native
n
Noticed one case where the new MM has some problems, string allocation. In one of my projects I am developing an Embedded GUI application. It was discovered that if
lv_dropdown_set_options
( https://docs.lvgl.io/8.0/widgets/core/dropdown.html?highlight=lv_dropdown_set_options#_CPPv423lv_dropdown_set_optionsP8lv_obj_tPKc ) is used instead of the
lv_dropdown_set_options_static
( https://docs.lvgl.io/8.0/widgets/core/dropdown.html?highlight=lv_dropdown_set_options_static#_CPPv430lv_dropdown_set_options_staticP8lv_obj_tPKc ) function then the reserved memory usage increases by about 400 KB, ouch! ­čę╣ . This is the string literal that is passed through to the function:
"Male\nFemale\nOther"
­čĹŹ 1
An interactive example of using the Dropdown widget can be found here: https://docs.lvgl.io/8.0/widgets/core/dropdown.html#example