Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Window going behind other windows on program start #1251

Closed
Tide opened this issue Apr 2, 2014 · 4 comments
Closed

Window going behind other windows on program start #1251

Tide opened this issue Apr 2, 2014 · 4 comments
Assignees
Labels
Milestone

Comments

@Tide
Copy link
Contributor

Tide commented Apr 2, 2014

I started noticing that when I start my application that the main window would go behind other windows on program startup some times. I thought at first it may just be my application as I had added splash screen to it around that same time.

I believe this started happening around 3-19-2014 (Not sure exactly the day). Well today I was playing with adding a new control to M.A.M. and using the demo to test it. The same bug appeared on occasion.

If you have other windows open and start the application it will start then quickly go behind other windows. The weird thing is it does not happen all the time.

I experience this most while debugging in Visual Studio. I rarely run my application enough for it to happen in application use. However, I debug it often in the course of working on the application and so I notice it more often while debugging. Just to be clear though it happens when I run my application on its own as well.

One thing I have noticed when it does happen and I am debugging I can change the value of a property from lets say False to True and debug again and it will occur. If I continue to repeat this process and change the bool value in xaml and debug ti will continue to happen each time. If I leave the bool the same and debug again the program will act normal. The hard part is getting the bug to happen in the first place. If it ever happens and you do as I just described you can get ti to happen every time.

The next thing you may think (I did) is well what does that have to do with when you run it on its own outside the Visual Studio debugger. My answer is I have no idea.

I feel bad even posting this but it has happened enough that I know something is up.

I can't give you any more information as like I said you do not know when it is going to happen.

I just wanted to put this up so if others are experiencing the same thing they will not think they are crazy and maybe can figure out what makes it happen.

@flagbug
Copy link
Member

flagbug commented Apr 2, 2014

I think I'm seeing this too. More specifically, I have an issue with the TopMost property in combination with IgnoreTaskBarOnMaximize="True", where with the latest alpha, TopMost doesn't have an effect anymore, this might be related.

@punker76 punker76 added the Bug label Apr 3, 2014
@punker76 punker76 self-assigned this Apr 3, 2014
@punker76
Copy link
Member

punker76 commented Apr 3, 2014

@flagbug i can repro your issue with 0.12.1 too, seems a TopMost with Maximize bug

  • set TopMost="True"
  • start mahapps demo
  • TopMost works
  • maximize window and back to normal
  • TopMost is gone
  • happens in alpha and 0.12.1

@punker76
Copy link
Member

punker76 commented Mar 1, 2015

@Tide fixed with 6b0a8fa

@punker76 punker76 closed this as completed Mar 1, 2015
@AndreasSchmid1
Copy link

This error appeared to me in v 1.2.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

4 participants