[Mono-dev] Patches for mono-winforms
https://github.com/mono/mono/commit/ecef298bcaf571a3d50e022318b20117f9d0388c introduced another bug that I found today. Enclosed is the fix. DataGridViewTextBoxCell was creating a single (as in static) instance of DataGridViewTextBoxEditingControl to do all editing. This fails if one edits two text-box cells, because ending the first edit calls Dispose() on the static instance, and the second attempt to edit throws an ObjectDisposedException. The solution is to use the control created by DataGridView, instead of maintaining a single static control. Incidentally, this also fixes a bug that I hadn't yet taken the time to track down. http://msdn.microsoft.com/en-us/library/system.windows.forms.datagridview.editingcontrolshowing.aspx mentions that DataGridView reuses the editing control whenever the cell type does not change between edits, and so any event-handlers placed on the control during the EditingControlShowing event should be removed. For this to work, control reuse could not be across multiple instances of DataGridView -- the event-handlers put onto editing-controls by other DataGridView instances would be unknowable. The previous static-instance code had this flaw; I noticed that event-handlers seemed to accumulate on text-box editing controls across data-grid-views when using Mono, even though I was following the recommended procedure, and that it wasn't happening under .NET and MS Windows. But no one would have noticed this until https://github.com/mono/mono/commit/f9bea537f1ac41753f2204b8528a6292bb547111 (about 2 months ago), when the EditingControlShowing event was posted for the first time. :-) Steven Boswell mwf-20-DataGridViewTextBoxCell-InitializeEditingControl.patch Description: Binary data ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] .Net versions ... compatibility history
From: mono-list-boun...@lists.ximian.com [mailto:mono-list- boun...@lists.ximian.com] On Behalf Of Stifu I don't know of documentation for this, but Mono 2.4 is old, and I wouldn't bother trying to support anything older. If we wish to develop distribute a server product using mono... It would be good to support rhel 5 6, as well as the various ubuntu LTS. Right now, ubuntu LTS all seem to have mono 2.10, which is good. But ... But centos 5 (epel5) has mono 1.2.4, and centos 6 (epel6) has mono 2.4.3. Maybe we'll just have to drop centos5 as a supported platform, but if you are a business distributing a product, telling your customers that you can only support the very latest OS, it makes it difficult for the customers to accept your product... Just ask any sysadmin who supports apple products. ;-) The day a new OS is released, the old OS is unsupported, so you as a company are forced to immediately drop what you're doing and test the new OS, as if the mac product release cycle is the only important thing in your life. ;-) Anyway... I know mono 1.2.4 is old. But what version of .Net is it compatible with? We may decide we're able to develop everything we need to develop, using that version... Or we may just drop support for centos5. I can't envision us saying we'll support ubuntu only and not redhat... Which means we're already limited to a maximum .Net 3.5. Thanks again... ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] .Net versions ... compatibility history
Keep in mind that just because a certain Mono version supports a certain .NET profile, doesn't mean it fully supports everything in that profile. For example, Mono 2.0 supports .NET 2.0 and 3.5, but has many missing 3.5 bits. Even the latest Mono versions do not support all the APIs .NET does. So things are not as simple as deciding which .NET version you want to support. By the way, check out the Mono wikipedia page: http://en.wikipedia.org/wiki/Mono_%28software%29#History It may give you the overview you're looking for. It says Mono 1.2 supports C# 2.0, but that the APIs are not on par with .NET 2.0 until Mono 2.0. edward.harvey.mono wrote From: mono-list-bounces@.ximian [mailto:mono-list- bounces@.ximian] On Behalf Of Stifu I don't know of documentation for this, but Mono 2.4 is old, and I wouldn't bother trying to support anything older. If we wish to develop distribute a server product using mono... It would be good to support rhel 5 6, as well as the various ubuntu LTS. Right now, ubuntu LTS all seem to have mono 2.10, which is good. But ... But centos 5 (epel5) has mono 1.2.4, and centos 6 (epel6) has mono 2.4.3. Maybe we'll just have to drop centos5 as a supported platform, but if you are a business distributing a product, telling your customers that you can only support the very latest OS, it makes it difficult for the customers to accept your product... Just ask any sysadmin who supports apple products. ;-) The day a new OS is released, the old OS is unsupported, so you as a company are forced to immediately drop what you're doing and test the new OS, as if the mac product release cycle is the only important thing in your life. ;-) Anyway... I know mono 1.2.4 is old. But what version of .Net is it compatible with? We may decide we're able to develop everything we need to develop, using that version... Or we may just drop support for centos5. I can't envision us saying we'll support ubuntu only and not redhat... Which means we're already limited to a maximum .Net 3.5. Thanks again... ___ Mono-list maillist - Mono-list@.ximian http://lists.ximian.com/mailman/listinfo/mono-list -- View this message in context: http://mono.1490590.n4.nabble.com/Net-versions-compatibility-history-tp4650745p4650765.html Sent from the Mono - General mailing list archive at Nabble.com. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list