You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, dear developers!
I am using the app Cyclestreets! I like the app but I find that some loss error when I rotate the phone.
The first is that the UI will go back to its previous one (however, I think it should still be at the same UI after the rotation).
The second is that the previous input will lose if I rotate phone When I try to find a place. I think this may affect user experience.
Do you think that these errors could be fixed? For example, by saving the return value of dialog.isShowing() in onPause(), the UI state of the dialog could be saved. In addition, the previous input can also be saved through saving the text of the editable widget. In this way, you can restore the UI state the same as before I rotate the phone.
Here are the snapshots to illustrate these errors:
No.1 before rotation
No.1 after rotation
No.2 before rotation
No.2 after rotation
The text was updated successfully, but these errors were encountered:
Hi, dear developers!
I am using the app Cyclestreets! I like the app but I find that some loss error when I rotate the phone.
The first is that the UI will go back to its previous one (however, I think it should still be at the same UI after the rotation).
The second is that the previous input will lose if I rotate phone When I try to find a place. I think this may affect user experience.
Do you think that these errors could be fixed? For example, by saving the return value of
dialog.isShowing()
inonPause()
, the UI state of the dialog could be saved. In addition, the previous input can also be saved through saving the text of the editable widget. In this way, you can restore the UI state the same as before I rotate the phone.Here are the snapshots to illustrate these errors:
No.1 before rotation
No.1 after rotation
No.2 before rotation
No.2 after rotation
The text was updated successfully, but these errors were encountered: