This question is locked. New answers and comments are not allowed.
I am using the RadPhoneApplicationFrame for my RootFrame.
If I enable fast app resume and want to enter the app via deeplink,
I can see the transitions of the old pages for a moment.
Is there any way to avoid this behaviour?
For reproduction:
1. download the sample from microsoft
2. change RootFrame = new RadPhoneApplicationFrame();
3. start the sample
4. create Page 3 Tile
5. restart app via app tile and go to page 2
6. exit via windows button
7 reenter via page 3 deeplink tile
--> Error: can see page 2 for a moment
If I enable fast app resume and want to enter the app via deeplink,
I can see the transitions of the old pages for a moment.
Is there any way to avoid this behaviour?
For reproduction:
1. download the sample from microsoft
2. change RootFrame = new RadPhoneApplicationFrame();
3. start the sample
4. create Page 3 Tile
5. restart app via app tile and go to page 2
6. exit via windows button
7 reenter via page 3 deeplink tile
--> Error: can see page 2 for a moment
5 Answers, 1 is accepted
0
Hello Andreas,
Thank you for contacting us.
I was able to reproduce the described issue (thanks to your detailed explain), but we are going to need a little more time to research how to fix it. I'll let you know when the fix is ready. I have updated your Telerik points for your cooperation.
Greetings,
Todor
the Telerik team
Thank you for contacting us.
I was able to reproduce the described issue (thanks to your detailed explain), but we are going to need a little more time to research how to fix it. I'll let you know when the fix is ready. I have updated your Telerik points for your cooperation.
Greetings,
Todor
the Telerik team
Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.
0
Accepted
Hello Andreas,
After reviewing your application again, it turned out that the issue that you experience is not caused by RadPhoneApplicationFrame. What happens is that you have the application in the memory and when you launch it again it resumes to the page where it was (Page2), then you navigate to the new page (Page3) and you see the transition between these pages (as expected). If you don't want to see this transition, you should disable the transition for the current page. For example, in App.xaml.cs you can do something like:
I hope this will help you.
Greetings,
Todor
the Telerik team
After reviewing your application again, it turned out that the issue that you experience is not caused by RadPhoneApplicationFrame. What happens is that you have the application in the memory and when you launch it again it resumes to the page where it was (Page2), then you navigate to the new page (Page3) and you see the transition between these pages (as expected). If you don't want to see this transition, you should disable the transition for the current page. For example, in App.xaml.cs you can do something like:
private
PhoneApplicationPage page;
// Code to execute when the application is activated (brought to foreground)
// This code will not execute when the application is first launched
private
void
Application_Activated(
object
sender, ActivatedEventArgs e)
{
page = RootFrame.Content
as
PhoneApplicationPage;
if
(page !=
null
)
{
page.SetValue(RadTransitionControl.TransitionProperty,
new
RadEmptyTransition());
RadPhoneApplicationFrame frame = RootFrame
as
RadPhoneApplicationFrame;
frame.PageTransitionCompleted += frame_PageTransitionCompleted;
}
mustClearPagestack = CheckDeactivationTimeStamp();
}
void
frame_PageTransitionCompleted(
object
sender, EventArgs e)
{
page.ClearValue(RadTransitionControl.TransitionProperty);
(RootFrame
as
RadPhoneApplicationFrame).PageTransitionCompleted -= frame_PageTransitionCompleted;
}
I hope this will help you.
Greetings,
Todor
the Telerik team
Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.
0
Andreas
Top achievements
Rank 1
answered on 21 Dec 2012, 10:49 AM
Thank you for looking into this issue.
Your solution did not solve my problem completely, but it improved the behaviour.
Your solution did not solve my problem completely, but it improved the behaviour.
0
Hello Andreas,
Yes, my proposal doesn't completely solve the issue, it is just a workaround, because it just removes the animation added from RadPhoneApplicationFrame, but you still navigate to Page2. In order to completely avoid the issue you have to think of another way of remembering the state of the application, without keeping it in the memory, otherwise it will keep resuming where it was (in that case Page2) no matter how you start it (from the primary tile or from manually created secondary tile) since it is the default behavior in Windows Phone.
Kind regards,
Todor
the Telerik team
Yes, my proposal doesn't completely solve the issue, it is just a workaround, because it just removes the animation added from RadPhoneApplicationFrame, but you still navigate to Page2. In order to completely avoid the issue you have to think of another way of remembering the state of the application, without keeping it in the memory, otherwise it will keep resuming where it was (in that case Page2) no matter how you start it (from the primary tile or from manually created secondary tile) since it is the default behavior in Windows Phone.
Kind regards,
Todor
the Telerik team
Have a suggestion or face a problem - you can use the Ideas & Feedback portal to submit ideas, feedback and vote for them.
0
Samuel
Top achievements
Rank 1
answered on 09 Aug 2014, 02:14 AM
If you hide the content of the page with
then maybe you can further minimize the problem to an almost acceptable level.
page.Content.Visibility = Visibility.Collapsed;
then maybe you can further minimize the problem to an almost acceptable level.