CommonControls (Replacement of the MS common controls)

OCX release 1.3

Quote:

---

Originally Posted by Arnoutdv

OCX release 1.3

---

Not available for the moment, due to forum policy. Please PM me to get it by another way.
Revision count will be updated here, for your reference.

Great work, this is an awesome set of controls, however I have been unable to find a post about legally redistributing the OCX file. Can you point me in the right direction?

Quote:

---

Originally Posted by trose44

I have been unable to find a post about legally redistributing the OCX file. Can you point me in the right direction?

---

There is no written notice for free license. However, of course, feel free to redistribute with your app, preferable with the reg-free solution.

Quote:

---

Originally Posted by ishalom

Also the Label Control does not have an hWnd Property.

---

The LabelW is a lightweight control. (Windowless)
This way it supports true transparency, like the original.
Actually I do not miss the .hWnd on it, do you?

Quote:

---

Originally Posted by Krool

The LabelW is a lightweight control. (Windowless)
This way it supports true transparency, like the original.
Actually I do not miss the .hWnd on it, do you?

---

I also do not need the hWnd, what I do need is the ability to make it RightToLeft (a property which is not on your controls but is on the standard vb controls) without this property in design time, the only way to do it is with api which requires an hWnd.

Hello, everyone, who has more than 6 versions of comctl32.dll? My version is 5.0, Some of the features are not tested.

Quote:

---

Originally Posted by Krool

Update released.



I have now included the VerticalAlignment property in the LabelW control. It supports also multi-line text.

---

is this included in the OCX version 1.3.0.3?

Quote:

---

Originally Posted by ishalom

is this included in the OCX version 1.3.0.3?

---

No. Will be on next release, means 1.4.

Krool, simple question:

Is it possible to have the toolbar vertical?
I have no clue if comctl32 has this functionality...

It is because I need one, and up to now it is made of a bunch of 'normal' toolbars, each with one button.

Only a question.

Karl

Quote:

---

Originally Posted by Karl77

Is it possible to have the toolbar vertical?

---

There are vbAlignLeft and vbAlignRight in the Align property. They will make the toolbar vertical on the left or right of the form respectively.

Quote:

---

Originally Posted by chosk

There are vbAlignLeft and vbAlignRight in the Align property. They will make the toolbar vertical on the left or right of the form respectively.

---

I know about align options, but speaking of orientation.

Quote:

---

Originally Posted by Karl77

I know about align options, but speaking of orientation.

---

The orientiation is vertical when you set the align option to vbAlignLeft or vbAlignRight.

Quote:

---

Originally Posted by Krool

The orientiation is vertical when you set the align option to vbAlignLeft or vbAlignRight.

---

Yes, this works when the toolbar is on the form.
BUT:

When it is in a picturebox, then it can't align...
...and the toolbar is always horizontal.

And as a next case, the toolbar is placed by .left and .top, so no alignment at all.

With the comctl32.ocx toolbar vertical orientation is not possible.
I thought maybe that's possible with the Krool toolbar.
Therefore the question.

Seems it is not possible.
Correct?

Karl

Quote:

---

Originally Posted by Karl77

Yes, this works when the toolbar is on the form.
BUT:

When it is in a picturebox, then it can't align...
...and the toolbar is always horizontal.

And as a next case, the toolbar is placed by .left and .top, so no alignment at all.

With the comctl32.ocx toolbar vertical orientation is not possible.
I thought maybe that's possible with the Krool toolbar.
Therefore the question.

Seems it is not possible.
Correct?

Karl

---

For the moment not..
The behavior should remain the same, but I could include a Orientation property to make this possible.
It would be just overwritten when changing the align option, but that should be no problem.

Quote:

---

Originally Posted by ishalom

the vb controls have a RightToLeft Property, with your OCX I have to use window API, and on a form with a controls it's a bit messy.

this is the code used for RightToLeft

Code:

---

Private Declare Function GetWindowLong Lib "User32" Alias "GetWindowLongA" (ByVal hWnd As Long, ByVal nIndex As Long) As Long
Private Declare Function SetWindowLong Lib "User32" Alias "SetWindowLongA" (ByVal hWnd As Long, ByVal nIndex As Long, ByVal dwNewLong As Long) As Long
Private Const WS_EX_RIGHT = &H1000&
Private Const WS_EX_RTLREADING = &H2000&
Private Const WS_EX_LAYOUTRTL = &H400000
Private Const WS_EX_LEFTSCROLLBAR = &H4000&
Private Const GWL_EXSTYLE = (-20)

Private Const GWL_STYLE = (-16)
Private Const WS_EX_NOINHERITLAYOUT = &H100000

Public Sub SetRTLControl(hwnd As Long)
Dim l As Long
l = GetWindowLong(hwnd, GWL_EXSTYLE)
l = l Or WS_EX_LAYOUTRTL
l = SetWindowLong(hwnd, GWL_EXSTYLE, l)

End Sub

---

---

RightToLeft is still a open topic. I really need to include it..

At the moment I have only the following when creating a control:

Code:

---

If Ambient.RightToLeft = True Then dwExStyle = dwExStyle Or WS_EX_RTLREADING

---

However, this makes only the text and not the layout RTL. (I am not adding the WS_EX_LAYOUTRTL style)
And I think the code above should be removed. It's a kind of automatism which should be avoided.

Instead, I would need to include a RightToLeft property to all controls which could then be set the following values: (enum instead of boolean)
- CCRightToLeftNone
- CCRightToLeftText (WS_EX_RTLREADING)
- CCRightToLeftLayout (WS_EX_RTLREADING)
- CCRightToLeftTextLayout (WS_EX_RTLREADING+WS_EX_LAYOUTRTL)

Default property would be CCRightToLeftNone.
And nothing else, correct?

PS: The VB's intrinsic RightToLeft properties are all read-only. (and only boolean)

Quote:

---

Originally Posted by Krool

I could include a Orientation property to make this possible.

---

Would be great!
Thanks for that in advance...

Karl

Again concerning the RightToLeft open topic.

What about doing like in .Net?
Two properties. 'RightToLeft' enum property and 'RightToLeftLayout' boolean property.

RightToLeft enums would be:
- Inherit (check for Ambient.RightToLeft; default value)
- No
- Yes

In addition the horizontal alignment properties would be reversed when RightToLeft.
So for instance setting right text align when RightToLeft is Yes the text will be displayed left.

And like MSDN states:
The RightToLeftLayout and RightToLeft properties cause the following Win32 API window styles to be set:
When RightToLeft is set to Yes and RightToLeftLayout is set to true, Windows Forms sets the WS_EX_LAYOUTRTL window style, and removes the WS_EX_RIGHT and WS_EX_RTLREADING styles.
When RightToLeft is set to Yes but RightToLeftLayout is set to No, Windows Forms sets the WS_EX_RIGHT and WS_EX_RTLREADING window styles.

Unlike RightToLeft, RightToLeftLayout does not inherit. If you want it to take effect for child controls, you must set it on each child control that you want mirrored.

Found a problem with the ComboBoxW control. Setting the Text property of the control does not fire the Change event like it does for VBs intrinsic Combo control

Code:

---

ComboBoxW1.Text = "foo"

Private Sub ComboBoxW1_Change()
  'we never make it here
End Sub

---

Quote:

---

Originally Posted by AAraya

Found a problem with the ComboBoxW control. Setting the Text property of the control does not fire the Change event like it does for VBs intrinsic Combo control

Code:

---

ComboBoxW1.Text = "foo"

Private Sub ComboBoxW1_Change()
  'we never make it here
End Sub

---

---

Thanks a lot for notifying this bug.
Update released.

Update released.

Important bugfix in the TextBoxW control.

Quote:

---

Originally Posted by Krool

Update released.

Important bugfix in the TextBoxW control.

---

It might be better if the Change event was raised in a WM_SETTEXT handler in the WindowProcControl procedure rather than doing it only in the Property Let Text procedure. This way, that event will always be raised regardless of who sent the WM_SETTEXT message.

Quote:

---

Originally Posted by Bonnie West

It might be better if the Change event was raised in a WM_SETTEXT handler in the WindowProcControl procedure rather than doing it only in the Property Let Text procedure. This way, that event will always be raised regardless of who sent the WM_SETTEXT message.

---

Interesting issue.

Indeed the intrinsic VB TextBox control has some kind of special WM_SETTEXT handler. It raises the Change event in a multi-line TextBox. The VB TextBox does not send a EN_CHANGE notification, it must just raise the event inside the WM_SETTEXT handler.
However, for the other controls (e.g. ListBox control), there it does not do something similar. For instance for the LB_SETCURSEL message. It seems the VB ListBox does not have an handler which raises a Click event. You must go via the .ListIndex property there.
So VB is not consistent at that point.

Quote:

---

Originally Posted by Krool

This is the 1.2 ActiveX Control version. (Revision 35)

Not available for the moment, due to forum policy. Please PM me to get it by another way.
Revision count will be updated here, for your reference.

Any bugfixes in future will be compatible to this binary and only the revision number will be incremented.

Advantageous compared to the Std-EXE version is that all property pages support Unicode.

All controls are marked as "Safe for Initialization and Scripting" by the IObjectSafety interface.
In order to mark the CommonDialog class also "Safe" it is necessary to run the following .reg file:

Code:

---

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\CLSID\{165B378C-D8A6-4C8F-B610-2E635D8CCBFE}\Implemented Categories]

[HKEY_CLASSES_ROOT\CLSID\{165B378C-D8A6-4C8F-B610-2E635D8CCBFE}\Implemented Categories\{7DD95801-9882-11CF-9FA9-00AA006C42C4}]

[HKEY_CLASSES_ROOT\CLSID\{165B378C-D8A6-4C8F-B610-2E635D8CCBFE}\Implemented Categories\{7DD95802-9882-11CF-9FA9-00AA006C42C4}]

---

Also everything is 100% IDE-Safe.

I do intentionally not publish the source code for this to avoid redundancies.

Here is a solution to use the VBCCR12.OCX Registration-Free. (Side-by-side)
Keep in mind that this technology needs at minimum Windows XP SP2 or Windows Server 2003.

Tutorial:
The "Development" machine needs to register VBCCR12.OCX as usual and use the components for e.g. in a Std-EXE project.
The source project needs to include the Side-by-side resources. (see below)
Then on the "End user" machine you only need the VBCCR12.OCX and the .exe (Std-EXE project) on the same folder.
It will work then without any registration.

The source code of "VBCCR12SideBySide.res" is:

Code:

---

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <file name="VBCCR12.OCX">
      <typelib tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" version="1.0" flags="control" helpdir="" />
      <comClass clsid="{4938782B-EFDC-4F54-B785-22D94B598CAA}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.CommonDialog" />
      <comClass clsid="{CA83B671-E5E4-48ED-938C-AA09DC61CF23}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{52CCAD04-8F72-42EF-9CA6-1D5D32D32539}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.UpDown" />
      <comClass clsid="{AFE52611-B3DB-4F9A-BC0F-F8C1D1344283}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{41E56E2A-E5E9-4F84-BE0B-79410C6AD60A}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.TreeView" />
      <comClass clsid="{2E9EEB68-F22F-4A19-8067-2353DCFEC88D}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{73B1DA0C-550B-4B41-AB19-68762CD75358}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.ToolBar" />
      <comClass clsid="{8E2D8071-8604-4116-91C1-BC7461F5BABD}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{5932F494-2E1F-4676-858F-5E54C9377699}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.TextBoxW" />
      <comClass clsid="{55D92003-40FB-4F71-9358-D6265A09C6F4}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{2A8E2AEC-CD77-4B4F-BE9D-E35BF404B2B8}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{0AC8F571-4408-4EDC-A4E3-699AA5E42D08}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.TabStrip" />
      <comClass clsid="{97634C1B-0750-4883-9192-BC7E1D3E37DA}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{3E4FEC4F-F3B6-4B89-8977-C5F1034CC7B1}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.SysInfo" />
      <comClass clsid="{9F2A1D5C-DBB9-4AA1-BCDD-B22D459000CD}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{78A2017F-108A-4589-B781-92A52D95E1C3}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{628F93DE-7CD5-441A-9B7E-D9F51B27342B}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.StatusBar" />
      <comClass clsid="{D4704274-4568-4834-87F1-FD6577FEF1BF}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.SpinBox" />
      <comClass clsid="{E0FE8265-0026-4A36-9E63-E60B082AD49F}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{B540FC9E-2F8B-4642-BD04-A61AC116F6E2}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{117E0FF3-1238-4B11-AD15-C6E879493C42}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.Slider" />
      <comClass clsid="{9E81702A-9C01-4BFF-B10D-5478A6BD2510}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{AD6EA497-4030-41BE-9AEA-715871432A7F}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{D77AD8C9-6641-44F9-93A9-0F929F85C0E2}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.RichTextBox" />
      <comClass clsid="{06AAA6F9-62FE-4D09-A42E-C516B16B49B3}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.ProgressBar" />
      <comClass clsid="{6BAF28AD-48C7-4563-AA50-7E578E71DDB9}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{3E069F4E-5ACC-4A28-9127-DFF30BF52C9E}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.Pager" />
      <comClass clsid="{10F2C232-F4BC-4711-8923-540F01FC6F2B}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{F22158B5-7E4C-44B4-B6E9-44C7CDD8107D}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.OptionButtonW" />
      <comClass clsid="{9BD6A91A-87D1-4D8D-80BB-9EB3DDC7D6E4}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{98A5991B-5155-45D3-815A-286F07C7B3DA}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.MonthView" />
      <comClass clsid="{9D2E438F-13DA-4802-A007-F9E363E32967}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.MCIWnd" />
      <comClass clsid="{989D106B-7A55-4910-91EE-2A47B882A507}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{309E9BA5-282C-445D-95C2-41A888C34B18}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.ListView" />
      <comClass clsid="{DBFC2C6C-041A-459B-A3B8-88B36E5EB228}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{B9B78BB0-4E51-4607-AC19-BC7A0CE79649}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{0F6B581C-CA58-4B5A-9255-B2B8B7BD5B10}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.ListBoxW" />
      <comClass clsid="{AC620C93-A436-4D7F-AE53-9837AB26FB1E}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.LabelW" />
      <comClass clsid="{DACD338A-00B7-41E1-92FD-3C654DFAE69C}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.IPAddress" />
      <comClass clsid="{B8D9B38B-237F-4F82-BD26-1F4682622C3B}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{78B8EA9A-1EF1-419A-8439-D5417799FA69}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.ImageList" />
      <comClass clsid="{17A76F87-C369-4B9B-98E0-31C63759016B}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{315097F6-D7DD-41B7-A02A-6CF41DD21541}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.ImageCombo" />
      <comClass clsid="{8F123121-8337-402F-AAB2-D80A2DD11A88}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{B93C5C9F-C014-41F5-B1A2-40F0DB94DA74}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.HotKey" />
      <comClass clsid="{BBEF7185-E0BB-4D0B-A5BE-72213E465F2D}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.FrameW" />
      <comClass clsid="{2C5D0981-8AEE-4B2D-8AB0-F55059577B2B}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{A207419D-F0FA-4F71-8477-4C95C498E711}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.DTPicker" />
      <comClass clsid="{90A66ED3-BEFE-4D5C-A483-FAA5554B65D8}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.CoolBar" />
      <comClass clsid="{7B324862-998C-4BC0-925B-E1130F965402}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{3410BFDD-6DE4-455D-86B2-13A450564F37}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{97580CA2-47D7-4A34-B168-E88E59F4D337}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.CommandButtonW" />
      <comClass clsid="{1F7DA4F3-1D5C-4589-8CF8-F0DFFA65F55B}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.ComboBoxW" />
      <comClass clsid="{5F9353EA-0ECF-45EC-A346-B0B6AC272F93}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.CheckBoxW" />
      <comClass clsid="{F83FD275-F22A-44BE-B40D-C87F42391678}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{D9805339-0982-425C-A7CF-755563E867E5}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.Animation" />
      <comClass clsid="{E3F47B9A-4945-4374-ACFE-9BBE14B6EE74}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.LinkLabel" />
      <comClass clsid="{021EC4F5-9257-4156-B170-25BFF1E7FDD2}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
      <comClass clsid="{B33F398B-50DE-4DD2-94F2-AA73D0B008BE}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" progid="VBCCR12.CommandLink" />
      <comClass clsid="{418EA391-6365-4C0D-97E6-074BBB180CC9}" tlbid="{A1B7D620-9184-40D2-B545-9307A6E0C109}" threadingModel="Apartment" />
  </file>
</assembly>

---

In the attachment I have added the same as a compiled resource.

---

Krool,
Could you giveme the .ocx version? 1.2

Thanks

Hi,

seems I'm too dense to populate the treeview correct.
This is with version 1.2.

Code:

---

With TreeView1

.Add(, , "root", "Root 1").Expanded = True
.Add "root", TvwNodeRelationshipChild, "ch1", "Child 1"
.Add "root", TvwNodeRelationshipChild, "ch2", "Child 2"

End With

---

Treeview doesn't expand after the code above ran.
It always shows "Root 1" collapsed.
Of course, after a click, it expands.
But it shall have the children expanded from the beginning without having to manually expand them.

I tried several combinations.
Regardless what I do, always the same.

In the sample project it work as wanted.
But I don't see the difference to what I do...

Someone has a hint?

Karl

I always do it in code after the child nodes have been added.

Code:

---

Dim rootNode as Node

With TreeView1

  Set rootNode = .Add(, , "root", "Root 1")
  .Add "root", TvwNodeRelationshipChild, "ch1", "Child 1"
  .Add "root", TvwNodeRelationshipChild, "ch2", "Child 2"
 
  rootNode.Expanded = True
End With

---

Quote:

---

Originally Posted by Arnoutdv

I always do it in code after the child nodes have been added.

---

Ok, thank you, that works.
Seems the treeview is not 100% compatible with the 'original'.

Doesn't matter.
It's ok as it is.


Karl

Quote:

---

Originally Posted by Karl77

Ok, thank you, that works.
Seems the treeview is not 100% compatible with the 'original'.

Doesn't matter.
It's ok as it is.


Karl

---

Not true. Fixed both Std-Exe and OCX since 16-May-2016.

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.

So: Either use 1.3 or take the latest 1.2. (Watch for revision number)
Or use the Std-EXE version, of course.

Quote:

---

Originally Posted by Krool

16-May-2016
- Improved the Expanded property of a Node in the TreeView control.

---

Oh well yes Krool, I'm really behind.
Missed that totally.
Sorry for bringing up the same issue a second time, unnecessarily.

Karl

In IDE state to open the form MainForm will automatically exit.

I thought I have seen the question being asked previously but I may have mistaken because I am unable to find it.

How do I get the TabStrip's Placement property TbsPlacementBottom to work? Also Left and Right. Is there a pre-requisite? Whatever I choose, the tabs are always at the top.

Quote:

---

Originally Posted by chosk

How do I get the TabStrip's Placement property TbsPlacementBottom to work? Also Left and Right. Is there a pre-requisite? Whatever I choose, the tabs are always at the top.

---

The placement property works not when using comctl32.dll version 6 or above.
What do you mean with Left and Right?

Ok thanks.

I understand now why I can't get it to work in Windows 7 and 10.
Left and Right, I was meaning TbsPlacementLeft and TbsPlacementRight.

Quote:

---

Originally Posted by chosk

I understand now why I can't get it to work in Windows 7 and 10.
Left and Right, I was meaning TbsPlacementLeft and TbsPlacementRight.

---

Just for info. You can set the Placement property when the DrawMode property is set to 'OwnerDraw'.

EDIT: Was in wrong memory. It does only work when using comctl32.dll v5.8x. DrawMode property changes nothing in this case.

Plz enlight me on something...
Can you post a project... and/or explain how to use theses new component ?
You talked about using VBCCR13.OCX wich I did not find in any of your download link,
I did downloaded ComCtlsDemo, I can compile it without problem, I even registered OLEGuids.tlb
Where I'm stuck is, where is the OCX, and how do I use the RES file?

also, I noticed while downloading both RES file, they download as ANSI file but loading it in NotePad++, they are not ANSI file because they include some NUL caracter at begin and end. Is there any purpose to theses NUL caracter or can I remove them ?
I was under impression SideBySide were supposed to be XML file (therefore not containing any unusual caracter)

thanks a lot.

There are 2 versions of the controls.

1) ComCtlsDemo
The replacement common controls are all in UserControls, therefore no need OCX. You will see them under User Controls in the IDE. Where required, they come with their own Classes and Pages. They are all in the respective Build sub-folders.

2) OCX
You will find download instruction in the link on the first page. You may have already gone there since you know about the RES files. Read the instruction in red on how to download the OCX. The RES are VB6 resource files that includes side-by-side usage of the OCX without the need to register the OCX on target computers. On your development computer you will have to register the OCX. All information are in the respective download posts.

Listview - drag down works errorneosly.

interesting, does that happen with the VB6 ListView?

No, not to my knowledge. Items scroll over when dragged, as they should.

Quote:

---

Originally Posted by Tech99

No, not to my knowledge. Items scroll over when dragged, as they should.

---

Do you have SnapToGrid disabled? Also happen on Icon view instead of Tile View?

Quote:

---

Originally Posted by Krool

Do you have SnapToGrid disabled? Also happen on Icon view instead of Tile View?

---

Negative. Settings are/were as in attachment.

Quote:

---

Originally Posted by Tech99

Negative. Settings are/were as in attachment.

---

Try with setting SnapToGrid to False.

Quote:

---

Originally Posted by Krool

Try with setting SnapToGrid to False.

---

Yes - without SnapToGrid it doesn't push items in forward, but no worky either, as items are not ordered.

Dragged item stays where it is dropped, without added empty space to position item between items, likewise no removed empty space where the item was positioned before drag operation.

Quote:

---

Originally Posted by Tech99

Yes - without SnapToGrid it doesn't push items in forward, but no worky either, as items are not ordered.

Dragged item stays where it is dropped, without added empty space to position item between items, likewise no removed empty space where the item was positioned before drag operation.

---

I think for your purpose you need some kind of manual mode d&d. Like it is used in the Demo on the TreeView.
Start dragging and drop per InsertMark.

Quote:

---

Originally Posted by Krool

I think for your purpose you need some kind of manual mode d&d. Like it is used in the Demo on the TreeView.
Start dragging and drop per InsertMark.

---

Have to code it that way then.

btw... OleDragDropScroll = False - setting, does not have an effect as items are still scrolling down, when items are dragged down.

Quote:

---

Originally Posted by Tech99

Have to code it that way then.

btw... OleDragDropScroll = False - setting, does not have an effect as items are still scrolling down, when items are dragged down.

---

That property means scrolling the scrollbar when drag near the border, not item scrolling down.

Hi Krool,

I have been stumped for the past several hours and still not finding where the problem lies.

I am using the Std-EXE. I just place a LabelW in the startup form and in Form_Load I have only SetupVisualStyles Me, and this is the only code in the project nothing else.

I run the project and it is my bad habit (have to change this) to always click the stop button on the IDE. Usually this may not be a problem but in this case, it is always. This is not a problem with ComCtlsDemo.Then I get the error:

Debug.Assert CBool(OldPointer <> NewPointer) in Sub CreateSubclass in VTableSubclass.

If I were to put only a FrameW and nothing else, I get the same error.

I think it is something simple but I am not getting it. Any help will be appreciated.

Edit: Usually after asking for help on a stupid problem, the answer finally come itself. I should make Startup Object as Sub Main, instead of MainForm. Problem solved.

"Not available for the moment, due to forum policy. Please PM me to get it by another way.
Revision count will be updated here, for your reference."

So... If I got it in proper manner, to get the latest version of the controls, is to ask for them?
to who? and by what way?

Or I am missing something?

Quote:

---

Originally Posted by padbravo

"Not available for the moment, due to forum policy. Please PM me to get it by another way.
Revision count will be updated here, for your reference."

So... If I got it in proper manner, to get the latest version of the controls, is to ask for them?
to who? and by what way?

Or I am missing something?

---

You are missing the part, where it says to PM him.
Click on his name user name "Krool"
Click "Private Message"
Type in a message to ask him to email or send you a download link.

Hi Krool! I just stumbled upon this thread - Wow! Is this set of controls all your creation? I've been wanting to hack up VB's controls forever, and it looks like you've done it, the right way! The biggest one for me is Unicode support: VB ends up eating 2 bytes for every string character you store, but you get no benefit from it. And then you have to suffer conversion back and forth from Unicode to ANSI and back...What were they thinking?
Can I download and test your current version? Some more questions:
1. Do you accept bug fixes?
2. Do you consider/accept compatible enhancements to original functionality? (Enhancements that were not intended functionality, broken or otherwise?)
3. How close are you on completing your goals for this project? In other words, are you just doing bugfixes at this stage, or do you have a lot more to add?

You should sell this code - I'd be happy to pay for corrected functionality, after suffering MS' original offerings for many years. I know everyone has gone .NET, but I just can't get my head around that idea. VB's simplicity and feel just cannot be beaten. You've effectively built VB7 :)

Thanks in advance.

Quote:

---

Originally Posted by KurtB

Can I download and test your current version?

---

Sure. :)

Quote:

---

Originally Posted by KurtB

1. Do you accept bug fixes?

---

Feel free to report anything you like. Here public or private by PM.

Quote:

---

Originally Posted by KurtB

2. Do you consider/accept compatible enhancements to original functionality? (Enhancements that were not intended functionality, broken or otherwise?)

---

Yes

Quote:

---

Originally Posted by KurtB

3. How close are you on completing your goals for this project? In other words, are you just doing bugfixes at this stage, or do you have a lot more to add?

---

I am developing an MSFlexGrid replacement. (with more features and with bugfixes)
But that will be in a separate project. Not linked to this set of controls.
Concerning this project, I think the set of controls seems to be complete. However, bugfix support will be continued and also some more features, if necessary.
For example right-to-left support for all controls is still missing and is in work right now.

Tks for the observation, DexWerx, also to Krool...

Quote:

---

Originally Posted by Krool

Sure. :)


Feel free to report anything you like. Here public or private by PM.


Yes


I am developing an MSFlexGrid replacement. (with more features and with bugfixes)
But that will be in a separate project. Not linked to this set of controls.
Concerning this project, I think the set of controls seems to be complete. However, bugfix support will be continued and also some more features, if necessary.
For example right-to-left support for all controls is still missing and is in work right now.

---

Sounds good. How exactly do I download your files? When I click on the link, the forum replies with this:
Not available for the moment, due to forum policy. Please PM me to get it by another way.
Revision count will be updated here, for your reference.
I tried to PM you, but I couldn't figure out how to do that either. I have a feeling that I'm being an idiot... :( Honestly, I did not read the 29 pages in this thread. Any help would be appreciated. I will be sure to thoroughly test your work, in return for your help :) Question about the FlexGrid: Will it provide cell editing capabilities? That's the most sorely missed control from the original set. I imagine I'm not the only guy to try to dynamically fit text boxes over grid cells - ugh!

Thanks again for what you do - it's like a dream come true.

Proper Scrollbars and a Virtual Databound mode are probably more missed, than editing a flexgrid.

Also the link to download all the code - is at the bottom of the first post.

Look... I was in the same situation as you...
"PM" means "send a private message", so, in order to get the download link, you need to send a private message to Krool, asking him to pass you a download link, not by "email" but in a message delivered to your inbox inside this site.

In order to do it:

You are missing the part, where it says to PM him.
Click on his name user name "Krool"
Click "Private Message"
Type in a message to ask him to email or send you a download link.

Quote:

---

Originally Posted by DEXWERX

Proper Scrollbars and a Virtual Databound mode are probably more missed.

---

Yes.
And sorting capabilities.

Quote:

---

editing a flexgrid.

---

Yes, placing a textbox over a cell is the easiest job.
Also I'm against such comfort, as in my usage other things than just editing a cell can happen.
E.g. selecting a color or showing a popup menu...

When it comes to a flexgrid, we should wait until Krool opens a separate thread for it.
Before this thread becomes unreadable...

Karl

Quote:

---

Originally Posted by DEXWERX

Proper Scrollbars and a Virtual Databound mode are probably more missed, than editing a flexgrid.

---

Proper scrollbars. Haha, very true. It is a shame that MSHFlexGrid have problems when scrolling beyond 65,535 rows.
But enough now. As Karl77 mentioned the discussion gets off-topic.

Hi

I am trying to download these controls but not able to find the PM option to contract Krool. Is this component information available anywhere else on the .net?

Quote:

---

Originally Posted by Chris1969

Hi

I am trying to download these controls but not able to find the PM option to contract Krool. Is this component information available anywhere else on the .net?

---

Me too ! I've just registered to this forum to be able to send the PM, but that option is not listed when clicking on "Krool". I have only "View profile" and "View forum posts" available.
Can it be that the account is too "fresh" ?

Edited: After few hours (or posting this message), the option suddenly appeared. So I guess, you just have to be patient :)

Are you able to download the controls from the first post? All the controls are downloadable at the bottom the first post.
The "Demo" includes all the code.
You only need to PM Krool if you want the distributable OCX.