…omposer

can cause min width

it can be ellipsized

we have to manually get the first child (toggle button)

…omposer

…omposer

if it's more than 1000 the string is too long to be useful: 1000/1000
let's just keep the remaining part only, it gets the point across as it goes down

the coditions are a bit messy but this the safest way to avoid race conditions
the delete button is visible if can-delete is true and the row is either not empty or not set to last

in general we would want to communicate with the parents through signals, so we might make the sandwitchview accept an interface that has said signals
atm it only supports scrolling which is needed when we update the poll components and we want the view to scroll to the bottom

an issue with the prior implementation was that the children would be 'cut off' when updating. After a very lengthy debugging process I discovered the issue. The yoffset gets updated after setting the top/bottom margins when we call size_allocate on the textview, but we would only call it between measuring and allocating the top and bottom children, which ended up messing with both. The correct way to do this is: 1. measure top & set top margin, 2. measure bottom & set bottom margin, 3. allocate textview, 4. get the yoffset, 5. allocate the top and bottom widgets as we did prior

…omposer

…ing children

just clear the target on cleanup

end of an era :')

needed for offset

needs to be done on mapped