lvgl: what happened to LV_OBJ_FLAG_OVERFLOW_VISIBLE
Perform all steps below and tick them with [x]
- Read the FAQ
- Check the related part of the Documentation
- Update lvgl to the latest version
- Reproduce the issue in a Simulator
Describe the bug
LV_OBJ_FLAG_OVERFLOW_VISIBLE seems to be missing. Maybe it was removed? If it was removed is there a replacement?
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 36 (25 by maintainers)
I’ve added back
LV_OBJ_FLAG_OVERFLOW_VISIBLEin c7e8b8447.sometimes it is just a matter of having someone tell you something that triggers the thought on how to do it. This happens to me all the time. It’s one of those moments where you smack your forehead.
There has to be a routine that is used to set the boundaries for a child object, That boundary test would get passed if the user is wanting to make the children visible if they are not within that boundary.
keeping them separate i think is a better thing to do because it allows the user to create only a single dsc that can be used to draw multiple items.