[Mono-dev] .net winforms and windows
stifu at free.fr
Wed Jun 13 20:35:55 UTC 2012
Just to make sure, you mean you get these issues with .NET, with Mono, or
Anyway, to clear things up, as far as GDI+ and WinForms are concerned, the
goal is to be as compatible with them as possible, not to make something
better or more powerful. Ideally, the same things should work or fail on
each framework. We don't want things that work only on Mono and not with
.NET, especially for compatibility stacks like these.
Rob Wilkens wrote
> I wanted to think about what to work on next, and i wonder if anyone has
> an opinion on this:
> In my testing of .net winforms on windows i received a lot of gdi+
> object busy errors when i was testing a multithreaded app, regardless of
> what thread the form was 'created' in (what thread the form was shown in
> may have been a factor). This only happened on Win32, and caused
> crashes in the apps when it occurred.
> If there really is an issue with gdi+ objects being busy because they
> are being accessed from both threads, then perhaps (and i haven't looked
> at the code yet) -- well, perhaps the calls to gdi+ should be made
> thread safe or at least thread "safer". i.e. Something as simple as
> creating a gdi+ lock or something similar, and before anything tries to
> access gdi+ acquire the lock (at least on win32, which is the only place
> this seemed to be an issue). IT should be better to make an app wait
> for a thread to finish using gdi+ (wait for the lock) then for otherwise
> the application to crash altogether in a WmPaint command.
> i know winforms, unofficially offically, is dead, but this seems like a
> simple enough thing to try to correct.
> Mono-devel-list mailing list
> Mono-devel-list at .ximian
View this message in context: http://mono.1490590.n4.nabble.com/net-winforms-and-windows-tp4649922p4649924.html
Sent from the Mono - Dev mailing list archive at Nabble.com.
More information about the Mono-devel-list