![]() The root element of the "curtain" is very simple - it is just a rectangular background with rounded corners at the top and a container in which the fragments are placed.Īnd the dialog_gray200_background.xml file looks like this:Įach new screen is a separate fragment, the fragments are replaced using the replace method, everything is standard here. This means that we will have a fragment container that is dynamic in height (since all fragments have different heights), and we must animate its height change. ![]() So, within the framework of our implementation (each screen is a new fragment), you can make only one bottom sheet, which should move as smoothly as possible in response to user actions. ![]() This led us to a technical limitation: we decided that we should not close the current bottom sheet and show a new one for each screen change, and it would also be bad to show several bottom sheets one above the other. In addition, you always want to see a smooth response to your action, and not convulsions. Users don't like it when there are too many abrupt movements on the screen. What, in fact, is the problem: where the client feels good, there we have limitations It will be necessary to take this into account in the future. The delay in displaying data is caused by the fact that it is loaded onto the screen asynchronously.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |