Opened 9 years ago

Closed 9 years ago

#2111 closed defect (fixed)

maestro crash on linux (System.Windows.Forms.SplitContainer doesn't implement interface System.ComponentModel.ISupportInitialize)

Reported by: gabrimonfa Owned by: jng
Priority: low Milestone:
Component: Maestro Version:
Severity: trivial Keywords:
Cc: External ID:


Maestro compiled from svn updated to first days of september 2012

Mono on ubuntu linux from badgerports

Crash on creating a new vector layer definition.

System.Windows.Forms.SplitContainer? doesn't implement interface System.ComponentModel?.ISupportInitialize

Probably a mono bug or not-implemented.

Stack trace attached

Attachments (1)

stack_trace (9.1 KB) - added by gabrimonfa 9 years ago.
Stack trace of crash

Download all attachments as: .zip

Change History (6)

Changed 9 years ago by gabrimonfa

Attachment: stack_trace added

Stack trace of crash

comment:1 Changed 9 years ago by jng

Is Mono running it as though it were a .net 2.0/3.5 application?

SplitContainer? implements ISupportInitialize as of .net 4.0

comment:2 Changed 9 years ago by gabrimonfa

It appears that this interface has not been implemented in 2.10 branch.

The unfortunate thing is that meastro is aborted. This prevents to create new vector layer definitions (however is always possible to duplicate and edit an existing one).

comment:3 Changed 9 years ago by jng

That is just stupid! Visual Studio will be inserting this piece of problematic code on any form/control I open that uses a SplitContainer?, meaning I'll not only have to battle with Mono, but Visual Studio's form designer. Argh!

Any form/control with a SplitContainer? will have this problem

comment:4 Changed 9 years ago by gabrimonfa

Tested on mono trunk - version 2.11.5 (master/1be50d0 mer 12 set 2012, 15.42.47, CEST)

The interface has indeed been implemented, thus maestro does not crash anymore creating a new feature source.

comment:5 Changed 9 years ago by jng

Resolution: fixed
Status: newclosed

All offending lines removed r7010

Note: See TracTickets for help on using tickets.