How to force focus on a second window/dialog in MVVM?
I'm currently working on a WPF app and I am facing a situation.
To make it simple, I have a mainwindow with multiple UserControl in it. At some point, I have another window opening, and I want this window to always being focused, even if the user try to click on the other one.
I found some things about the Window.Activate() method. So I tried this solution. But it doesn't work like I would. I need my window to be the only one accessible for the user, and I don't want him to access the main one when the second one is not closed.
Obviously, I really want not to break the MVVM.
Any clue ?
.net wpf mvvm behavior
add a comment |
I'm currently working on a WPF app and I am facing a situation.
To make it simple, I have a mainwindow with multiple UserControl in it. At some point, I have another window opening, and I want this window to always being focused, even if the user try to click on the other one.
I found some things about the Window.Activate() method. So I tried this solution. But it doesn't work like I would. I need my window to be the only one accessible for the user, and I don't want him to access the main one when the second one is not closed.
Obviously, I really want not to break the MVVM.
Any clue ?
.net wpf mvvm behavior
add a comment |
I'm currently working on a WPF app and I am facing a situation.
To make it simple, I have a mainwindow with multiple UserControl in it. At some point, I have another window opening, and I want this window to always being focused, even if the user try to click on the other one.
I found some things about the Window.Activate() method. So I tried this solution. But it doesn't work like I would. I need my window to be the only one accessible for the user, and I don't want him to access the main one when the second one is not closed.
Obviously, I really want not to break the MVVM.
Any clue ?
.net wpf mvvm behavior
I'm currently working on a WPF app and I am facing a situation.
To make it simple, I have a mainwindow with multiple UserControl in it. At some point, I have another window opening, and I want this window to always being focused, even if the user try to click on the other one.
I found some things about the Window.Activate() method. So I tried this solution. But it doesn't work like I would. I need my window to be the only one accessible for the user, and I don't want him to access the main one when the second one is not closed.
Obviously, I really want not to break the MVVM.
Any clue ?
.net wpf mvvm behavior
.net wpf mvvm behavior
asked Nov 24 '18 at 13:03
Quentin S.Quentin S.
9611
9611
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If you want a single window to be the only one the user interacts with then use .ShowDialog rather than show.
Any instantiation of manipulation of windows is a view responsibility so put the code that will do that in one of your usercontrol or windows.
Then you need some way to make that happen from your viewmodel.
You can add a dependency property to your view and bind that to a property in the viewmodel then handle the change of that dependency property.
An alternative would be to use the pub/sub pattern and mvvmlight messenger or a bridging object like prism eventaggregator.
Or any number of other bridging mechanisms you could share via resources or dependency injection.
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%2f53458416%2fhow-to-force-focus-on-a-second-window-dialog-in-mvvm%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
If you want a single window to be the only one the user interacts with then use .ShowDialog rather than show.
Any instantiation of manipulation of windows is a view responsibility so put the code that will do that in one of your usercontrol or windows.
Then you need some way to make that happen from your viewmodel.
You can add a dependency property to your view and bind that to a property in the viewmodel then handle the change of that dependency property.
An alternative would be to use the pub/sub pattern and mvvmlight messenger or a bridging object like prism eventaggregator.
Or any number of other bridging mechanisms you could share via resources or dependency injection.
add a comment |
If you want a single window to be the only one the user interacts with then use .ShowDialog rather than show.
Any instantiation of manipulation of windows is a view responsibility so put the code that will do that in one of your usercontrol or windows.
Then you need some way to make that happen from your viewmodel.
You can add a dependency property to your view and bind that to a property in the viewmodel then handle the change of that dependency property.
An alternative would be to use the pub/sub pattern and mvvmlight messenger or a bridging object like prism eventaggregator.
Or any number of other bridging mechanisms you could share via resources or dependency injection.
add a comment |
If you want a single window to be the only one the user interacts with then use .ShowDialog rather than show.
Any instantiation of manipulation of windows is a view responsibility so put the code that will do that in one of your usercontrol or windows.
Then you need some way to make that happen from your viewmodel.
You can add a dependency property to your view and bind that to a property in the viewmodel then handle the change of that dependency property.
An alternative would be to use the pub/sub pattern and mvvmlight messenger or a bridging object like prism eventaggregator.
Or any number of other bridging mechanisms you could share via resources or dependency injection.
If you want a single window to be the only one the user interacts with then use .ShowDialog rather than show.
Any instantiation of manipulation of windows is a view responsibility so put the code that will do that in one of your usercontrol or windows.
Then you need some way to make that happen from your viewmodel.
You can add a dependency property to your view and bind that to a property in the viewmodel then handle the change of that dependency property.
An alternative would be to use the pub/sub pattern and mvvmlight messenger or a bridging object like prism eventaggregator.
Or any number of other bridging mechanisms you could share via resources or dependency injection.
answered Nov 24 '18 at 14:06
AndyAndy
2,9791106
2,9791106
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%2f53458416%2fhow-to-force-focus-on-a-second-window-dialog-in-mvvm%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