So, there is nothing left to fix in this bug, and Mono behaves the same as .NET. Is that right? By the way, I think that on bugzilla.novell, anyone can close bugs and all, unlike on xamarin.bugzilla.
Robert Wilkens wrote > > I was just looking at this old 'bug' from the Novell's bugzilla: > > https://bugzilla.novell.com/show_bug.cgi?id=321541 > > Some stuff was fixed for that bug some 6 years ago, but it hasn't been > closed yet because they didn't understand why the events were being > delivered to both threads. > > The answer is because both threads in the sample code are processing the > same event queue by virtue of calling Application.Run() which is the > event processor, and there is only one event queue per application. I > read this somewhere on msdn today when i was googling information > related to the problem. Only one thread should be processing the event > queue. > > Does anyone here have the authority to close old Novell bugs such as > this one? It would make it easier to get an idea of what is actually > still broken versus what needs to be fixed. > > I am only writing here because i saw very few people were being cc'd > when i made a comment on it stating this much. > _______________________________________________ > Mono-devel-list mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/mono-devel-list > -- View this message in context: http://mono.1490590.n4.nabble.com/Request-for-Novell-bug-maintainer-tp4649597p4649598.html Sent from the Mono - Dev mailing list archive at Nabble.com. _______________________________________________ Mono-devel-list mailing list [email protected] http://lists.ximian.com/mailman/listinfo/mono-devel-list
