I’ve updated the DateTimeControls library to improve compatibility with Linux/Wine and ReactOS.
I’ve updated the Animation, DateTimeControls, and LabelControls controls to fix the drag’n’drop crashes.
Today I’ve released updates to the DateTimeControls, EditControls, and ExplorerTreeView libraries, introducing the FinishOLEDragDrop method.
I’ve released an update of the DateTimeControls library. The controls now provide events for extended mouse button clicks and 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 new versions of the Animation, DateTimeControls and EditControls libraries. They fix a couple of bugs, one of them being the infamous data-binding bug, which made me remove data-binding features.
I’ve released updates of the ComboListBoxControls and DateTimeControls libraries. They fix problems with various events, especially the ContextMenu event.
Additionally, the DateTimeControls library now officially supports Windows 8.
I’ve released version 1.3.1 of the DateTimeControls library. It fixes the problem that the MinDate and MaxDate properties did not really work at runtime.
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 some updates. They don’t contain new features, but fix several bugs.
More updates will come soon, so stay tuned.
I’ve released another update of DateTimeControls. The CaretDate property of the Calendar control could return invalid dates due to a strange behavior of the native calendar control of Windows.