Blocked texts on the menu page after adding an new event class

[EasyVector]

Describe the bug

Dear developer!
In the process of using, I found a bug in layout / display. As shown in the figure below, on the menu page, there are some texts which are blocked by the border of their buttons. This may be an adaptation problem. I suspect it is because display and font size are set to large (mainly due to display size).
Because of some problems with my eyesight, I often use the largest font and display.

App version is 3.2, my mobile phone is Google Pixel 2, and the screen resolution setting is 1920* 1080. And my font size and display size are the largest ! ! ! Also, my Android system version is 10.0.
The above is a description of the problem. The overall experience of the software is good. You can see that the design is very attentive. Thank you very much for the efforts of the developers all the time. I hope to receive a reply. Thank you so much!!

Expected behavior

I hope that I can see all of the texts inside those buttons, and in this circumstance, part of them seem to be blocked.

Steps to reproduce the behavior:

1.use the largest font and display in the display setting
2.click the button, "new event class", then add a new event like "go shopping"
3.this error could be seen

Screenshot

(The blocked parts are marked in red)

Environment

1. Version of CalendarTrigger: 3.2
2. Device : Google Pixel 2,
3. OS version : Android 10.0

[rparkins999]

I'm sorry it has taken me so long to deal with this. Side-effects of the pandemic and other issues have prevented me form writing code for a while.

I decided that the right solution was to make all the screens into ScrollViews. Unfortunately Fragments don't work properly inside a ScrollView, and they are now deprecated anyway, so I had to promote all my Fragments to Activities. I've also fixed a couple more user interface issues related to the behaviour when using large fonts.

I don't seem to be able to set my emulator to have fonts as large as those which you use, so you may find other places where text doesn't get displayed properly. If you do, please let me know and I will try to fix them. Judging by my experience, problems seem to occur where one or more text boxes and input fields are arranged horizontally in a LinearLayout. Android doesn't seem to deal correctly with breaking a text box over multiple lines in this case. If the text box is a direct child of a vertical LinearLayout it seems to get it right.

Note that these changes are currently only in the floatingbugfix branch. My local master branch is currently about 18 commits ahead of the master branch in github, and in the middle of a major rewrite of the underlying engine, which isn't working properly yet. So it may be some while before these changes get propagated into the master branch on github.

[EasyVector]

OK, I will test further on my emulator and I appreciate your work! :)