|
From: Maurizio la C. <m.l...@gm...> - 2013-06-20 08:31:22
|
Hi Alex, 2013/6/20 Alexander S.Kresin <al...@be...> > Przemyslaw Czerpak writes: > > > > > Fatal code quality which begins to be problematic to keep it alive. > > Nothing amazing but something what has to happen sooner or later. > > This is exactly what I'm talking about last time. > And what I was meaning when you came back to hwgui and I told about the try-and-go growth of the library. > > > But it covers only very small subset of problems created by code > > which converts windows handles and pointers to numeric values and > > only for Win32. The time shows that it was bad decision because > > nothing has really changed in HWGUI code in next years. > > This conversion of pointers to numeric values ( HWG_PTRTOULONG() > function ), which is used everywhere in the code creates those problems > with focus, colors, etc. > HwGUI 2.16c is free of this problem, this is one of the reasons why I > suggest to get it as a base. It isn't ideal :), but it is much more clean. > > I already agreed with you and it seems to be the only way to have hwgui working good. I think that's better to add on a rocky base the new features, than to patch erratically a collapsing building. All the contributions of Basso and Culik since 2.16c could be implemented after purging them of pointers bugs. I'm trying to resume what, after 2.16c, was a patch and what a new feature. Maybe applying the introduced patches, before to add the enhancements, could be the right way. Regards. Maurizio > > Regards, Alexander. > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Hwgui-developers mailing list > Hwg...@li... > https://lists.sourceforge.net/lists/listinfo/hwgui-developers > |