-
Notifications
You must be signed in to change notification settings - Fork 57
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
ShowAsPopupAsync broken in Avalonia 11.1.0 #185
Comments
fixeed here #182 |
Is this in a released version? I'm still having the same issues using MessageBox 3.1.6 with both Avalonia 11.1.0 and 11.1.1. |
I can confirm it still happens on browser with Avalonia 11.1.1 and MessageBox 3.1.6. |
This issue also occurs on my Android app (both emulator and hardware) using the very latest Avalonia 11.1.2 and MessageBox 3.1.6. ShowWindowDialogAsync works as expected on the Windows/Linux/MacOS app versions but ShowAsPopupAsync displays a transparent non-modal popup in both light and dark modes. Hopefully nobody minds if I attach a light mode image. |
usercontrol background=white |
@Upanc Sorry please explain "usercontrol background=white" A workaround is to manipulate the UserControl via styles. But that's not pretty!
(UserControl of MsBoxStandardView is the only one with padding 15 ;-) |
here MsBoxCustomView.axaml,It's useful to me |
I haven't found any examples or Wiki of how to use Custom. What does your solution look like in the code? |
clone this project and build |
I got ShowWindowDialogAsync to do the job, although I don't know how to hide the title bar buttons:
|
Hi, after upgrading to Avalonia 11.1.0 the ShowAsPopupAsync() method is no longer working as expected. When displayed it no longer grays out the screen behind it nor does it prevent a user from interacting with that screen. It also sometimes displays with the text behind it overlayed on top of the popup.
None of these were issues with 11.0.11. It's only after the latest upgrade. ShowWindowDialogAsync is working as expected, so I am using that instead for now.
The text was updated successfully, but these errors were encountered: