You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I have no idea how to do this. If I had widgets/views like Xilem, but with Taffy built in first-class instead of BoxConstraints (so we can use TaffyTree internally instead of traits externally), what would the layout and measure/compute_max_intrinsic function signatures look like and how would they be used (instead of the BoxConstraints that Masonry has)? Also, when Taffy is the main layout paradigm and there's no BoxConstraints, I don't see how I would make flex((...)) widget(s)/view(s) that take as arguments other widgets.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I have no idea how to do this. If I had widgets/views like Xilem, but with Taffy built in first-class instead of BoxConstraints (so we can use TaffyTree internally instead of traits externally), what would the
layout
andmeasure
/compute_max_intrinsic
function signatures look like and how would they be used (instead of the BoxConstraints that Masonry has)? Also, when Taffy is the main layout paradigm and there's no BoxConstraints, I don't see how I would makeflex((...))
widget(s)/view(s) that take as arguments other widgets.Beta Was this translation helpful? Give feedback.
All reactions