在 WP7 中处理双向导航？
基本上，当我的应用程序加载时，我的第一个屏幕是 MainPage.xaml，我将其视为加载屏幕。这是为了使屏幕更新显示得更快。从加载屏幕，用户会自动导航到另一个包含名为 Content.xaml 的内容的页面。
问题是第一种方式工作正常，
SpashScreenImage --> MainPage.xaml -->内容.xaml
，但如果用户决定点击后退按钮，他们会转到加载页面，但随后会将他们导航回内容页面。
MainPage.xaml <-- Content.xaml
MainPage.xaml -->内容.xaml
如果我知道它们来自哪个页面，这看起来很容易解决。 有没有办法检测用户正在浏览哪个页面？这样我才能妥善处理。
编辑：我的主要目标是获取当您导航到 WP7 中的全景页面时发生的动画（幻灯片效果）。到目前为止，我能够触发此事件的唯一方法是手动导航到页面，就像我在问题中建议的那样（Content.xaml == Panorama Page），或者重新激活该页面上的应用程序。
basically when my app loads my first screen is MainPage.xaml, which I'm treating as a loading screen. This is to make an update to screen appear faster. From the loading screen the user is automatically navigated to another page that contains content called Content.xaml respectively.
The problem is navigating the first way works fine,
SpashScreenImage --> MainPage.xaml --> Content.xaml
but if the user decides to hit the back button they go to the loading page, but then that navigates them back to the content page.
MainPage.xaml <-- Content.xaml
MainPage.xaml --> Content.xaml
This looks real easy to solve if I knew what page they were coming from.
Is there a way to detect what page the user is navigating from? That way I could handle it properly.
EDIT: My main objective is to get the animation that occurs when you navigate to a Panorama page in WP7 (Slide effect). So far the only way I've been able to trigger this event is by manually navigating to the page, like I suggested in my question (Content.xaml == Panorama Page), or by reactivating the app on that page.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这里最简单的方法是完全避免瞬时加载/启动页面，将其设为位于 Content.xaml 页面顶部的全屏 UserControl。
加载完成后，只需在 UserControl 上设置 Visibility=Collapsed，您就会立即进入内容页面。
现在，当用户按回键时，您的应用程序将按预期退出。
当您的应用程序已进行逻辑删除时，此方法也非常有效。
The easiest approach here is to avoid the transient loading/splash page altogether, by making it a full-screen UserControl that sits on top of your Content.xaml page.
When the loading is complete, just set Visibility=Collapsed on the UserControl and you are immediately on your content page.
Now when the user presses back, your app exits as expected.
This approach also works great when your app is Tombstone'ed.