[Mono-dev] Fwd: Re: Patches for mono-winforms

Rob Wilkens robwilkens at gmail.com
Tue Jul 31 21:38:41 UTC 2012


Wish I kept that off list.

Sorry - I am bipolar and have mood swings.  I must have stopped myself
from sending something similar about 3-5 times before.

Please ignore any 'woe is me' messages - I am not quitting.  I finally
got home, and my linux machine is working fine with my home network.

Like i said, i've learned a lot doing this.

I really have to look at the fix i submitted on the list more
carefully.  I am not home and should have time, but we're still
unpacking and stuff, may take a few days to settle down.

If no one applied the fix i submitted on the list, that is ok, it may be
no better than the original problem anyway.  I need to think more
carefully about the fix.

There is an easier way to solve this problem than i idd it originally. 
I just remember when I was looking at the code originally there was a
mixture of recursive areas and non-recursive areas, so i cannot
guarantee that i'll be at the same level of recursion when i would want
to 'back track', but i know i can come up with a better solution than i
did for 2663 which doesn't add too much slowness as the current solution
does.  The benefit of the current solution is i got it to 'work' where
before it failed. 

-Rob

On 07/29/2012 04:55 PM, Rob Wilkens wrote:
>
> Oops accidentally replied off list
>
> ---------- Forwarded message ----------
> From: "Rob Wilkens" <robwilkens at gmail.com <mailto:robwilkens at gmail.com>>
> Date: Jul 29, 2012 4:22 PM
> Subject: Re: [Mono-dev] Patches for mono-winforms
> To: "Steven Boswell II" <ulatekh at yahoo.com <mailto:ulatekh at yahoo.com>>
>
> On a bright note, I think my phase of programming for fun is over for
> now.  It's become clear to me that I am not very good at it.  Perhaps
> in the future if I read/learn/practice more ill give it an honest
> effort again.  I am a decent hacker, but at this time an out of
> practice engineer.  Hope I get to give it another go in the future.
>
> On Jul 29, 2012 3:57 PM, "Rob Wilkens" <robwilkens at gmail.com
> <mailto:robwilkens at gmail.com>> wrote:
>
>     The one idle per thread test was first created by me and committed
>     by Miguel, but I thought he backed out the whole patch... It was
>     part of a bigger patch and was tested on three platforms as a whole.
>
>     On Jul 29, 2012 11:44 AM, "Steven Boswell II" <ulatekh at yahoo.com
>     <mailto:ulatekh at yahoo.com>> wrote:
>
>         https://github.com/mono/mono/commit/38bdbad5071487a11f4330077c383375dce39840
>
>         This change introduced a OneIdlePerThread unit test that has
>         never worked for me.  All I get is the following exception:
>
>         System.InvalidOperationException : Cannot call Invoke or
>         BeginInvoke on a control until the window handle is created
>
>         Patch #18 fixes that by creating a Form type that calls
>         CreateHandle() in its constructor.  But now the unit test
>         hangs hard in Mono!
>
>         I created a project with the unit-test, and when run in Mono,
>         it hangs hard; selecting "Run -> Pause" in MonoDevelop hangs
>         MonoDevelop, and the debugged process chews up 100% of the CPU
>         time
>
>         I ran the project in .NET, and instead of a hang, I get this
>         exception:
>
>         System.InvalidOperationException: Cross-threaded operation not
>         valid: Control '' accessed from a thread other than the thread
>         it was created on.
>
>         Patch #18a fixes that by moving the creation of form2 into the
>         right thread.  Now the unit test passes.
>
>         So patch #18a can be checked in, but note that patch #18
>         demonstrates that Mono hangs in a situation where .NET throws
>         an exception.
>
>         Steven Boswell
>
>
>         _______________________________________________
>         Mono-devel-list mailing list
>         Mono-devel-list at lists.ximian.com
>         <mailto:Mono-devel-list at lists.ximian.com>
>         http://lists.ximian.com/mailman/listinfo/mono-devel-list
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20120731/246339d1/attachment.html>


More information about the Mono-devel-list mailing list