progress ring in xaml not preventing the game pad controller action?
I have implemented the uwp loader in my xaml page to prevent the user interaction.
<ProgressRing x:Name="loader" Width="70" Height="70" Foreground="White"/>
but the problem is controller actions still working which allows the user interactions.Is there any possibility for preventing the controller actions while the loader is working?
xaml uwp xbox
asked Nov 14 '18 at 3:59
Haritha EsHaritha Es
486
add a comment |
I have implemented the uwp loader in my xaml page to prevent the user interaction.
<ProgressRing x:Name="loader" Width="70" Height="70" Foreground="White"/>
but the problem is controller actions still working which allows the user interactions.Is there any possibility for preventing the controller actions while the loader is working?
xaml uwp xbox
asked Nov 14 '18 at 3:59
Haritha EsHaritha Es
486
Also you should consider calling Progress Ring asynchronously and disable it when you dont need it.
– Venkat
Nov 15 '18 at 15:53
add a comment |
I have implemented the uwp loader in my xaml page to prevent the user interaction.
<ProgressRing x:Name="loader" Width="70" Height="70" Foreground="White"/>
but the problem is controller actions still working which allows the user interactions.Is there any possibility for preventing the controller actions while the loader is working?
xaml uwp xbox
asked Nov 14 '18 at 3:59
Haritha EsHaritha Es
486
I have implemented the uwp loader in my xaml page to prevent the user interaction.
<ProgressRing x:Name="loader" Width="70" Height="70" Foreground="White"/>
but the problem is controller actions still working which allows the user interactions.Is there any possibility for preventing the controller actions while the loader is working?
xaml uwp xbox
xaml uwp xbox
asked Nov 14 '18 at 3:59
Haritha EsHaritha Es
486
asked Nov 14 '18 at 3:59
Haritha EsHaritha Es
486
edited Nov 14 '18 at 4:36
Haritha Es
asked Nov 14 '18 at 3:59
Haritha EsHaritha Es
486
asked Nov 14 '18 at 3:59
Haritha EsHaritha Es
486
asked Nov 14 '18 at 3:59
Haritha EsHaritha Es
486
486
Also you should consider calling Progress Ring asynchronously and disable it when you dont need it.
– Venkat
Nov 15 '18 at 15:53
add a comment |
Also you should consider calling Progress Ring asynchronously and disable it when you dont need it.
– Venkat
Nov 15 '18 at 15:53
Also you should consider calling Progress Ring asynchronously and disable it when you dont need it.
– Venkat
Nov 15 '18 at 15:53
Also you should consider calling Progress Ring asynchronously and disable it when you dont need it.
– Venkat
Nov 15 '18 at 15:53
add a comment |
1 Answer
1
active
oldest
votes
Progress ring is only a visual indicator for user that there is some longer action taking place. It does not prevent him from doing anything.
You are too unspecific with your question, but there are many ways of suppressing user input depending on your aproach to handling gamepad.
You can, for example set IsEnabled attribute for the whole page to false (works only for XAML elements).
You can detach event handlers for keydown event.
Or you can create a boolean variable (e.g. canplay) which you set to to false whenever you want to suppress user input, and in the function when you processing gamepad buttons you can check its value:
if (canplay)
{
//process gamepad buttons
}
answered Nov 15 '18 at 10:41
MailoszMailosz
647
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53293008%2fprogress-ring-in-xaml-not-preventing-the-game-pad-controller-action%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Progress ring is only a visual indicator for user that there is some longer action taking place. It does not prevent him from doing anything.
You are too unspecific with your question, but there are many ways of suppressing user input depending on your aproach to handling gamepad.
You can, for example set IsEnabled attribute for the whole page to false (works only for XAML elements).
You can detach event handlers for keydown event.
Or you can create a boolean variable (e.g. canplay) which you set to to false whenever you want to suppress user input, and in the function when you processing gamepad buttons you can check its value:
if (canplay)
{
//process gamepad buttons
}
answered Nov 15 '18 at 10:41
MailoszMailosz
647
add a comment |
Progress ring is only a visual indicator for user that there is some longer action taking place. It does not prevent him from doing anything.
You are too unspecific with your question, but there are many ways of suppressing user input depending on your aproach to handling gamepad.
You can, for example set IsEnabled attribute for the whole page to false (works only for XAML elements).
You can detach event handlers for keydown event.
Or you can create a boolean variable (e.g. canplay) which you set to to false whenever you want to suppress user input, and in the function when you processing gamepad buttons you can check its value:
if (canplay)
{
//process gamepad buttons
}
answered Nov 15 '18 at 10:41
MailoszMailosz
647
add a comment |
Progress ring is only a visual indicator for user that there is some longer action taking place. It does not prevent him from doing anything.
You are too unspecific with your question, but there are many ways of suppressing user input depending on your aproach to handling gamepad.
You can, for example set IsEnabled attribute for the whole page to false (works only for XAML elements).
You can detach event handlers for keydown event.
Or you can create a boolean variable (e.g. canplay) which you set to to false whenever you want to suppress user input, and in the function when you processing gamepad buttons you can check its value:
if (canplay)
{
//process gamepad buttons
}
answered Nov 15 '18 at 10:41
MailoszMailosz
647
Progress ring is only a visual indicator for user that there is some longer action taking place. It does not prevent him from doing anything.
You are too unspecific with your question, but there are many ways of suppressing user input depending on your aproach to handling gamepad.
You can, for example set IsEnabled attribute for the whole page to false (works only for XAML elements).
You can detach event handlers for keydown event.
Or you can create a boolean variable (e.g. canplay) which you set to to false whenever you want to suppress user input, and in the function when you processing gamepad buttons you can check its value:
if (canplay)
{
//process gamepad buttons
}
answered Nov 15 '18 at 10:41
MailoszMailosz
647
answered Nov 15 '18 at 10:41
MailoszMailosz
647
answered Nov 15 '18 at 10:41
MailoszMailosz
647
answered Nov 15 '18 at 10:41
MailoszMailosz
647
647
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53293008%2fprogress-ring-in-xaml-not-preventing-the-game-pad-controller-action%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Also you should consider calling Progress Ring asynchronously and disable it when you dont need it.
– Venkat
Nov 15 '18 at 15:53