Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Nothing in Xamarin Studio sets the static `MessageDialog.RootWindow` variable. We have two options:
* Kill that variable completely and expose it in all the methods in Xwt.MessageDialog.* so it can be passed in properly.
* Set it in Xamarin Studio on startup and pray that no-one ever unsets it.
I'd go for the former if at all possible because we already have code which (re)sets that static variable, and i'm sure it's just going to be really broken if we try to keep using it.
Bug #39689 is the same as this, but was reported against an app we don't ship.
I ported the only user I could find of this variable to do things The Right Way
NOTE: I did not grep the sourcecode for all users of `Xwt.MessageDialog` so I don't know how many other places are going to display dialogs on the wrong screen.
Similar code to the Xwt.MessageDialog is found in MonoDevelop.Ide.MessageService which does have its RootWindow variable set at startup
The issues described in bug #39689 will affect XS and VS until we have a workaround
Fixed in version 188.8.131.5245 (master)
Author: Vsevolod Kukol
Commit: 9a243d296dedaeb397dd7c383a78756c13f54d72 (mono/monodevelop)