[Mono-dev] Feedback for Windows Forms in 1.1.15

Andreas Nahr ClassDevelopment at A-SoftTech.com
Wed Apr 19 12:52:27 EDT 2006

Hi Peter,

if I find some time I will log the bugs. The sample apps used are not 
currently available, but I think the problems described are easily 
reproduceable even from the screenshots and are mostly not bugs but just 
missing or incorrectly implemented features.

I also found out what the problems with most of the bigger apps is: They all 
use an ImageList and throw exceptions. I'll add the CallStack:

Unhandled Exception: System.Reflection.TargetInvocationException: Exception 
has been thrown by the target of an invocation. ---> 
System.ArgumentException: Invalid Parameter. A null reference or invalid 
value was found.
in <0x00084> System.Drawing.GDIPlus:CheckStatus (Status status)
in <0x001e0> System.Drawing.Image:InitFromStream (System.IO.Stream stream)
in <0x0001c> System.Drawing.Bitmap:.ctor (System.IO.Stream stream, Boolean 
in <0x0000f> System.Drawing.Bitmap:.ctor (System.IO.Stream stream)
in (wrapper remoting-invoke-with-check) System.Drawing.Bitmap:.ctor 
in <0x004f9> System.Windows.Forms.ImageListStreamer:.ctor 
(System.Runtime.Serialization.SerializationInfo info, StreamingContext 
in <0x00000> <unknown method>
in (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke 
in <0x0008d> System.Reflection.MonoCMethod:Invoke (System.Object obj, 
BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] 
parameters, System.Globalization.CultureInfo culture)--- End of inner 
exception stack trace ---
in <0x0010e> System.Reflection.MonoCMethod:Invoke (System.Object obj, 
BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] 
parameters, System.Globalization.CultureInfo culture)
in <0x0001a> System.Reflection.MethodBase:Invoke (System.Object obj, 
System.Object[] parameters)
in <0x001db> System.Runtime.Serialization.ObjectRecord:LoadData 
(System.Runtime.Serialization.ObjectManager manager, ISurrogateSelector 
selector, StreamingContext context)
in <0x00110> System.Runtime.Serialization.ObjectManager:DoFixups ()
in <0x00042> 
(System.IO.BinaryReader reader)
in <0x000a3> 
(System.IO.BinaryReader reader, Boolean readHeaders, System.Object result, 
System.Runtime.Remoting.Messaging.Header[] headers)
in <0x0011f> 
(System.IO.Stream serializationStream, 
System.Runtime.Remoting.Messaging.HeaderHandler handler)
in <0x0000f> 
(System.IO.Stream serializationStream)
in <0x00032> System.Resources.ResourceReader:ReadNonPredefinedValue 
(System.Type exp_type)
in <0x0031e> System.Resources.ResourceReader:ReadValueVer1 (System.Type 
in <0x00163> System.Resources.ResourceReader:ResourceValue (Int32 index)
in <0x00028> System.Resources.ResourceReader+ResourceEnumerator:get_Value ()
in <0x0007e> System.Resources.ResourceSet:ReadResources ()
in <0x00049> System.Resources.ResourceSet:GetObject (System.String name, 
Boolean ignoreCase)
in <0x0007a> System.Resources.ResourceManager:GetObject (System.String name, 
System.Globalization.CultureInfo culture)
in <0x00010> System.Resources.ResourceManager:GetObject (System.String name)
in <0x00b77> FileCenter.FileCenter:InitializeComponent ()
in (wrapper remoting-invoke-with-check) 
FileCenter.FileCenter:InitializeComponent ()
in <0x00061> FileCenter.FileCenter:.ctor ()
in (wrapper remoting-invoke-with-check) FileCenter.FileCenter:.ctor ()
in <0x00018> FileCenter.FileCenter:Main ()

Also to make things a little bit easier I wrote a small application that 
lets you start Mono WinForms Apps without using the Commandline ;)
Currently the tool only works on MS.Net (seems as if Mono Winforms does not 
support Drag-And-Drop yet).


> Thanks for the testing. I'd be great if you could log bugs for these, that
> way we don't loose track of them. Also, if you could provide links where 
> to
> get the sample apps you used, that would help in reproducing the problems.
> What were the problems with the real-world apps?
> Cheers,
> Peter
> -----Original Message-----
> From: "Andreas Nahr" <ClassDevelopment at A-SoftTech.com>
> To: <mono-devel-list at lists.ximian.com>
> Date: 18 April, 2006 13:04
> Subject: [Mono-dev] Feedback for Windows Forms in 1.1.15
>>I tested some of my Winforms Apps on Mono 1.1.15 running on WinXP x64.
>>Most of the real-world apps didn't start, but some small sample ones did.
>>Here are some notes about Problems with the ones that did:
>>Wrong clipping region/ Window size calculation? See screenshot
>>* Dividing line at wrong position -> should be at 50% of width of control.
>>* Readonly Elements not grayed out -> Gray out
>>* Readonly Elements show designers (if designers are used -> crash) ->
>>display designers for readonly elements
>>* Category Names not determined correctly if inherited -> Use inherited
>>CategoryName Attributes
>>* Description default is currently: "Title<crlf>The long important
>>Description" -> should be ""
>>* Default: All Entries expanded -> Should be: All entries NOT expanded
>>* Setting values does not work
>>* ToolbarVisible/HelpVisible ignored sometimes -> See screenshot
>>Crashes with any selection
>>Happy hacking!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MonoLaunch.exe
Type: application/x-msdownload
Size: 69632 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20060419/1658d164/attachment.bin 

More information about the Mono-devel-list mailing list