In MVP, this button hid all buttons with stages. In the mobile version of the OS, it also hides all the buttons.
On the desktop, the buttons are not hidden, but are placed in one row, which is why the ones that do not fit are not visible. The height of the block with buttons does not change, which results in a white field overlapping the interface blocks.
And the button itself disappears, which makes it impossible to return everything back.
Please fix to hide all statuses when clicked. What is the purpose of the button?
[file]18798[/file]
[file]18798[/file]
In MVP, this button hid all buttons with stages. In the mobile version of the OS, it also hides all the buttons. On the desktop, the buttons are not hidden, but are placed in one row, which is why the ones that do not fit are not visible. The height of the block with buttons does not change, which results in a white field overlapping the interface blocks. And the button itself disappears, which makes it impossible to return everything back. Please fix to hide all statuses when clicked. What is the purpose of the button?
I just saw that I attached the wrong screen. Thanks, the problem is gone! The only second delay is the white background of the block with buttons.
I just saw that I attached the wrong screen.
Thanks, the problem is gone! The only second delay is the white background of the block with buttons. [file]18816[/file]
Farkhshatov Rodion wrote: Thanks, the problem is gone! The only second delay is the white background of the block with buttons.
This time is necessary for the script to be able to calculate the height of the scrollable block.
[quote]
Farkhshatov Rodion wrote:
Thanks, the problem is gone! The only second delay is the white background of the block with buttons.
[/quote]
This time is necessary for the script to be able to calculate the height of the scrollable block.
Farkhshatov Rodion wrote: Thanks, the problem is gone! The only second delay is the white background of the block with buttons.
This time is necessary for the script to be able to calculate the height of the scrollable block.
Of course, it would be great to solve this moment, the block immediately disappeared in the MVP. But here's another problem with it: - Process at a stage from which there are many options for transition to others. Block with buttons in several rows. - When switching to a stage from which there are fewer options for transitions, and accordingly fewer rows in the block, the height of the block does not change, and a white area is formed that does not go away and overlaps the data.
[quote]
Derkach Dmytriy wrote:
[quote]
Farkhshatov Rodion wrote:
Thanks, the problem is gone! The only second delay is the white background of the block with buttons.
[/quote]
This time is necessary for the script to be able to calculate the height of the scrollable block.
[/quote]
Of course, it would be great to solve this moment, the block immediately disappeared in the MVP.
But here's another problem with it:
- Process at a stage from which there are many options for transition to others. Block with buttons in several rows.
- When switching to a stage from which there are fewer options for transitions, and accordingly fewer rows in the block, the height of the block does not change, and a white area is formed that does not go away and overlaps the data.
[file]18839[/file]
[file]18840[/file]
Farkhshatov Rodion wrote: But here's another problem with it: - Process at a stage from which there are many options for transition to others. Block with buttons in several rows. - When switching to a stage from which there are fewer options for transitions, and accordingly fewer rows in the block, the height of the block does not change, and a white area is formed that does not go away and overlaps the data.
separate topic
[quote]
Farkhshatov Rodion wrote:
But here's another problem with it:
- Process at a stage from which there are many options for transition to others. Block with buttons in several rows.
- When switching to a stage from which there are fewer options for transitions, and accordingly fewer rows in the block, the height of the block does not change, and a white area is formed that does not go away and overlaps the data.
[/quote]
separate topic
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment
Donate
You don't have enough funds in your account Top up