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
Not sure if this is a configuration issue or not, but it seems I'm getting different behaviors when testing with the same tree on the playground vs c code.
Interesting. Playground uses same C API under the hood. Minor differences like JS would use YGEdgeAll in the example given. Would need to debug why these two would behave differently.
Hi, did someone end up looking into this? I'm also seeing different results to playground, the C example looks like this on my end, with 3.1.0 and 2.0.1, with Visual Studio 2019.
Also notice the greatgrandchild (small vertical line in the top bright rectangle) not having any width.
Update, this wasn't as big of an issue as I thought; my main hurdle was not understanding that top/bottom was relative the parent node, and not a screenspace coordinate. Hence the odd looking layout above.
Report
Issues and Steps to Reproduce
Not sure if this is a configuration issue or not, but it seems I'm getting different behaviors when testing with the same tree on the playground vs c code.
Here's the c code:
Here's the equivalent playground code (plus comments):
In the output of the c code, I get:
Width
shouldn't be zero imo and the playground correctly assigns the appropriate width:Tested both v3.0.2 and v2.0.1 with WebDefaults and without.
The text was updated successfully, but these errors were encountered: