-
Notifications
You must be signed in to change notification settings - Fork 42
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
Inconsistent padding/height #63
Comments
Some further debugging: This only occurs with |
Hi @CmdrSharp Thank you for submitting the issue. Unfortunately, the bug is caused by Horizontal Pager, which calculates its height eagerly, thus setting it to a height of a month with 5 rows. So right now I don't think its fixable from my side, but I will check if its an expected behaviour of the pager over the weekend. |
I understand. A possible workaround is mentioned here: google/accompanist#1050 |
Another interesting note @boguszpawlowski: Note how June and April have the same amount of row, yet one has padding, and one does not. |
@CmdrSharp Thanks for the workaround! I will see if it's fixing the problem in this case. |
@CmdrSharp Sorry for a late reply, I was able to try the workaround, but the results were pretty laggy and inconsistent. So, until a better workaround comes, or this will be fixed from the Accompanist side, I will leave mark this issue as blocked. |
Hi! Thanks for a great composable :)
I've found that the padding seems a tad inconsistent. Below are three screenshots. The text at the bottom is positioned the same across all three, but note how the calendar has padding on some months, and none on others.
From my testing, it seems that some months in each year (different for different years) get padded.
See the screenshots, where you can notice this clearly on the month April.
The following months have padding added in 2022
In 2023 the following months have padding:
And in 2024, the following:
..And so on. I find no good reason for this behaviour when looking through the source.
Here's an example to reproduce:
The text was updated successfully, but these errors were encountered: