ExplorerTreeView 1.x isn’t dead yet, just a bit rusty. 🙂 I’ve released version 1.15.0 which has some performance improvements and – more important – runs much more stable. Many thanks to Christian Lütgens for helping me nailing down the AutoUpdate crashes by providing helpful crashdumps and bug reports.
Speaking of crashdumps, ExplorerTreeView 1.x comes with (stripped) debug symbols now.
Category: Releases
-
ExplorerTreeView 1.15.0
-
ExplorerTreeView 2.0.0 RC2
I’ve released a second release candidate of ExplorerTreeView 2.0.0. I made some compatibility breaking changes to improve performance and to avoid incompatibilities with other controls of mine. You should read the changelog to see what has changed in detail and how your code needs to be changed. I think most of you will get away with a simple recompile.
Now to the better part of this release 😉 You can now specify whether you want Aero drag images or classic style drag images. I’ve also implemented two new events that are raised if the sort order is changed. And of course I’ve fixed bugs.
Under the hood, I’ve worked hard on the interface for the yet-to-be-released shell browser controls. I consider it to be complete. -
DateTimeControls 1.1.0
Here’s another update of DateTimeControls. I’ve added a new property “Value”. You may wonder why I did this, as there’s already the “CurrentDate” property. Well, “CurrentDate” is of type “Date”. This causes problems with data-binding if the table contains NULL values. Those NULL values should be handled as “no selection made”, i. e. the “DateSelected” property should be set to “False” on such a NULL value. However, you would need to bind 2 properties for 1 column. I doubt this is possible.
I could have changed the type of “CurrentDate” to “Variant” and change its implementation so that setting this property to a NULL value is handled as if “DateSelected” was being set to “False”. But this would have broken binary compatibility. Therefore I introduced a new property that combines “CurrentDate” and “DateSelected”.