Mixing
C# Topmost=true - restrict to application
Our Application is displaying an "update-hint", if a new version is available.
This Update-hint should be "topmost" within the application, but, if the application is minimized, or send to the background, the update-hint should vanish as well..
Just using
this.TopMost = true;
will overlay "ANY" application that is currently running...
Is there a way to just "overlay" windows generated by the current application?
Desired:
application shows update-hint on top of every window, while application is in the foreground. Switching to another application will also send the update-hint to the background.
Desired: Update-Hint overlays ANY window of the current application:
Not desired: Update-Hint overlays FOREIGN applications as well:
c# winforms
asked Nov 20 '18 at 21:31
dognosedognose
15.8k64690
|
show 19 more comments
Our Application is displaying an "update-hint", if a new version is available.
This Update-hint should be "topmost" within the application, but, if the application is minimized, or send to the background, the update-hint should vanish as well..
Just using
this.TopMost = true;
will overlay "ANY" application that is currently running...
Is there a way to just "overlay" windows generated by the current application?
Desired:
application shows update-hint on top of every window, while application is in the foreground. Switching to another application will also send the update-hint to the background.
Desired: Update-Hint overlays ANY window of the current application:
Not desired: Update-Hint overlays FOREIGN applications as well:
c# winforms
asked Nov 20 '18 at 21:31
dognosedognose
15.8k64690
Make sure the main form is the owner of the floating form.
– LarsTech
Nov 20 '18 at 21:34
Windows 10 has a Notification System for just this kind of thing. Your current itteration overlaps with this article: blogs.msdn.microsoft.com/oldnewthing/20110310-00/?p=11253
– Christopher
Nov 20 '18 at 21:38
1
@Christopher That article is not what the OP issue is.
– LarsTech
Nov 20 '18 at 21:39
@LarsTech explicit setting the owner has no impact at all...
– dognose
Nov 20 '18 at 21:42
1
That's a special property you have to custom write. lol
– Michael Puckett II
Nov 20 '18 at 22:20
|
show 19 more comments
Our Application is displaying an "update-hint", if a new version is available.
This Update-hint should be "topmost" within the application, but, if the application is minimized, or send to the background, the update-hint should vanish as well..
Just using
this.TopMost = true;
will overlay "ANY" application that is currently running...
Is there a way to just "overlay" windows generated by the current application?
Desired:
application shows update-hint on top of every window, while application is in the foreground. Switching to another application will also send the update-hint to the background.
Desired: Update-Hint overlays ANY window of the current application:
Not desired: Update-Hint overlays FOREIGN applications as well:
c# winforms
asked Nov 20 '18 at 21:31
dognosedognose
15.8k64690
Our Application is displaying an "update-hint", if a new version is available.
This Update-hint should be "topmost" within the application, but, if the application is minimized, or send to the background, the update-hint should vanish as well..
Just using
this.TopMost = true;
will overlay "ANY" application that is currently running...
Is there a way to just "overlay" windows generated by the current application?
Desired:
application shows update-hint on top of every window, while application is in the foreground. Switching to another application will also send the update-hint to the background.
Desired: Update-Hint overlays ANY window of the current application:
Not desired: Update-Hint overlays FOREIGN applications as well:
c# winforms
c# winforms
asked Nov 20 '18 at 21:31
dognosedognose
15.8k64690
asked Nov 20 '18 at 21:31
dognosedognose
15.8k64690
edited Nov 20 '18 at 22:07
dognose
asked Nov 20 '18 at 21:31
dognosedognose
15.8k64690
asked Nov 20 '18 at 21:31
dognosedognose
15.8k64690
asked Nov 20 '18 at 21:31
dognosedognose
15.8k64690
15.8k64690
Make sure the main form is the owner of the floating form.
– LarsTech
Nov 20 '18 at 21:34
Windows 10 has a Notification System for just this kind of thing. Your current itteration overlaps with this article: blogs.msdn.microsoft.com/oldnewthing/20110310-00/?p=11253
– Christopher
Nov 20 '18 at 21:38
1
@Christopher That article is not what the OP issue is.
– LarsTech
Nov 20 '18 at 21:39
@LarsTech explicit setting the owner has no impact at all...
– dognose
Nov 20 '18 at 21:42
1
That's a special property you have to custom write. lol
– Michael Puckett II
Nov 20 '18 at 22:20
|
show 19 more comments
Make sure the main form is the owner of the floating form.
– LarsTech
Nov 20 '18 at 21:34
Windows 10 has a Notification System for just this kind of thing. Your current itteration overlaps with this article: blogs.msdn.microsoft.com/oldnewthing/20110310-00/?p=11253
– Christopher
Nov 20 '18 at 21:38
1
@Christopher That article is not what the OP issue is.
– LarsTech
Nov 20 '18 at 21:39
@LarsTech explicit setting the owner has no impact at all...
– dognose
Nov 20 '18 at 21:42
1
That's a special property you have to custom write. lol
– Michael Puckett II
Nov 20 '18 at 22:20
Make sure the main form is the owner of the floating form.
– LarsTech
Nov 20 '18 at 21:34
Make sure the main form is the owner of the floating form.
– LarsTech
Nov 20 '18 at 21:34
Windows 10 has a Notification System for just this kind of thing. Your current itteration overlaps with this article: blogs.msdn.microsoft.com/oldnewthing/20110310-00/?p=11253
– Christopher
Nov 20 '18 at 21:38
Windows 10 has a Notification System for just this kind of thing. Your current itteration overlaps with this article: blogs.msdn.microsoft.com/oldnewthing/20110310-00/?p=11253
– Christopher
Nov 20 '18 at 21:38
1
1
@Christopher That article is not what the OP issue is.
– LarsTech
Nov 20 '18 at 21:39
@Christopher That article is not what the OP issue is.
– LarsTech
Nov 20 '18 at 21:39
@LarsTech explicit setting the owner has no impact at all...
– dognose
Nov 20 '18 at 21:42
@LarsTech explicit setting the owner has no impact at all...
– dognose
Nov 20 '18 at 21:42
1
1
That's a special property you have to custom write. lol
– Michael Puckett II
Nov 20 '18 at 22:20
That's a special property you have to custom write. lol
– Michael Puckett II
Nov 20 '18 at 22:20
|
show 19 more comments
2 Answers
2
active
oldest
votes
Despite the name of the property, TopMost is actually your enemy here. To make a "floating form" stay above a main form, without obscuring other applications when they get focus, try it this way:
FormX f = new FormX();
f.Show(this);
"this" in this example, is the main form instance. It means the form you created is now owned by the main form, and will make it float above it. You get the added benefit of, when minimizing the main form, the floating forms will disappear, too.
answered Nov 20 '18 at 23:15
LarsTechLarsTech
69.9k12105158
Thanks for your example. This will work, if the "target" is to keep the floating form just on top of the main-window. However, this approach would allow "other" forms of the application to overlay the floating form - and obviously I can't callf.Show(this)for more than one form.
– dognose
Nov 21 '18 at 11:19
@dognose What you really want my man is to switch to WPF where problems like are long forgotten.
– Michael Puckett II
Nov 21 '18 at 12:55
@dognose That's just a different issue. I would re-think this whole update-floating-form concept and just show a toast notification or something else. To be honest, annoying an end-user with the update form is just...annoying.
– LarsTech
Nov 21 '18 at 14:53
@LarsTech See my answer, I found a way to change the owner "easily" to handle this. Yep, it should be annoying, cause people should update. (especially those who never shutdown their pc and/or application)
– dognose
Nov 21 '18 at 16:55
add a comment |
I figured out a way to solve it.
Setting the owner of the UpdateHint is required, but in order to keep it on top of every application window, one has to change the owner, if a new Window is either shown, or activated.
Within our application, every Form is inheriting InterceptorForm, so all I had to do was to modify the InterceptorForm accordingly:
Change the Owner to this, except if there is no dialog, or this is the dialog itself:
public class InterceptorForm : Form
{
protected override void OnLoad(EventArgs e)
{
...
if (this.GetType() != typeof(UpdateHint) && MainWindow.updateHint != null)
{
Log.t("Setting owner on update hint during onload: " + this.GetType());
MainWindow.updateHint.Owner = this;
}
base.OnLoad(e);
}
and
protected override void OnActivated(EventArgs e)
{
if (this.GetType() != typeof(UpdateHint) && MainWindow.updateHint != null)
{
Log.t("Setting owner on update hint: " + this.GetType());
MainWindow.updateHint.Owner = this;
}
base.OnActivated(e);
}
}
The UpdateHint now stays on top of every window belonging to our application, but can be overlayed by any other application.
answered Nov 21 '18 at 16:53
dognosedognose
15.8k64690
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%2f53401866%2fc-sharp-topmost-true-restrict-to-application%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Despite the name of the property, TopMost is actually your enemy here. To make a "floating form" stay above a main form, without obscuring other applications when they get focus, try it this way:
FormX f = new FormX();
f.Show(this);
"this" in this example, is the main form instance. It means the form you created is now owned by the main form, and will make it float above it. You get the added benefit of, when minimizing the main form, the floating forms will disappear, too.
answered Nov 20 '18 at 23:15
LarsTechLarsTech
69.9k12105158
Thanks for your example. This will work, if the "target" is to keep the floating form just on top of the main-window. However, this approach would allow "other" forms of the application to overlay the floating form - and obviously I can't callf.Show(this)for more than one form.
– dognose
Nov 21 '18 at 11:19
@dognose What you really want my man is to switch to WPF where problems like are long forgotten.
– Michael Puckett II
Nov 21 '18 at 12:55
@dognose That's just a different issue. I would re-think this whole update-floating-form concept and just show a toast notification or something else. To be honest, annoying an end-user with the update form is just...annoying.
– LarsTech
Nov 21 '18 at 14:53
@LarsTech See my answer, I found a way to change the owner "easily" to handle this. Yep, it should be annoying, cause people should update. (especially those who never shutdown their pc and/or application)
– dognose
Nov 21 '18 at 16:55
add a comment |
Despite the name of the property, TopMost is actually your enemy here. To make a "floating form" stay above a main form, without obscuring other applications when they get focus, try it this way:
FormX f = new FormX();
f.Show(this);
"this" in this example, is the main form instance. It means the form you created is now owned by the main form, and will make it float above it. You get the added benefit of, when minimizing the main form, the floating forms will disappear, too.
answered Nov 20 '18 at 23:15
LarsTechLarsTech
69.9k12105158
Thanks for your example. This will work, if the "target" is to keep the floating form just on top of the main-window. However, this approach would allow "other" forms of the application to overlay the floating form - and obviously I can't callf.Show(this)for more than one form.
– dognose
Nov 21 '18 at 11:19
@dognose What you really want my man is to switch to WPF where problems like are long forgotten.
– Michael Puckett II
Nov 21 '18 at 12:55
@dognose That's just a different issue. I would re-think this whole update-floating-form concept and just show a toast notification or something else. To be honest, annoying an end-user with the update form is just...annoying.
– LarsTech
Nov 21 '18 at 14:53
@LarsTech See my answer, I found a way to change the owner "easily" to handle this. Yep, it should be annoying, cause people should update. (especially those who never shutdown their pc and/or application)
– dognose
Nov 21 '18 at 16:55
add a comment |
Despite the name of the property, TopMost is actually your enemy here. To make a "floating form" stay above a main form, without obscuring other applications when they get focus, try it this way:
FormX f = new FormX();
f.Show(this);
"this" in this example, is the main form instance. It means the form you created is now owned by the main form, and will make it float above it. You get the added benefit of, when minimizing the main form, the floating forms will disappear, too.
answered Nov 20 '18 at 23:15
LarsTechLarsTech
69.9k12105158
Despite the name of the property, TopMost is actually your enemy here. To make a "floating form" stay above a main form, without obscuring other applications when they get focus, try it this way:
FormX f = new FormX();
f.Show(this);
"this" in this example, is the main form instance. It means the form you created is now owned by the main form, and will make it float above it. You get the added benefit of, when minimizing the main form, the floating forms will disappear, too.
answered Nov 20 '18 at 23:15
LarsTechLarsTech
69.9k12105158
answered Nov 20 '18 at 23:15
LarsTechLarsTech
69.9k12105158
answered Nov 20 '18 at 23:15
LarsTechLarsTech
69.9k12105158
answered Nov 20 '18 at 23:15
LarsTechLarsTech
69.9k12105158
69.9k12105158
Thanks for your example. This will work, if the "target" is to keep the floating form just on top of the main-window. However, this approach would allow "other" forms of the application to overlay the floating form - and obviously I can't callf.Show(this)for more than one form.
– dognose
Nov 21 '18 at 11:19
@dognose What you really want my man is to switch to WPF where problems like are long forgotten.
– Michael Puckett II
Nov 21 '18 at 12:55
@dognose That's just a different issue. I would re-think this whole update-floating-form concept and just show a toast notification or something else. To be honest, annoying an end-user with the update form is just...annoying.
– LarsTech
Nov 21 '18 at 14:53
@LarsTech See my answer, I found a way to change the owner "easily" to handle this. Yep, it should be annoying, cause people should update. (especially those who never shutdown their pc and/or application)
– dognose
Nov 21 '18 at 16:55
add a comment |
Thanks for your example. This will work, if the "target" is to keep the floating form just on top of the main-window. However, this approach would allow "other" forms of the application to overlay the floating form - and obviously I can't callf.Show(this)for more than one form.
– dognose
Nov 21 '18 at 11:19
@dognose What you really want my man is to switch to WPF where problems like are long forgotten.
– Michael Puckett II
Nov 21 '18 at 12:55
@dognose That's just a different issue. I would re-think this whole update-floating-form concept and just show a toast notification or something else. To be honest, annoying an end-user with the update form is just...annoying.
– LarsTech
Nov 21 '18 at 14:53
@LarsTech See my answer, I found a way to change the owner "easily" to handle this. Yep, it should be annoying, cause people should update. (especially those who never shutdown their pc and/or application)
– dognose
Nov 21 '18 at 16:55
Thanks for your example. This will work, if the "target" is to keep the floating form just on top of the main-window. However, this approach would allow "other" forms of the application to overlay the floating form - and obviously I can't call
f.Show(this) for more than one form.– dognose
Nov 21 '18 at 11:19
Thanks for your example. This will work, if the "target" is to keep the floating form just on top of the main-window. However, this approach would allow "other" forms of the application to overlay the floating form - and obviously I can't call
f.Show(this) for more than one form.– dognose
Nov 21 '18 at 11:19
@dognose What you really want my man is to switch to WPF where problems like are long forgotten.
– Michael Puckett II
Nov 21 '18 at 12:55
@dognose What you really want my man is to switch to WPF where problems like are long forgotten.
– Michael Puckett II
Nov 21 '18 at 12:55
@dognose That's just a different issue. I would re-think this whole update-floating-form concept and just show a toast notification or something else. To be honest, annoying an end-user with the update form is just...annoying.
– LarsTech
Nov 21 '18 at 14:53
@dognose That's just a different issue. I would re-think this whole update-floating-form concept and just show a toast notification or something else. To be honest, annoying an end-user with the update form is just...annoying.
– LarsTech
Nov 21 '18 at 14:53
@LarsTech See my answer, I found a way to change the owner "easily" to handle this. Yep, it should be annoying, cause people should update. (especially those who never shutdown their pc and/or application)
– dognose
Nov 21 '18 at 16:55
@LarsTech See my answer, I found a way to change the owner "easily" to handle this. Yep, it should be annoying, cause people should update. (especially those who never shutdown their pc and/or application)
– dognose
Nov 21 '18 at 16:55
add a comment |
I figured out a way to solve it.
Setting the owner of the UpdateHint is required, but in order to keep it on top of every application window, one has to change the owner, if a new Window is either shown, or activated.
Within our application, every Form is inheriting InterceptorForm, so all I had to do was to modify the InterceptorForm accordingly:
Change the Owner to this, except if there is no dialog, or this is the dialog itself:
public class InterceptorForm : Form
{
protected override void OnLoad(EventArgs e)
{
...
if (this.GetType() != typeof(UpdateHint) && MainWindow.updateHint != null)
{
Log.t("Setting owner on update hint during onload: " + this.GetType());
MainWindow.updateHint.Owner = this;
}
base.OnLoad(e);
}
and
protected override void OnActivated(EventArgs e)
{
if (this.GetType() != typeof(UpdateHint) && MainWindow.updateHint != null)
{
Log.t("Setting owner on update hint: " + this.GetType());
MainWindow.updateHint.Owner = this;
}
base.OnActivated(e);
}
}
The UpdateHint now stays on top of every window belonging to our application, but can be overlayed by any other application.
answered Nov 21 '18 at 16:53
dognosedognose
15.8k64690
add a comment |
I figured out a way to solve it.
Setting the owner of the UpdateHint is required, but in order to keep it on top of every application window, one has to change the owner, if a new Window is either shown, or activated.
Within our application, every Form is inheriting InterceptorForm, so all I had to do was to modify the InterceptorForm accordingly:
Change the Owner to this, except if there is no dialog, or this is the dialog itself:
public class InterceptorForm : Form
{
protected override void OnLoad(EventArgs e)
{
...
if (this.GetType() != typeof(UpdateHint) && MainWindow.updateHint != null)
{
Log.t("Setting owner on update hint during onload: " + this.GetType());
MainWindow.updateHint.Owner = this;
}
base.OnLoad(e);
}
and
protected override void OnActivated(EventArgs e)
{
if (this.GetType() != typeof(UpdateHint) && MainWindow.updateHint != null)
{
Log.t("Setting owner on update hint: " + this.GetType());
MainWindow.updateHint.Owner = this;
}
base.OnActivated(e);
}
}
The UpdateHint now stays on top of every window belonging to our application, but can be overlayed by any other application.
answered Nov 21 '18 at 16:53
dognosedognose
15.8k64690
add a comment |
I figured out a way to solve it.
Setting the owner of the UpdateHint is required, but in order to keep it on top of every application window, one has to change the owner, if a new Window is either shown, or activated.
Within our application, every Form is inheriting InterceptorForm, so all I had to do was to modify the InterceptorForm accordingly:
Change the Owner to this, except if there is no dialog, or this is the dialog itself:
public class InterceptorForm : Form
{
protected override void OnLoad(EventArgs e)
{
...
if (this.GetType() != typeof(UpdateHint) && MainWindow.updateHint != null)
{
Log.t("Setting owner on update hint during onload: " + this.GetType());
MainWindow.updateHint.Owner = this;
}
base.OnLoad(e);
}
and
protected override void OnActivated(EventArgs e)
{
if (this.GetType() != typeof(UpdateHint) && MainWindow.updateHint != null)
{
Log.t("Setting owner on update hint: " + this.GetType());
MainWindow.updateHint.Owner = this;
}
base.OnActivated(e);
}
}
The UpdateHint now stays on top of every window belonging to our application, but can be overlayed by any other application.
answered Nov 21 '18 at 16:53
dognosedognose
15.8k64690
I figured out a way to solve it.
Setting the owner of the UpdateHint is required, but in order to keep it on top of every application window, one has to change the owner, if a new Window is either shown, or activated.
Within our application, every Form is inheriting InterceptorForm, so all I had to do was to modify the InterceptorForm accordingly:
Change the Owner to this, except if there is no dialog, or this is the dialog itself:
public class InterceptorForm : Form
{
protected override void OnLoad(EventArgs e)
{
...
if (this.GetType() != typeof(UpdateHint) && MainWindow.updateHint != null)
{
Log.t("Setting owner on update hint during onload: " + this.GetType());
MainWindow.updateHint.Owner = this;
}
base.OnLoad(e);
}
and
protected override void OnActivated(EventArgs e)
{
if (this.GetType() != typeof(UpdateHint) && MainWindow.updateHint != null)
{
Log.t("Setting owner on update hint: " + this.GetType());
MainWindow.updateHint.Owner = this;
}
base.OnActivated(e);
}
}
The UpdateHint now stays on top of every window belonging to our application, but can be overlayed by any other application.
answered Nov 21 '18 at 16:53
dognosedognose
15.8k64690
answered Nov 21 '18 at 16:53
dognosedognose
15.8k64690
answered Nov 21 '18 at 16:53
dognosedognose
15.8k64690
answered Nov 21 '18 at 16:53
dognosedognose
15.8k64690
15.8k64690
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%2f53401866%2fc-sharp-topmost-true-restrict-to-application%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
Make sure the main form is the owner of the floating form.
– LarsTech
Nov 20 '18 at 21:34
Windows 10 has a Notification System for just this kind of thing. Your current itteration overlaps with this article: blogs.msdn.microsoft.com/oldnewthing/20110310-00/?p=11253
– Christopher
Nov 20 '18 at 21:38
1
@Christopher That article is not what the OP issue is.
– LarsTech
Nov 20 '18 at 21:39
@LarsTech explicit setting the owner has no impact at all...
– dognose
Nov 20 '18 at 21:42
1
That's a special property you have to custom write. lol
– Michael Puckett II
Nov 20 '18 at 22:20