-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Description
I'm sorry in advance. I know it is never a fun issue when it happens randomly. I cannot narrow down what is causing this to happen. I will try my best to explain what's happening.
I have a flyout that has its IsOpen property bound to a boolean property in my ViewModel. My flyout let's the user enter in information to search my database. Once the user hits the button to search the database, I disable the controls in the flyout and show a MetroProgressBar inside of the flypout. Once all the data is pulled fine, I enable the controls, hide the progressbar, and then set the property bound to IsOpen to False. Most of the time, this will close the flyout and everything is fine.
I am using this app on what I would call sub-par tablets. They just don't have a lot of CPU power so they can be kinda laggy. Anyway, maybe 1 out of 1000 times I do this action, the flyout is still visible, but the internal software thinks it is closed. In other words, the overlay of the main window is no longer there and when I click the arrow to close the flyout, it does nothing. It is basically drawn on the window but all the internal code (your DLL and my app) thinks it is closed.
If I were to force the IsOpen property to true in this situation, it would do the flyout animation and do what it is supposed to, but once I close the "new" flyout, the "old" flyout is still shown. It seems like some sort of drawing issue but I have no clue on how to fix it.
Is anyone else running into this issue? Does anyone have a suggestion on how to resolve this?
When I get it to happen again, I will try to get some screenshots.