Open notjosh opened 5 years ago
My quick workaround was this, fyi: https://github.com/notjosh/IBPCollectionViewCompositionalLayout/commit/f8995b313e56f0700521872f993dd3c8bdb049bb
Thank you for reporting the issue. I'll look into it this weekend.
Floating-point values should eventually be rounded to screen scale. It should be delayed as much as possible to minimize the round-ff error.
I'm aware of this issue and it should be fixed, but it's a project-wide issue and I haven't started work.
Whew, this one was a tricky one, and probably a bigger issue to address (there are a lot of float comparisons!), so I'm interested in your thoughts.
The comparison here was causing a layout issue for me, where an orthogonal view wasn't moving down below the header (boundary supplementary) view.
I was getting these values:
Obviously in UI coordinates,
314.66666666666669
is the same as314.66666666666663
, but the comparison failed.How do you think we should handle comparisons like this across the lib?