I am new to windows phone 7.
I have a .xaml page, in that i have lot of TextBoxes and DatePickers to enter User data, If he Submit form i am inserting User data in to Database. But my problem is, in that form i have Country Button if he clicks on that button i am going to different page, in that page he can select Country then i am returning back to the previous form. While returning to Previous page data entered by user will be gone. But here i need to maintain the State(date entered by user should reappear on Form) in that page.
Ho can i do this in Windows Phone 7?
Consider using the ListPicker from Windows Phone Toolkit for choosing the Country. This will not delete your control states
You will want to store this data in the page state. This way you can reconstruct the page when it is navigated to and also after the application is suspended. Otherwise, after your app is tombstoned you will lose this data and after your app rehydrates the user will have to enter it again. If you save it to the page state, you can restore the page to make it appear as if tombstoning never occurred.
There is a lot of documentation on msdn to help you manage application state.
Related
after successfull login automation when its redirects too dashboard page i am not able too perform any activity on dashboard page using UIPath Studio
i was trying too perform click activity on dashboard page elemnts
Ensure that your window selector is updated once you move on to the next page. I have seen in almost every single automation I have created, the Login page has a different window title than the actual web app screens after login.
With the Modern Design Experience in UiPath, the Window selector is a little hidden from the rest of the selector, so make sure you open the Window Selector dropdown in the Selector Window (or modify the Window Selector property in the properties pane) to modify that when advancing from the Login screen to the main app screen.
I am creating a prototype web app using Oracle Weblogic/ADF. I am using JDeveloper 11.1.1.6.0.
I have a basic application with one entity object and one view object. One of the requirements I is that once data is changed it must be digitally signed. I am using a applet/servlet based solution to get this done.
Once a user decides to edit an entry in the table they are taken to a page that shows a two-column form layout. On this page is a button that, when clicked, brings up an ADF dialog window. On this page there is a button called "Sign". Once the user clicks the "Sign" button some JavaScript executes that communicates with the embedded applet. This embedded applet in turn communicates with a servlet and returns a string representing a signature. This process is task-flow based.
The issue I am having is that for SOME users (IE 8, Win 7 Enterprise) once they click the "Sign" button on the popup they are shown the following popup:
If they click "OK", the page reloads and when they click "Sign" again the process repeats resulting in a loop. Initially I thought the alert was coming from IE, but upon further research it seems that the alert is coming from ADF. I have NO idea WHY they are getting this message as there are NO dependent dialogs. I have tried setting the "uncommitted data warning" to off for the document but I still get the same popup. Also the message ONLY appears for SOME users running IE 8 on top of Windows 7.
Does anyone have any ideas as to how to get this popup to stop and/or WHY it is happening?
ANY help would be greatly appreciated as I am stumped.
Thanks.
disable the uncommitted data warning property on af:document
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e12419/tagdoc/af_document.html
Frank
Is it allowed by Windows Phone application certification rules, to only have users be able to return to a previous screen with the use of a hardware back button?
In my scenario, a user clicks on a setting button and lands at a settings page. He changes settings if he decides to, and all the changes get saved automatically, like in iOS.
But currently, the only way for the user to get out of the settings screen, is to press a hardware Back button on the phone.
Will such implementation of navigation functionality pass the Windows Phone certification?
Yes - leave the back button as the navigation method to get back to your main page after visiting the settings page. Not only is this allowed, but it is the desired method of back navigation, and it is what Windows Phone users expect. Here is a great article on the subject: http://blogs.msdn.com/b/ptorr/archive/2011/10/06/back-means-back-not-forwards-not-sideways-but-back.aspx
As far as I understand the terms of the navigation guideline is your usage the right way to go.
Back button
Pressing the back button from the first screen of an application must exit the application.
Pressing the back button must return the application to the previous page.
If the current page displays a context menu or a dialog, the pressing the Back button must close the menu or dialog and cancel the
backward navigation to the previous page.
You should only implement back button behaviors that navigate back or dismiss context menus or modal dialog boxes. All other
implementations are prohibited.
See this cheat sheet for more informations on the design guidelines.
When user click the Bing Search button, this will cause Deactivated event. So, I have these questions.
1) When user press Bing Search Button, How to I store the data. What type of Data can be stored and What to use to store?
How do I store stream type data?
2) When user Click Back Button after pressing Bing Search Button, this will reActivate ? What event will this be and How do I get back the data that I store in (1)?
Thanks
Jeff Prosise's Real-World Tombstoning in Silverlight for Windows Phone 7 will tell you everything you need to know about tombstoning:
Part 1
Part 2
Part 3
Part 4
For my Windows Phone 7 app, I have a main panorama page which opens up into a pivot control. The main panorama page correctly calls Activated/Deactivated, and restores correctly.
But after visiting the pivot page, pressing the Windows key doesn't call Deactivated.
When the app is relaunched with the back button, it goes right to how the page looked before tombstoning, but Activated is not called, and the page is not usable, and the back key doesn't work.
Has anyone else experienced this problem before?
If you just go to the Start screen then your application MAY not get tombstoned. This is expected behaviour.
If you open another application or open search from within your application you should experience tombstoning.