-
Notifications
You must be signed in to change notification settings - Fork 703
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pos.Combine
is incorrect for scenarios involving PosAbsolute
#2358
Comments
Right, the
Depends if it has any logic or not.
My opinion is that it doesn't sense because is the same as using
Without percent value it doesn't make sense (is the same as only using
Right (10020%=20+10020%=20=40 so it's the same as 100*40%=40)
Ask for more :-) |
Thanks. BTW, I have a refactor of all this in progress that fixes this an simplifies the code significantly. I believe I can make it work in a backwards compatible way. |
If is a backwards compatible merge it in the develop (v1) first and then merge it in the v2 while V2 is not released. |
Thanks. BTW, I have a refactor of all this in progress that fixes this an simplifies the code significantly. I believe I can make it work in a backwards compatible way. |
Pos.Combine
is incorrect if left
is PosAbsolute
Pos.Combine
is incorrect for scenarios involving PosAbsolute
Pos.Combine
is incorrect for scenarios involving PosAbsolute
Pos.Combine
is incorrect for scenarios involving PosAbsolute
Pos.Combine
is incorrect for scenarios involving PosAbsolute
Pos.Combine
is incorrect for scenarios involving PosAbsolute
Changed title since this is not such a big deal now that it's targeting v2. |
Fixes #2358 - BREAKING CHANGE: Pos.Combine is incorrect for scenarios involving PosAbsolute.
Can this be closed as completed? |
Change the
ComputedScenario
to add an additional button like this:Expected:
The new button is centered in the view.
Actual:
The bug is in
View.SetRelativeLayout
. It needs to check forPosCombine
and iterate throughPosCombine.left
andPosCombine.right
to adjust the relative location properly.I'm not actually sure it is possible to deal with all combinations. This may not be worth fixing.
Related:
Pos.Center() + Pos.Center()
to do?Pos.Percent() + Pos.Center()
to do?Pos.Percent(20) + Pos.Percent(20)
? (this one's obvious: just likePos.Percent(40)
).etc...
The text was updated successfully, but these errors were encountered: