I’ve released version 1.7.5 of the TrackBar control. It slightly changes the event order (regarding the various change types) of the PositionChanging and PositionChanged events.
I’ve updated the StatusBar, TabStrip, ToolBarControls, and TrackBar control libraries to fix the memory leaks. Now all controls are up-to-date again.
I’ve updated the ExplorerListView, ExplorerTreeView, and TrackBar controls to fix the drag’n’drop crashes.
As promised I’ve released updates to the ComboListBoxControls, ProgressBar, and TrackBar libraries, introducing the FinishOLEDragDrop method.
I’ve released a new version of the TrackBar control. It now has events for extended mouse button clicks and for mouse wheel scrolling. Additionally I’ve reactivated the data-binding capabilities.
Be aware that the events for the extended mouse buttons depend on the mouse driver configuration. So if they are not raised at all, this is more likely because of the mouse driver than because of potential bugs in the control library.
I’ve released updates for the ProgressBar, StatusBar and TrackBar controls. ProgressBar and TrackBar no longer support data-binding. The reasons are the same as for the ComboListBoxControls library which I’ve released three days ago.
All three releases also fix problems with the ResizedControlWindow event and Windows 8 now is officially supported.
I’ve released new versions of Animation, ButtonControls, EditControls and TrackBar. All controls come with improved drawing code which fixes a couple of problems that could occur with version 6.0 of comctl32.dll.
You might wonder what happened to ButtonControls 1.8.0. Well, I released it yesterday and an hour later I had an idea how the drawing performance of the Frame control can be improved extremely while making it more robust against drawing issues at the same time. I could have canceled the release, but this would have produced some chaos in my source code repository.
EditControls 1.8.0 contains an interesting new VB6 sample project: A search box that looks and feels like the search box of Windows 7 Explorer. It also requires the ToolBarControls library and runs on Windows Vista/7 only with Aero Glass being activated – that’s the price for using modern API calls.
I’ve released the following controls:
- DateTimeControls 1.3.0
- EditControls 1.7.0
- ExplorerListView 1.3.0
- ExplorerTreeView 2.2.0
- TabStrip 1.5.0
- TrackBar 1.5.0
The DateTimeControls, EditControls and the TrackBar control have got the new DetectDoubleClicks property. For some controls, for instance for the Calendar control, Windows does not detect double mouse clicks. I wanted to provide DblClick events, so I worked around this limitation. Unfortunately the Microsoft developers had good reasons to not detect double-clicks for some controls. For instance if you rapidly click on the navigation arrows of the calendar control, you want the months fly by rapidly, but with double clicks enabled, the app will run into double clicks every now and then, and this slows down navigation alot. So I decided to implement a new property which can be used to deactivate my work-around. Attention: For the Calendar control and the up-down part of the UpDownTextBox control, double-clicks now are disabled by default. If you use the DblClick events of those controls, make sure to change the DetectDoubleClicks property to True.
The TabStrip control now can attach a window (usually a control) with a tab and show/hide this window depending on the tab selection. This should make it a bit easier to display different controls on each tab. For instance the attached window could be a Frame control (without border and caption) that contains a specific tab’s child controls. Selecting the tab would make the Frame control (and its content) visible; unselecting the tab would make the Frame control invisible.
ExplorerListView and ExplorerTreeView come with new sorting capabilities. There are new sort criterions which are based on the item text (just like sobText), but treat the texts as integer values, floating point values, currency values or date/time values. Your items are named “1”, “10” and “2” and you want them to be sorted “1”-“2”-“10” instead of alphabetically, which would be “1”-“10”-“2”? No problem! Simply specify sobNumericIntText as the sort criterion. You can also specify the locale identifier and a couple of flags that are applied when parsing the texts. Of course all this also applies to sorting listview groups.
Additionally I improved the ItemGetDisplayInfo event a bit.
I’ve released the remaining updates. ShellBrowserControls has been ported to Visual C++ 2010 (no support for Windows 2000 anymore, sorry). The other releases are bugfix releases.
Here are some more controls that I have fixed and migrated to Visual C++ 2010.