Handling Navigation in Windows Phone 8.1 app - windows-phone-8.1

I have 2 pages in my Windows Phone 8.1 app.
The 1st page displays 9 image buttons. Its purpose is to allow the User to enter their 4 digit PIN to proceed to the next screen.
The 2nd page display other information.
I have an image button on my 2nd page that when pressed will take the User back to the 1st page.
If I press that button it will take me to 1st page.
If I then press the back button on my phone it will take me back to the 2nd page.
I had expected the app to exit?
What am i missing from my logic here?
thanks

Related

Windows Phone Sliding Page/Control

I want to design a page on windows phone 8.1 which should have 2 pages in a screen.
One page should always be visible.
Second page should come up when user tries to "hold and tries to swap to right on the left corner of the visible screen"
[The Second Page i'm planning to make it as a User control. so that i can put it on different pages as a hidden control and will show up when user tries hold and drag from left to right, action on a page just the way action center shows in phone]
It's same way how action center page comes up when user hold's and drag down the top corner of phone screen windows phone 8.1, but I'm trying to do the same but from the dragging should be from left side of the Screen.
I have tried experimenting with Manipulation methods could achieve the expected result.
Hope i have conveyed my question properly. :)
Please share your thought's.
Thanks.
Your question is not very clear, but is That what you are looking for ?
Application side menu (NavigationDrawer) ?
Checkout this project, see if it suit your need. You need some changes in source to make it work with Windows 8.1

Windows Phone notification content sometimes not displayed

I have a simple windows phone 8 project that consists in receiving notifications from a server, and displays its content on a MainPage.xaml.
The notification has a title, a subject and a content. I have faced a strange issue on Nokia devices that have a notification center, where you can see all the received notifications which are not opened yet. I have noticed that those notification are separated in 2 clickable lines:
The first line (icon and application name) opens the
application.
The second line (notification title and subject) opens the
application with the notification content.
During my tests, I sometimes missclicked on the first line, which opens my application without the notification's content (and so did not understood what the hell was happening). As I am not a Windows Phone user, can you confirm this is a common behavior on Nokia devices ? Or is there a way to always open the application with the notification content, even if you clicked on the first line ?

iOS7 - <select> menu not reset on history.back / browser back button

This is a strange bug that occurs on the iPhone 5 when navigating back to a previous page.
Here's the steps to reproduce the bug on an iPhone 5:
Select a menu option that directs to a new page
From the new page press the browser back button
Try and navigate to the same page again using the same menu
An example page to try this on is here. On this page, select 'Javascript Tutorials' from the first menu on the page. Then follow steps above...
In my situation there is no go button to follow the link (like the second menu on the example page). The option is followed when clicked. The problem with this is that because the page you returned from is selected in the menu, you are unable to navigate to it. You cant re-select it.
My question: Is this a known iOS 7 bug? And is there a solution? My search has come up empty so far.
My JS code selects the first option when the menu is generated on page load. And as said, this bug only occurs on the iPhone.
This is not an iOS 7/iPhone 5 bug.
I can recreate it in Chrome on Windows 7.
As you said,
"because the page you returned from is selected in the menu,
you are unable to navigate to it"
The menu is pre-selected because of autocomplete behavior
When you press browser "back" in step 2 (versus page refresh), browser remembers the state you left the select in
https://stackoverflow.com/a/2699400/1175496
When you re-select an option that is already selected
You haven't changed anything; so the change event doesn't fire
Scripts listening for that event (as with the onChange attribute in your example) won't send you to the page
I fix this by putting autocomplete="off" attribute on the form element containing your select;
this prevents number 1, which prevents number 2.

selecting an item opens edit mode in windows 8 apps C#.net

I have a windows 8 app, in which i show the list of students as tiles. When a tile is tapped on, the app bar opens which give the option to edit. My question is; when the tile is tapped, is it fine to go to the Edit window rather than opening the app bar. Does windows 8 app guidelines allow this.
I have gone through the windows 8 guidelines but it has left me confused if its the right way or not.
Thanks in advance.
I think the best way to do this must be that on click of the tile you should open the edit window. And the appbar must have only add button, so that in case the user wants to add a student he can do so through the app bar. I feel this is the correct user experience.

Windows Phone | Dialog Window Cross Icon and Hardware Back Button

I am developing a windows Phone Application. I have a pop up displayed when an icon is tapped on the screen. That pop has a cross icon on the top right corner so that user can tap on the cross icon and pop up gets closed?
Pop also gets closed when user presses the hardware back button.
I want to ask if it is OK to place a cross icon on pop up windows because there is two way to close the same pop(from hardware back button and from cross icon)????
Is it OK from Windows Phone Certification certification point of View.
From certification point of view its not a problem as long as the back button also does the same.
Just remember that many users have had WP for a while and you as a developer are expect to support native mechanisms while doing every thing you want to do on top of it.