Setting Flyout to Main Frame Navigation(Windows 8.1 app store) - windows-store-apps

I have created login screen using settings flyout control in Windows 8.1 store app. I need to navigate to Mainpage.xaml in case user successfully entered the login credentials.
How can handle parent Frame navigation from Settings Flyout.
Thanks in Advance.

You can hide the SettingsFlyout and Navigate to the MainPage using Frame Navigation, after the required validation.
[C#]:
new SettingsFlyout().Hide();
this.Hide();
(Window.Current.Content as Frame).Navigate(typeof(MainPage));

Guidance is not to preform navigation from a SettingsFlyout (see “Inappropriate Use of Settings” section). Generally, a Popup is a better option for a login dialog and a popup would allow you to easily navigate to the main page.

Related

Hiding a ribbon button when specific Dynamics CRM Web Resource is in context

Like most of dynamics crm programmers know, we can add "web resources that are not associated with any entity" to the sitemap. If such a customization is made, when user clicks that link, web resource will be opened and the buttons in the application ribbon will be added to the ribbon section of the dynamics crm.
What I am wondering is if there is any way I can hide this global buttons that are in the application ribbon based on the web resource on the page.
Let's say I added more than one web resources to my sitemap, namely a.htm and b.htm. Let's say I have a custom button named x in the application ribbon. Right now x is displayed both for a.htm and b.htm, but in reality I would like to hide the button when user clicks on b.htm from the sitemap.
Is there a way to accomplish that?
You could use the following (unsupported) code to hide the Ribbon button (the 'Run Workflow' button in this example):
var btnRunWorklfow=top.document.getElementById("account|NoRelationship|Form|Mscrm.Form.account.RunWorkflow-Large");
btnRunWorklfow.style.display='none';
You can also use ribbon editor available in codeplex to disable your button based on your javascript.
Refer to: http://crmvisualribbonedit.codeplex.com/
I figured there is no supported way of doing this.

Windows phone 8.1 Universal app - Show the Button all the time

In Windows phone 8.1 universal app, Appbar currently support only icons, not the buttons. If i use the button, Button is hidden below the keyboard.
I need help to achieve either one of the below
I want to show the Button below the Keyboard, Any ways to achieve it?
Or, Move the Button above the Keyboard when keyboard appears. When Keyboard is not shown, Button should be at the Bottom of the page. Is there any way to do this?
It helps User to see the Button clearly all the time.
React on an OnInputPaneShowing event. The size of the input control is passed into this function and you can update the position of the button according this size.
See MSDN respond to the keyboard presence and MSDN occluded rect property for more info on how to do this.

How can a jsp based application launch a browser with no window frame or tabs or menu or toolbar

I am looking for a way to launch my application in a browser with window frame or tabs or menu or toolbar, is there any way i could achieve that.
For instance i want to launch my application without the part marked in orange. (without tabs or possibility of creating a new tab) and the settings button beside the address bar
Update:
i am adding a image of what i am trying to accomplish...
Thanks in advance

How to navigate within settings flyout in Windows 8.1 Store app?

I am working on my first Win 8.1 Store app and have some trouble understanding the SettingsFlyout.
Thanky to the docs creating Flyouts for my custom settings and adding them to the Settings Charm is not a problem.
However I have not been able to find out how navigate within the Flyout. I would like to create the following behavior as it can be seen in the Mail App:
Swipe from the right to show charms
Click on "Settings" to show the settings pane
Click on Account to show the "Accounts List Flyout"
On the "Accounts List Flyout" click on an account show its settings
The settings of the selected account are shown within the Flyout
Using the Back button brings you back to the accounts list
Steps 1-3 are no problem. But how do I manage the other steps? How can I navigate one lever deeper into the settings and use the Back button to go up again?
For Step 5 you can do something like
var newFlyout = new AccountFlyout(id);
newFlyout.ShowIndependent();
Now you are done with Step 5.
In the AccountFlyout.xaml.cs file hook on the BackClick event (in constructor) and then do something like:
void OnAccountFlyoutBackClick(object sender, BackClickEventArgs e)
{
// go back to the accounts list
var listFlyout = new AccountsListFlyout();
listFlyout.Show();
}
Clicking the Back button being on an Account will now go 'back' to the Accounts List flyout.
Yes, this is not very 'MVVM' friendly (if you perform the navigation in the VM you must know about the Flyouts and if you do it in the 'code-behind' you are not 100% MVVM conform) but it gets the job done without creating unnecessary complexity :)

Chrome app navigate htmls without creating windows

I'm creating a chrome packaged app, and I need to navigate my htmls without creating a lot of windows, like, if the user click one button, it opens the html in the same window the user are.
Is it even possible? If not, is there a way to make windows modal? So the user can't focus another window without closing the current?
Packaged apps intentionally do not support navigation. Apps are not in a browser, there is no concept of forward, back, or reload. Applications which do require the concept of navigation, or modal dialogs, should use a user interface framework that supports that functionality. In fundamentals, you can navigate by manipulating the DOM or by using CSS to animate and control visibility of components of your app.
The page you want to navigate to can be opened in a new window, then the previous page can be closed.
function navigateToLink (link) {
var current = chrome.app.window.current();
chrome.app.window.create(link);
current.close();
}