Trace is here, http://oscill8.biol.vt.edu/_files/trace.txt.bz2. (I tried sending it to the list, but it bounced... it's on 200K zipped).
I ran with this command line:
mono --trace=N:Oscill8.Gui,T:System.Drawing.Size,T:System.Drawing.Rectangle,T:System.Windows.Forms.Control oscill8.exe
Grep for -103... this brings you to the erroneous .Height.
Thanks,
Emery
This looks like an issue with scrollbar/trackbar actually (at least the message matches exceptions they throw). Can you post the stack trace?
Thanks,
Jonathan
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Emery Conrad
Sent: Thursday, February 23, 2006 10:09 AM
To: Jackson Harper
Cc: [EMAIL PROTECTED]
Subject: Re: [Mono-winforms-list] 1.1.9.2 vs 1.1.13.2
Jackson,
Curious... I'm not loading any images specifically (I've disabled the one splash screen image I have). The only other graphics that could be loaded would be the application icon I suppose, but the error seems to be triggered by the painting of a control inside of a user defined control. Is there a good way to debug this... I haven't yet figured out a decent way to thoroughly debug my mono apps yet... how do you guys debug these things?
Emery
On 2/22/06, Jackson Harper <[EMAIL PROTECTED]> wrote:
On Wed, 2006-02-22 at 12:07 -0500, Emery Conrad wrote:
> Hello, new to the list. Nice to meet you all...
>
> Question:
>
> I have a VS.NET app that I'm porting to Linux. In order to get things
> to work, I had to convert .resx to .resources and then do a mono
> build. In version 1.1.9.2, my app at least starts (all the features
> don't work, but I was working on it). Upgrading Mono to 1.1.13.2,
> there is an exception when it's laying out one of the user defined
> controls saying:
>
> "Value '-104' must be greater than or equal to 0."
>
> which you can see back in the trace is a result of one of the controls
> calling .Height:
>
> "System.Drawing.Rectangle:get_Height ()result=-104."
Sounds like something in the image loading code. Do you mind filing a
bug report and attaching the image that's failing?
Jackson
> Does anyone know what's changed from 1.1.9.2 to 1.1.13.2 that might
> cause this? FYI, if I use the old .exe (built for 1.1.9.2) and run it
> with the new 1.1.13.2 runtime, this still happens (as opposed to
> rebuilding everything and running with the 1.1.13.2 setup).
>
> FYI, I'm willing to join the team and help implement new features, fix
> old features as time permits... I plan on investing a great deal of
> energy into making sure that I can continue to develop .NET/Mono apps
> on both linux and MacOSX (in addition to windows), so I don't mind
> investing the time.
>
> Thanks,
>
> Emery
>
> _______________________________________________
> Mono-winforms-list maillist - [email protected]
> http://lists.ximian.com/mailman/listinfo/mono-winforms-list
--
Emery Conrad
--
Emery Conrad
_______________________________________________ Mono-winforms-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-winforms-list
