CommonControls (Replacement of the MS common controls)

[xxdoc]

This project is intended to replace the MS common controls for VB6.

The "MSCOMCTL.OCX" (respectively "COMCTL32.OCX") can be replaced completly.
The "MSCOMCT2.OCX" (respectively "COMCT232.OCX") can be replaced completly.
The "RICHTX32.OCX" can be replaced completly.
The "COMDLG32.OCX" can be replaced completly.
The "COMCT332.OCX" can be replaced completly.
The "MCIWNDX.OCX" (shipped with VB5) can be replaced completly.
The "SYSINFO.OCX" can be replaced completly.

Following controls are available at the moment:

- Animation
- CheckBoxW
- ComboBoxW
- CommandButtonW
- CommandLink
- CoolBar
- CommonDialog (Class Module)
- DTPicker
- FrameW
- HotKey
- ImageCombo
- ImageList
- IPAddress
- LabelW
- LinkLabel
- ListBoxW
- ListView
- MCIWnd
- MonthView
- OptionButtonW
- Pager
- ProgressBar
- RichTextBox
- Slider
- SpinBox
- StatusBar
- SysInfo
- TabStrip
- TextBoxW
- ToolBar
- TreeView
- UpDown

Unicode is supported for all the stated controls.

At design time (IDE) there is only one dependency. (OLEGuids.tlb)
This is a modified version of the original .tlb from the vbaccelerator website.
But for the compiled .exe there are no dependencies, because the .tlb gets then compiled into the executable.

Everything should be self explained, because all functions and properties have a description.

This Demo shows of how to make the ToolBar control accessible per shortcut key on a MDIForm.

ActiveX Control versions, together with a Registration-Free (Side-by-side) solution:
Version 1.0 (End of support)
Version 1.1
Version 1.2

Notes:
- When using the SetParent API, then you should pass .hWndUserControl and not .hWnd to it.
- When changing the "Project Name", then you should have all forms open, else all properties are lost. Reason is due to the fact that the library to which the controls are referring is the "Project Name" itself. Keeping all forms open will ensure that the .frx files will be updated with the new "Project Name".
- In order to trap error raises via "On Error Goto ..." or "On Error Resume Next" it is necessary to have "Break on Unhandled Errors" selected instead of "Break in Class Module" on Tools -> Options... -> General -> Error Trapping.
- If you want to embed the controls into another UserControl then you need to add the following code (Post #597) into your UserControl. As else the accelerator keys like the Left/Right key will not work. This issue is only relevant when using the Std-EXE Version. (The OCX Version will just work fine without any additional code)

List of revisions:

04-Jun-2016
- Included the Level property of a Node in the TreeView control.
02-Jun-2016
- Included the ItemFromPos property in 'CbrBands' in the CoolBar control.
01-Jun-2016
- Bugfix in the Key (String) handling for the ListSubItems method 'Add', 'Item' and 'Remove' in the ListView control.
31-May-2016
- Noticeable less memory consumption in Report View in the ListView control.
  Also the Tag property in 'LvwListSubItem' is now as Variant.
- Some other minor internal improvements.
30-May-2016
- Fixed a bug when adding a ListSubItem in-between in the ListView control.
29-May-2016
- Tag property in class collections are now as Variant. (except for 'LvwListSubItem', which remains as String)
  At design-time only String variables can be set, like in the original MS control.
  It is not allowed to store circular reference objects. (error will be raised)
  Example: 'Set TreeView1.Nodes(1).Tag = TreeView1.Object' (Though TreeView1 without '.Object' is allowed)
28-May-2016
- Shadow objects in class collections are now also decoupled in run-time controls. (ImageCombo, LinkLabel, ListView and TreeView control)
  This ensures that UserControl_Terminate will always be fired.
  They were already decoupled in design-time controls. (TabStrip, StatusBar, ToolBar, CoolBar and ImageList control)
26-May-2016
- Included the ItemFromPos property in 'LvwColumnHeaders' in the ListView control. (via HDM_ORDERTOINDEX)
25-May-2016
- Included the NodeBeforeCheck event in the TreeView control.
23-May-2016
- Minor bugfixes in the TopItem property in the ListView control.
22-May-2016
- Improved the TopItem property in the ListView control.
  It can be used now also when groups are enabled in 'report' view. (LVM_GETTOPINDEX fails in this case, thus a workaround was necessary)
  Enhanced the code when in 'Icon', 'SmallIcon' and 'Tile' view.
21-May-2016
- Included the NodeBeforeSelect event in the TreeView control.
- Removed the GetFirstVisible function in the TreeView, ListView and ImageCombo control.
  It has been replaced by the TopItem property. It can be even 'Set' in the TreeView and ImageCombo control.
- The NodeCheck event is now also fired when the checked state of a node was changed by code in the TreeView control.
- The ItemCheck event is now also fired when the checked state of an item was changed by code in the ListBoxW control.
- The ColumnCheck event is now also fired when the checked state of a column header was changed by code in the ListView control.
19-May-2016
- The DragIcon, DragMode and ToolTipText property are now also available when setting to a shadow object. ('Set' command)
- The Drag and SetFocus method are now also available when setting to a shadow object. ('Set' command)
17-May-2016
- Included the class 'RtfOleCallback' in the RichTextBox control.
  This decouples the IRichEditOleCallback interface and ensures UserControl_Terminate will always be fired.
  When updating, please replace all components. (e.g. RichTextBoxBase.bas)
16-May-2016
- Improved the Expanded property of a Node in the TreeView control. It works now like in the original MS control.
  It is now ensured that BeforeCollapse/BeforeExpand and Collapse/Expand events are always fired when state is being changed.
  Also it is now possible to set the expanded state even when there are no child items associated.
- To support large numbers the Children property of a Node returns now 'Long' instead of 'Integer' in the TreeView control.
15-May-2016
- It is now possible to pass a Node object in the Relative parameter in Nodes.Add and Node.Move in the TreeView control.
- Removed the error message 'the size of the selected picture is not compatible' in the Images property page of the ImageList control.
  So at design time it is now allowed to select different sized pictures. At run time it was already allowed.
  The original MS control allows it also. So such error message was a unnecessary limitation.
12-May-2016
- Fixed a bug in the Move method of a Node and some other internal improvements in the TreeView control.
  Bugs were in relation to the new ExpandedImage property of a Node.
11-May-2016
- Included the ExpandedImage property of a Node in the TreeView control.
08-May-2016
- The SelChange event is now also fired when value or selection was changed by code in the MonthView control.
- Some internal improvements in the DTPicker and MonthView control.
06-May-2016
- Fixed a bug that the DateClicked parameter in the DateClick event was invalid in the MonthView control.
- Included Error 35770 "An invalid date range was specified" in the MonthView control.
05-May-2016
- Fixed a bug that the Change event was not fired when the checkbox state changed in the DTPicker control.
- Included Error 35787 "Can't set Value to Null when CheckBox property is False" in the DTPicker control.
  This Error is also raised in the original MS control.
04-May-2016
- The Change event is now also fired when value was changed by code in the DTPicker control.
  Though in the original MS control it is only raised when value was changed by user.
  But that makes actually no sense and might be even a bug in the original MS control.
15-Apr-2016
- Minor adjustment to the BackColor in the StatusBar control so that the Pager control can recognize it.
31-Mar-2016
- Minor bugfix in the internal Numeric/Currency/Date sorting functions in the ListView control.
09-Mar-2016
- Improved the calculation that determines if DPIs are different. All controls are now really "DPI Aware".
01-Mar-2016
- Bugfixes and improvements for vertical ToolBar control. (Align property set to vbAlignLeft or vbAlignRight)
  The Vertical ToolBar behaves now like the original MS control when the Wrappable property is set to False.
  Also changing from horizontal to vertical and vice versa after initialization works now properly.
29-Feb-2016
- All controls are now "DPI Aware". (concerns exotic DPI or very large DPI, e.g. 113% and 200%)
- ComboBoxW with Style 'CboStyleDropDownCombo' is now working on Windows 2000.
  Message CB_GETCOMBOBOXINFO is not supported on Windows 2000, so little workaround was necessary to solve this.
- Some other minor internal improvements.
25-Feb-2016
- Minor adjustment to the BackColor in the ToolBar control so that the Pager control can recognize it.
24-Feb-2016
- Fixed a bug that the Scroll event fired twice instead of once in the Slider control.
19-Feb-2016
- The BackColor property in the ToolBar control is now shown/visible at design-time.
  But it remains ignored when the control paints via double-buffering. (also at run-time)
30-Jan-2016
- Included the ShowTrailingDates property in the MonthView control.
- Included the CalendarShowTrailingDates property in the DTPicker control.
- Forgot to rename the HotTrack property to 'HotTracking' in the property page of the SpinBox control.
28-Jan-2016
- Fixed a bug in the LVN_ITEMACTIVATE handler in the ListView control.
  The Shift parameter in the ItemActivate event was not properly set.
19-Jan-2016
- Renamed the HotTrack property to 'HotTracking' in the SpinBox control.
  So the wording is in line with the UpDown, TreeView, TabStrip, ListView and LinkLabel control.
07-Jan-2016
- Included the MaxText event in the TextBoxW and RichTextBox control.
01-Jan-2016
- Mouse events now again in correct order in the ImageCombo, TreeView and ListView control.
  Some workaround was necessary to raise them 'After' (refer to update 21-Nov-2015) and keep correct order.
  Issue was an internal modal message loop on these controls. (DragDetect)
29-Dec-2015
- UserControl_Resizer is now called in the CoolBar control when setting a child control.
08-Dec-2015
- WM_MOUSEWHEEL handlers are now "processed" (no forward to the chain anymore) in the DTPicker and MonthView Control.
02-Dec-2015
- Fixed a bug in the mouse events in the ListView and TreeView control. (relates to update on 21-Nov-2015)
23-Nov-2015
- Forgot to include ListBoxW and ComboBoxW in the ComCtlsIDEStopProtectionHandler.
- InitReleaseVisualStyles function in VisualStyles.bas is now only called outside IDE.
  This is more efficient then always call InitReleaseVisualStyles and do the IDE check on ReleaseVisualStyles.
21-Nov-2015
- Mouse events (e.g. MouseDown) are now raised 'After' the window procedures. (like MS controls do)
  When using the GetCapture() API in the mouse events the return values are now appropriate.
  Also calling for instance a MsgBox in the mouse events does not mess up the mouse capture anymore.
  All other events (e.g. KeyDown) remains 'Before', as the values can be altered. (like MS controls do)
20-Nov-2015
- Included the TabScrollWheel property in the TabStrip control.
16-Nov-2015
- Included the constant 'CdlPDUseDevModeCopies' in the CommonDialog class.
15-Nov-2015
- Less memory consumption in Report View in the ListView control.
13-Nov-2015
- Control arrays are now working properly on all controls.
  Shadow objects in class collections are now decoupled in design-time controls. (TabStrip, StatusBar, ToolBar, CoolBar and ImageList control)
10-Nov-2015
- Improved the InitReleaseVisualStyles function in VisualStyles.bas.
30-Oct-2015
- Some minor internal improvements.
29-Oct-2015
- Fixed a bug in the Font property in the LinkLabel control.
- Setting 'Nothing' to the Font properties does not raise an error anymore.
  Instead in that case the Font will be set to the 'Ambient.Font'. (like MS controls do)

[...]

11-Nov-2012
- First release.

Attachment 132059Attachment 132057

The attached file is a .rar file with a .zip extension so it could be uploaded.
This is necessary as for a zip file there is a file limit of 500 KB.

how can i used HotKey.control....may be have some Instructions

[Tech99]

See the demo project, for the general usage... However it is quite easy to define hotkey and window handle to it.

' Set CTRL + ALT + F10 as the default hot key.
HotKey1.Value(vbCtrlMask + vbAltMask) = vbKeyF10
HotKey1.SetApplicationHotKey (Me.hWnd)

[xxdoc]

how can i Raise Event is i used CTRL + ALT + F10 for example。if everyone used CTRL + ALT + F10，i want hide EXE? THANKS

[xxdoc]

See the demo project, for the general usage... However it is quite easy to define hotkey and window handle to it.

' Set CTRL + ALT + F10 as the default hot key.
HotKey1.Value(vbCtrlMask + vbAltMask) = vbKeyF10
HotKey1.SetApplicationHotKey (Me.hWnd)

how can i Raise Event is i used CTRL + ALT + F10 for example。if everyone used CTRL + ALT + F10，i want hide EXE? THANKS

[Tech99]

how can i Raise Event is i used CTRL + ALT + F10 for example。if everyone used CTRL + ALT + F10，i want hide EXE? THANKS

I believe that Hotkey control handles that - at least API function fails, if the key combination is already registered as a system wide hotkey.

So there could be no 'everyone used' this/that combination situation what so ever.

https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

[Chrissss]

Hello,

and thanks a lot for this great piece of software. Works really fine so far.

I only encountered a problem with the tree view:
When using it in a custom control, the keys e.g. left, right, up, down and Enter (when editing the text of a node) are NOT working.

[Chrissss]

Hello,

and thanks a lot for this great piece of software. Works really fine so far.

I only encountered a problem with the tree view:
When using it in a custom control, the keys e.g. left, right, up, down and Enter (when editing the text of a node) are NOT working.

Now I have attached the example project were you can see this:
treeview.zip

Tested with VBCCR12.OCX 1.2.0.29


Another issuew with the treeview:
The key property of a node is write protected, although it is not in the original non unicode treeview. Any chance to make the key property writeable as well?

Thanks a lot and keep up this great development!
Chris

[Krool]

I only encountered a problem with the tree view:
When using it in a custom control, the keys e.g. left, right, up, down and Enter (when editing the text of a node) are NOT working.

And normally it works? (When not editing text)
Does it work on the ListView? (for test)

Maybe try this:
If you want to embed the controls into another UserControl then you need to add the following code (Post #597) into your UserControl. As else the accelerator keys like the Left/Right key will not work. This issue is only relevant when using the Std-EXE Version.

[Karl77]

if i want used one control .i must del other controls,or when i load all controls that is a very big exe.can any good ider?

Sure the EXE becomes larger if you use all the provided controls.
On the other hand, you don't have to struggle with the MS originals.

If the size matters, you can, as you said, remove the unused controls, then the EXE becomes smaller.

Or just use the OCX version, then your EXE is as small as usual.

[Chrissss]

Thanks a lot.

This topic was already discussed in this thread.

ok, but clearly I i did not read the whole thread, and searching will search the whole forum and not only this thread.
So may be you may think about an own forum. This would help a lot.

Chris

[DaveInCaz]

searching will search the whole forum and not only this thread.

There is a "search thread" function up at the top.

[DEXWERX]

No need to search when, just read the first post.

Notes:
- If you want to embed the controls into another UserControl then you need to add the following code (Post #597) into your UserControl. As else the accelerator keys like the Left/Right key will not work. This issue is only relevant when using the Std-EXE Version. (The OCX Version will just work fine without any additional code)

[Krool]

Update released.

Important when using the ListView control.
LabelEdit is now working again.

[mozaiktm]

Update released.

Important when using the ListView control.
LabelEdit is now working again.

Hi Krool, thanks for the CommonControls, it's very helpful

but i have some problem,
is there a way to add an image to ImageList and display it to the ListView from code?
i mean, i want to add an image from file (such as icon from .DLL file), when i try to do this, the ListView just displaying black image.

Thanks. (and sorry for my bad english )

[Karl77]

Mozaiktnm,

I had similar problems with the toolbars.
Perhaps it is the same with the listview.

In case of PNGs with Alpha, you need to use the imagelist Krool provides.
And in this imagelist, you need to set the image format:

.ColorDepth = ImlColorDepth32Bit

Please try this.

[Krool]

Update released.

ExpandedImage is a Vista+ thing, there's other features missing too--

I includeded on 11-May-2016 the ExpandedImage property, but this was implemented using TVN_GETDISPINFO and I_IMAGECALLBACK.
So even Win XP users can benefit from it..

the TVITEMEX type doesn't have the other 6.0 members either (uStateEx that allows nodes to be grayed out as disabled).

This has been implemented by this update. (Enabled property)

I had similar problems with the toolbars.
Perhaps it is the same with the listview.

In case of PNGs with Alpha, you need to use the imagelist Krool provides.
And in this imagelist, you need to set the image format:

.ColorDepth = ImlColorDepth32Bit

Should I set the ColorDepth property to ImlColorDepth32Bit instead of ImlColorDepth24Bit by default ?

[Karl77]

Should I set the ColorDepth property to ImlColorDepth32Bit instead of ImlColorDepth24Bit by default ?

Krool, I'm not so sure.

I assume most of today used images will be 32bit and nothing else.
In this respect it makes sense to have the default 32bit.

The original imagelist seems to have an automatic for this.
It can hold and manage 32bit images without explicitely setting it.

I think to copy this automatic is far too much effort.
Change the default to 32bit or just leave it as it is now.

To avoid an obstacle for new users of your project, it could be an idea to update the sample project using PNGs w. Alpha or BMP32.


My 2 cents.

Karl

[Karl77]

So even Win XP users can benefit from it..

I would drop XP support completely.


Karl.

[DEXWERX]

Should I set the ColorDepth property to ImlColorDepth32Bit instead of ImlColorDepth24Bit by default ?

I think the VB6 imagelist detects a bitdepth when an image is loaded.

[Cube8]

I would drop XP support completely.


Karl.

You shouldn't, since there are still many XP installations out there.

[Arnoutdv]

You should drop support, XP is not even supported by MS anymore

[Krool]

You should drop support, XP is not even supported by MS anymore

I even support W2k...
I think there are many systems out there which are isolated and embedded and still use XP or even W2k. And they don't need to worry as it's not connected to internet or a network.

They are some hassles and workarounds sometimes of course..

[LeandroA]

hi in the Treeview is not present NodeLevel property, TreeView1.Nodes(x).Level

[Krool]

hi in the Treeview is not present NodeLevel property, TreeView1.Nodes(x).Level

It was included on 4th of june.
However, not yet in the OCX. It will be included there when releasing VBCCR13..

[Krool]

Big update released.

Finally, it is possible to set now a index or key in a Image property in the class collections.
Affected are the CoolBar, ListView, ToolBar, ImageCombo, TabStrip and TreeView control.

[Krool]

Update released.

Also the new 1.3 ActiveX Control version (VBCCR13.OCX), together with a Registration-Free (Side-by-side) solution, is now available.

[Karl77]

Finally, it is possible to set now a index or key in a Image property in the class collections.

Cool Krool.
This extensions makes so much sense, thank you for this.

Karl.

[DEXWERX]

Is there a way to get the checkbox or option boxes to have a transparent bg when used on a coolbar? similar to the way they look on a tabstrip.

edit: FYI definitely not important, since i dont even use the coolbar currently!

[jpskiller]

Windows 10
1.3 OCX activeX register error, I have not tried this before, but can you help please when I try to register I get Error : file loaded but unable-to-register-dll-error-code0x80004005, I have loaded cmd in admin mode but still same error, can some please help, basic guide thanks

[Tech99]

Possibly you are using wrong (64-bit version) of regsvr32 tool.

Correct path/folder to 32-bit executable is:
C:\Windows\SysWOW64\regsvr32.exe

https://support.microsoft.com/en-us/kb/249873

[jpskiller]

Possibly you are using wrong (64-bit version) of regsvr32 tool.

Correct path/folder to 32-bit executable is:
C:\Windows\SysWOW64\regsvr32.exe

https://support.microsoft.com/en-us/kb/249873

Yes I tried that one same error, do I have to put the OCX file in a specific folder.

[Elroy]

Say Krool,

The "ImageList" control isn't listed in your Select Case statement in the ComCtlsIDEStopProtectionHandler procedure.

Are we to assume that the ImageList control has no subclassing, or is this possibly an oversight?

In any case FANTASTIC work.

Thanks,
Elroy

[Krool]

Yes I tried that one same error, do I have to put the OCX file in a specific folder.

You need to put the OCX to C:\Windows\SysWOW64.

Are we to assume that the ImageList control has no subclassing, or is this possibly an oversight?

Yes, no subclassing. Thus no need to put into the ComCtlsIDEStopProtectionHandler procedure. Thanks anyhow.

[jpskiller]

[QUOTE=Krool;5069083]You need to put the OCX to C:\Windows\SysWOW64.

Thanks for info, I have tried that and still get same error "The module "vbccr13.ocx" was loaded but the call to DllRegisterServer failed with error code 0x80004005", I will just stick to standard method.

[Krool]

Thanks for info, I have tried that and still get same error "The module "vbccr13.ocx" was loaded but the call to DllRegisterServer failed with error code 0x80004005", I will just stick to standard method.

Are you sure running the CMD with admin?

1. Click the Start button, then in the "Start Search" box, type CMD but DO NOT press Enter yet.
2. In the list above, under "Programs" right-click on CMD that appears above and choose "Run as Administrator" and click. You might need to press Shift while right clicking to have the "Run as Administrator" in the list.
3. In the open window, type the following command and press Enter:

regsvr32 c:\windows\sysWOW64\VBCCR13.OCX

[jpskiller]

Are you sure running the CMD with admin?

1. Click the Start button, then in the "Start Search" box, type CMD but DO NOT press Enter yet.
2. In the list above, under "Programs" right-click on CMD that appears above and choose "Run as Administrator" and click. You might need to press Shift while right clicking to have the "Run as Administrator" in the list.
3. In the open window, type the following command and press Enter:

regsvr32 c:\windows\sysWOW64\VBCCR13.OCX

thanks that seems to have worked, it was failing using the regsvr32 from the sysWOW64 folder

[fafalone]

OCX hell is why I offer a hearty "thank you" to Krool for providing the .ctl's that don't need one of those infernal ocx's.

[AAraya]

The textbox has a great Property

AllowOnlyNumbers

would it be possible to add AllowDecimal, and/or how many digits after the Decimal?

This is a very useful property which I have just discovered also. There are cases where I want to allow negative numbers but this control seems to allow only positive whole numbers. It would be wonderful if "Numbers" was allowed to be defined somewhere (e.g. AllowDecimal, AllowNegative)

[lrd_VB6]

Hello

Very nice work, it is "almost" perfect.
I have a small problem with the control "TreeView"
If using the properties "BackColor" or "ForeColor", control is refreshed even if "Redraw" = False.

The easy solution is to change the method "Refresh"

Public Sub Refresh()

    If PropRedraw = False Then Exit Sub
    UserControl.Refresh
    RedrawWindow UserControl.hWnd, 0, 0, RDW_UPDATENOW Or RDW_INVALIDATE Or RDW_ERASE Or RDW_ALLCHILDREN
End Sub

I join my vb project converter to go from version 11-12 to version 13 of your OCX
Attachment 139475

[Shaggy Hiker]

I had to edit the attachment as it contained compiled binaries, which we don't allow because we can't vouch for their safety. Please remove any compiled files, such as .exe, .dll, or ocx files and re-attach.