This question is locked. New answers and comments are not allowed.
I have a RadMessageBox that when it fires the closedHandler it navigates back to a page. But that page's background is now transparent. Is the message box code manipulating containers or anything that it could be grabbing the wrong container and setting it as transparent? Here's an example
Anything look odd here (e.g. should the closedHandler run on the UI thread automatically?)
UPDATE: Confirmed that there is code running after the closed handler that is looking for and changing my transparency to about 80% from 100%. Replace code with MessageBox and it doesn't happen.
ANOTHER UPDATE: I've confirmed the bug with a reproducable case. It seems that if I have a container with a background of "{StaticResource PhoneBackgroundBrush}" it makes that 80%ish in my case (mixed in with navigation it seems). My guess is that you're looking for the brush as an indication of an ancestor and finding my overlay. If I make the background "Black" it works but that's not an acceptable fix. I can share a reproducible case (can't attach it here). Feel free to contact me directly.
RadMessageBox.Show(
"Are you sure"
,
MessageBoxButtons.YesNo,
"Are you sure you wish to delete this order?"
,
vibrate:
false
,
closedHandler: a =>
{
if
(a.Result == DialogResult.OK)
{
// Do Some Work Then...
App.Current.RootFrame.GoBack();
}
});
Anything look odd here (e.g. should the closedHandler run on the UI thread automatically?)
UPDATE: Confirmed that there is code running after the closed handler that is looking for and changing my transparency to about 80% from 100%. Replace code with MessageBox and it doesn't happen.
ANOTHER UPDATE: I've confirmed the bug with a reproducable case. It seems that if I have a container with a background of "{StaticResource PhoneBackgroundBrush}" it makes that 80%ish in my case (mixed in with navigation it seems). My guess is that you're looking for the brush as an indication of an ancestor and finding my overlay. If I make the background "Black" it works but that's not an acceptable fix. I can share a reproducible case (can't attach it here). Feel free to contact me directly.