On Mon, 3 Nov 2003 02:03:39 +0100 (Romance Standard Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote:
> Ugh, I disagree. wxTextCtrl style support is buggy, this is true. But > other than that I don't think there are many bugs in wxWindows [that affect > us]. wxString is still sensitive to null characters. wxWindows 2.4 had broken wxString.find_* functions and sorted array lookup. wxListCtrl items used to trash/garble pointers when one forgot to set a mask. I know it's my error, but library provides abstraction and in case of wxListCtrl, this abstraction leaks. It's surprising how wxWindows often imitates Windows API including all misfeatures. There are many bugs in Gtk and instead of fixing them, wxWindows waits until they get fixed themselves (and they won't). The infinite recursion in font mapper looked very untested. Sizers often don't do their job of maintaining layout, especially when layout changes dynamically. I understand that wxWindows developers like to accept patches, but there is no marking of features as stable / new / experimental / broken. Features aren't fully covered in docs and samples. There is no interest in making stuff work in all cases and make it developer-friendly, just make it work at all. > And we're in a rather unique position to be able to fix the bugs in > the UI toolkit we use ouselves which is an advantage. And what about bugs in Gtk? I know it's a rant. There is no alternative to wxWindows that would do better job. But that isn't good excuse to waste contributor's and developer's time on bugfixes and workarounds. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
