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
I am currently using page's onappearing event to retrieve data from database and to get page updated when users navigate to the page. The page is registered as singleton since it is the main interface of my app, I do not want users to wait for page to be constructed every time. But I find if a user clicks a button to navigate to another page and backward, if the old page is in the async onappearing function, the event will not fire again during backward progress even when the user changed some data on the new page(I have to refresh the old page now).
My idea is to lock all the buttons' isenabled property when retrieving data, is there any better ways to solve the problem?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am currently using page's onappearing event to retrieve data from database and to get page updated when users navigate to the page. The page is registered as singleton since it is the main interface of my app, I do not want users to wait for page to be constructed every time. But I find if a user clicks a button to navigate to another page and backward, if the old page is in the async onappearing function, the event will not fire again during backward progress even when the user changed some data on the new page(I have to refresh the old page now).
My idea is to lock all the buttons' isenabled property when retrieving data, is there any better ways to solve the problem?
Beta Was this translation helpful? Give feedback.
All reactions