Krools Common Controls - Documentation and an Update/Compile Utility

[MountainMan]

Version 3.5 is at the bottom of the first post. It now works with VBCCRxx up through 18 (v1.8).

[smileyoufu]

Hello MountainMan!

When compiling "DriveComboDemo" (linked above), the following error is reported, please help you deal with it. Thank you!

Error Message:
FolderCompress = ErrCatch("Cannot set compression for " & Quote(anFSD.Path), -1&, True, , ErrCtrl)

[Condor3]

First, many thanks for your contributions and support.

Your update utility requires a project that was already converted to Krool's OCX.
Hexagora's (out-of-support) UNICODE OCX suite comes with a nice utility (PrjConv.exe) that allows conversion from a project that has NOT been converted yet (to Hexagora's controls -- not to Krool's controls).

Please consider adding that option to your utility? It would be a big time saver and would make the transition much easier.

[TheLeePiper]

Excellent utility, thanks. I'd like to update our code to the current VBFLXGRD18, and see that the utility only goes to 17. I see where you are using this in Set_xx_Flex, but in looking at the GUIDs in Krool's post for 18, I see four CLSIDs instead of three (which I can confirm for the prior versions). So, I'm afraid I must ask for a bit of help. Thanks, and happy new year!

[xiaoyao]

In fact, we need a general version management system.?Use the OCX version for testing. The source code is used for the final compilation.

For many of these open source controls or other libraries.
It's also good to keep multiple versions of the source code. Because the new version may have a lot of bugs, the old version is smaller.

Some versions can be used seamlessly, and some versions can not be directly compatible because they are too modified, so they need to modify a lot of things.

Better add another one. For a project with multiple controls. Userconrtol, if we only need to keep one. You can use code to automatically remove redundant other controls or modules. It would be better if we could delete all the unnecessary API declaration data structures and redundant functions.

In short, if there are four user controls in a control project, I only need to extract one of them and delete all the unnecessary code.

[TheLeePiper]

Excellent utility, thanks. I'd like to update our code to the current VBFLXGRD18, and see that the utility only goes to 17. I see where you are using this in Set_xx_Flex, but in looking at the GUIDs in Krool's post for 18, I see four CLSIDs instead of three (which I can confirm for the prior versions). So, I'm afraid I must ask for a bit of help. Thanks, and happy new year!

Just following up on this to see if you have near-term plans to add VBFLXGRD18 to your migration utility. Not pressing, just planning. Thanks!

[tmighty2]

Thank you so much! They work amazingly!

[woeoio]

Or, you can also refer to this document.

VBCCR (VB6 ActiveX Universal Control Alternative Library) supports native unicode characters
https://doc.vb6.pro/vbccr/

[ahenry]

Or, you can also refer to this document.

VBCCR (VB6 ActiveX Universal Control Alternative Library) supports native unicode characters
https://doc.vb6.pro/vbccr/

Very nice. But you should give a separate attribution / link to this thread, not just Krool's main thread, since they are separate authors.