- 2013-03-12: Version 0.9.2 released. No new features, but many bugfixes.
- 2013-03-12: What a busy week. I experienced hard disk failure, so spent a lot of time to save some data, reinstalling Windows and all the SW on new disk. A lot of fun was also caused bz the idea to register mCtrl as a project for Coverity Scan. False positive rate is quite low and acceptable and it indeed found so many bugs, some of them quite major. Static analysis capabilities of the tool really impressed me. Thank you, Coverity!
- 2013-03-03: Minor update 0.9.1 comes. The coolest news of this release is animation of MdiTab and expand controls, but of course there is more. See ChangeLog for more info.
- 2013-02-06: New version 0.9.0 brings many new features, including new chart control, expand control and tree-list view control. Note that it also breaks binary compatibility with older versions. However I consider it as a major step towards 1.0 and API freeze. See ChangeLog for more complete list of changes.
Call for Help
Do you like the project? Do you think the progress is too slow?
Currently the project is one man show. Feel free to contact me and join. There certainly is a lot of space for other developers, documentators or testers.
Last but not least some help about graphic would be also appreciated. The project still lacks any kind of logo and sometimes some icon for purposes of the controls might be needed.
API of the MCTRL.DLL library is not yet rock-stable and can change any time. However bigger fundamental changes to components which are generally (almost) complete are unlikely.
Once we reach version 1.0, the API will be stabilized and since that point the source as well as binary compatibility will become strict requirement for further development.
The version 0.9 is considered the last big step towards 1.0. During the 0.9.x lifetime the <mCtrl/value.h> and controls used that API (grid, property list view) should be finished and their API stablized, and once that happens we will approach to release 1.0 as soon as possible.
All the other controls and modules can be improved of course too, but for them the incompatibible changes in the API are very unlikely.