MWF Status report

Hi all,

As promised, attached a OpenOffice Calc spreadsheet with details about
MWF bug status, this week I also implemented a comparison with last
week.

I also would like to propose one "bug hunt week" on winforms, so
instead of implement new functionalities we can use this week to fix
bugs and try to reduce our queue. Maybe start on easy (fast) bugs.

We have a lot of bugs assigned to people that is working now on
Moonlight or assigned to people that is not current working on bug. So
will be nice if we assign this bugs to "mono-bugs <at> ximian.com" (I
already done it with my owns).

Theres also some bugs marked as "NEEDINFO" if you are creator of one
of this bugs please give us some feedback, maybe it is already
working.

Thanks,
Everaldo.

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

MWF Status report

Hi all,

As promised, attached a OpenOffice Calc spreadsheet with details about
MWF bug status, this week I also implemented a comparison with last
week.

I also would like to propose one "bug hunt week" on winforms, so
instead of implement new functionalities we can use this week to fix
bugs and try to reduce our queue. Maybe start on easy (fast) bugs.

We have a lot of bugs assigned to people that is working now on
Moonlight or assigned to people that is not current working on bug. So
will be nice if we assign this bugs to "mono-bugs <at> ximian.com" (I
already done it with my owns).

Theres also some bugs marked as "NEEDINFO" if you are creator of one
of this bugs please give us some feedback, maybe it is already
working.

Thanks,
Everaldo.
_______________________________________________
Mono-winforms-list maillist  -  Mono-winforms-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-winforms-list

Re: MWF Status report

Attachment.

On 9/4/07, Everaldo Canuto <everaldo.canuto <at> gmail.com> wrote:
> Hi all,
>
> As promised, attached a OpenOffice Calc spreadsheet with details about
> MWF bug status, this week I also implemented a comparison with last
> week.
>
> I also would like to propose one "bug hunt week" on winforms, so
> instead of implement new functionalities we can use this week to fix
> bugs and try to reduce our queue. Maybe start on easy (fast) bugs.
>
> We have a lot of bugs assigned to people that is working now on
> Moonlight or assigned to people that is not current working on bug. So
> will be nice if we assign this bugs to "mono-bugs <at> ximian.com" (I
> already done it with my owns).
>
> Theres also some bugs marked as "NEEDINFO" if you are creator of one
> of this bugs please give us some feedback, maybe it is already
> working.
>
>
> Thanks,
> Everaldo.
>

_______________________________________________

Re: [Mono-dev] MWF Status report

Hi,

I just add a flat version since Google docs don't show functions
properly. Next weeks I will make plain version and import on Google
docs.

You can see it here:

   http://spreadsheets0.google.com/ccc?key=pNj_nZBoo-7G0KVgtYrK-IA&hl=pt_BR

Everaldo.

On 9/4/07, olivier dufour <olivier.duff <at> gmail.com> wrote:
> Hi all,
>
> I have just put the document attachment.bin on google spreadsheet to allow
> people to read it easily.
> You can see it here :
>
>
> http://spreadsheets.google.com/ccc?key=pGyiJ8QsIX7CXwDRqEygnYQ&hl=fr
> bye,
> olivier dufour
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list <at> lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>

TreeView: Handling of Mouse-Events and two minor bugfixes

Hello all,

following Everaldos request I've tried to fix some of the smaller bugs
of the TreeView.

So far, I managed to fix 81779 and 81839 (both patches are in bugzilla
for review).

But while working on 81739 I've noticed that MouseEvents in TreeViews
are handled strangely because the appropriate OnMouseXXX methods are
only overridden by parts of the mouse event, the rest subscribes to his
own MouseXXX-Events instead.

Is there any reason why this has been implemented this way and would it
make sense to alter all the events to override the OnMouseXX methods
(for more performance and more readable code)? And btw is someone
already working at this bug so that I should leave it alone?

Kind Regards,
Valentin S.

_______________________________________________
Mono-winforms-list maillist  -  Mono-winforms-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-winforms-list

New to the list

Hi,

I'm new to the list (and to Mono).

I'm trying to run a rather large Win Forms MDI application with Mono 
1.2.5 and found some minor bugs that made Mono crash when running this app.

I have some (really minor) bugfixes and cosmetic changes to some 
controls and I was wondering if I should send them directly to the list.
Should I just attach a .patch or .diff file to a post?
Should I send a patch for multiple files or one individual patch for 
every file?
Should I send the change log as part of the post body or as a patch to 
the ChageLog file?

Thanks in advance.

Regards,
Ernesto

_______________________________________________
Mono-winforms-list maillist  -  Mono-winforms-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-winforms-list

Re: New to the list

Hello and welcome to Mono (and this list),

On Thu, 2007-09-06 at 16:48 -0300, Ernesto wrote:
> Hi,
> 
> I'm new to the list (and to Mono).
> 
> I'm trying to run a rather large Win Forms MDI application with Mono 
> 1.2.5 and found some minor bugs that made Mono crash when running this app.
> 
could you please check if your Bugs are new or are they already known
and filed in the bugzilla at http://bugzilla.ximian.com/
(If they are not in the bugzilla would you please file them in?)

> I have some (really minor) bugfixes and cosmetic changes to some 
> controls and I was wondering if I should send them directly to the list.
> Should I just attach a .patch or .diff file to a post?
> Should I send a patch for multiple files or one individual patch for 
> every file?
> Should I send the change log as part of the post body or as a patch to 
> the ChageLog file?
> 
It would be best if you attach your patches to the bug-entries in the
bugzilla, this way it's harder for your patches to get lost 

> Thanks in advance.
> 
> Regards,
> Ernesto
> 

Re: New to the list

Awesome, we love people who fix the bugs they find!

Generally a bug is opened in bugzilla and the patch is attached to it. 
This makes sure they don't get ignored on the list and are trackable. 
But if they're pretty minor, I can probably take them from the list and 
make sure they get committed.

Ideally, each .patch file will contain all the files for one 'bug'. 
That allows us to commit and test each change independently.

So maybe "bug one" patch file has changes to:
Form.cs
ChangeLog

and "bug two" patch file has changes to:
Control.cs
ThemeWin32Classic.cs
ChangeLog

Go ahead and patch the ChangeLog with your message saying what was 
changed and why (what it fixes) following the format of other messages.

If possible (and things like cosmetic changes aren't), it's also nice to 
provide NUnit tests that ensure the issue is fixed and never creeps back in.

Thanks for your help in tracking these down and providing fixes!
Jonathan

Ernesto wrote:
> Hi,

Re: New to the list

Jonathan Pobst wrote:
> Generally a bug is opened in bugzilla and the patch is attached to it. 
> This makes sure they don't get ignored on the list and are trackable. 
> But if they're pretty minor, I can probably take them from the list 
> and make sure they get committed.
>

Ok, here are two really minor (a one-liner and a two-liner). These two 
missing checks where causing Mono to crash on my app.

For other bigger fixes I'm filing bug reports and attaching patches.

Sorry I didn't patch ChangeLog. I didn't want to submit two patches for 
the same version of the same file.
So below is the change log, if needed.

Thanks for your help.
Ernesto.

---------

2007-09-06  Ernesto Carrea  <equistango <at> gmail.com>

    * ListView.cs: ListViewItemCollection must call
    AdjustItemsPositionArray when the collection changes.

2007-09-06  Ernesto Carrea  <equistango <at> gmail.com>

    * ScrollBar.cs: UpdatePos value was checked to be not less than minimum,
    but wasn't checked not to be more than maximum.

Re: New to the list

Hey Ernesto!

The changes look harmless, but I have a feeling they are simply hiding a 
bigger problem, ie: what is trying to set a scroll position bigger than 
the maximum and why.  The ListView maintainer (calberto) thinks the same 
about the ListView one.  Do you have a test case or code snippet for 
each of them that reproduces the crash so we can dig a bit a deeper?

Thanks!
Jonathan

Ernesto wrote:
> Jonathan Pobst wrote:
>> Generally a bug is opened in bugzilla and the patch is attached to it. 
>> This makes sure they don't get ignored on the list and are trackable. 
>> But if they're pretty minor, I can probably take them from the list 
>> and make sure they get committed.
>>
> 
> Ok, here are two really minor (a one-liner and a two-liner). These two 
> missing checks where causing Mono to crash on my app.
> 
> For other bigger fixes I'm filing bug reports and attaching patches.
> 
> Sorry I didn't patch ChangeLog. I didn't want to submit two patches for 
> the same version of the same file.
> So below is the change log, if needed.
> 
> Thanks for your help.
> Ernesto.