-
Oct 29th, 2018, 04:16 AM
#41
New Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Many thanks, I just tested, works perfect!!!!
-
Dec 3rd, 2018, 02:18 PM
#42
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
I might be missing something obvious, but why does CommonDialog.cls need to use registry entries to be used in scripts vs just having the class Implement IObjectSafety?
Thanks!
-
Dec 5th, 2018, 03:19 PM
#43
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Originally Posted by DEXWERX
I might be missing something obvious, but why does CommonDialog.cls need to use registry entries to be used in scripts vs just having the class Implement IObjectSafety?
Thanks!
There is a good reason for this.
Having Implements in UserControl is no problem as only an amalgamation is exposed in the OCX.
However, using Implements in Classes exposes the interfaces directly.
Means: any one using OCX would need to install OLEGuids.tlb and that's a no-go.
-
Dec 6th, 2018, 09:46 AM
#44
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
ah! Thanks.
That's too bad that Classes are treated differently than User Controls in the OCX.
-
Sep 10th, 2019, 03:14 PM
#45
New Member
Name conflicts with existing module, project, or object library
In a new VB project everything works perfectly.
But when I try to add 'VB Common Controls Replacement 1.6 Library' in my existing project from 'Project > Components' box and click on Apply button, I get the message "Name conflicts with existing module, project, or object library". Does anyone have solution?
Last edited by pramod9763; Sep 10th, 2019 at 03:15 PM.
Reason: Grammatical error
-
Sep 11th, 2019, 09:52 AM
#46
New Member
Re: Name conflicts with existing module, project, or object library
Originally Posted by pramod9763
In a new VB project everything works perfectly.
But when I try to add 'VB Common Controls Replacement 1.6 Library' in my existing project from 'Project > Components' box and click on Apply button, I get the message "Name conflicts with existing module, project, or object library". Does anyone have solution?
The file VBCCR16. OCX was mentioned twice in the VBP file of my project that caused the problem. I deleted both mentions in the file and referenced file again. This time it loaded perfectly!
-
Sep 11th, 2019, 09:53 AM
#47
New Member
Re: Name conflicts with existing module, project, or object library
-
Sep 14th, 2019, 04:37 PM
#48
New Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
The ComboBoxW control allows to edit at Property Style= 0. What if I don't want the user to edit in the control. I just want him to select item from drop-down list. I tried using property Locked = True. But then ComboBoxW only let the user to Drop the items but it does not let him select the item.
Please suggest a solution!
-
Sep 14th, 2019, 04:38 PM
#49
New Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
The ComboBoxW control allows to edit at Property Style= 0. What if I don't want the user to edit in the control. I just want him to select item from drop-down list. I tried using property Locked = True. But then ComboBoxW only let the user to Drop the items. However, it does not let him select the item.
Please suggest a solution!
-
Sep 14th, 2019, 04:52 PM
#50
New Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Originally Posted by pramod9763
The ComboBoxW control allows to edit at Property Style= 0. What if I don't want the user to edit in the control. I just want him to select item from drop-down list. I tried using property Locked = True. But then ComboBoxW only let the user to Drop the items. However, it does not let him select the item.
Please suggest a solution!
I should have used Property Style = 3.
That solved the problem!
-
Sep 19th, 2019, 11:20 AM
#51
New Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Hello,
Is there any thing similar to VisualStyles that can be done to the aspect of the forms?
Thanks
-
Oct 7th, 2019, 01:31 PM
#52
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Originally Posted by PauloFranc
Hello,
Is there any thing similar to VisualStyles that can be done to the aspect of the forms?
Thanks
Forms are automatically visual styled. Or what do you mean exactly?
-
Oct 7th, 2019, 03:33 PM
#53
New Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Ok, thanks.
I was just wondering about the borders and format of the corners for example.
-
Oct 7th, 2019, 03:34 PM
#54
New Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Ok, thanks.
I was just wondering it I should do something about the borders and format of the corners for example.
-
Oct 12th, 2019, 12:02 PM
#55
Junior Member
LinkLabel Bug
Hi Krool,
first, thanks for your great work.
I encountered a bug when using your ActiveX Component.
LinkLabel control with transparent back style, works great in normal DPI size (96 DPI - 100%). But, in 192 DIP (200%), it completely cluttered and the background color becomes black. By changing the Transparent Property to False, everything works well again.
I apologize for my poor English.
Thanks
Last edited by kavian; Oct 12th, 2019 at 03:46 PM.
-
Oct 13th, 2019, 12:56 AM
#56
Addicted Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
I have a problem with the DTPicker control!
It works ok as long as the application is loaded without manifest file (not themed) like this :
When loaded with the manifest (.manifest File or even Resource) it looks like this :
The format is reversed which ruins the display and causes a lot of confusion.
My Windows regional setting are:
Format: Arabic Egypt
Location: Egypt
When I change the Format to, say, English (United States) it works ok.
I tried to change the system date format from code before initializing the theme but it does not work.
Although Arabic is Right To Left language but numbers, dates and time is left to right (well, Date can be used both ways but not Time)
Even if we typed in Hindu numbers all is left to right except date unless we type in Arabic numbers it is Left to Right for All:
Hindu date and Time:
٢٠١٩/١٠/١٣ (all is right to left) or ١٣/١٠/٢٠١٩ (all is left to right but its ok as long as years are in YYYY format)
٠٧:٤٢ ص (hours are left and minutes are right) in the themed screen shot time is 42 as hours and 7 as minutes which is wrong!
Arabic numbers:
13/10/2019 (all left to right)
07:42 ص (all left to right)
Any suggestions?
Last edited by labmany; Oct 13th, 2019 at 02:32 AM.
-
Oct 13th, 2019, 11:20 AM
#57
Re: LinkLabel Bug
Originally Posted by kavian
Hi Krool,
first, thanks for your great work.
I encountered a bug when using your ActiveX Component.
LinkLabel control with transparent back style, works great in normal DPI size (96 DPI - 100%). But, in 192 DIP (200%), it completely cluttered and the background color becomes black. By changing the Transparent Property to False, everything works well again.
I apologize for my poor English.
Thanks
Please try LinkLabel1.Refresh for the meantime. It should resolve it. I'm looking for a fix which will makes the .Refresh not needed.
EDIT: OCX has been updated. It should now work even without extra .Refresh.
Last edited by Krool; Oct 13th, 2019 at 12:34 PM.
-
Oct 23rd, 2019, 03:52 AM
#58
Junior Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Hi Krool, Thanks for update. now the control is working properly.
But two more. In 200% DPI:
1. The label size doesn't change correctly (Autosize property is set to True).
2. The icon size of any controls that use the ImageList, doesn't change correctly. Also the Toolbar control, isn't DPI-aware. These bugs are not present in the Std-EXE version.
-
Oct 27th, 2019, 05:02 AM
#59
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Originally Posted by kavian
But two more. In 200% DPI:
1. The label size doesn't change correctly (Autosize property is set to True).
AutoSize for LabelW at design time is only a 1 time Autosizing, because the behavior is then that the size can be freely changed afterwards..
It works when design time DPI is same as run time DPI.
However, to be sure in all cases it is better to apply an .AutoSize = True during Form_Load again.
The intrinsic VB.Label has the same behavior. So I don't consider this as a bug, but rather a feature.
-
Jan 15th, 2020, 01:53 AM
#60
Hyperactive Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Krool,
I have 3 questions regarding using the OCX version of the controls.
1 - What modules, if any, of the Std-EXE version need to be included when we use the OCX version? You have 3 modules int eh Std-EXE version that are general to all of the forms, Common.bas, Startup.bas and VisualStyles.bas. Are any of these needed to use the OCX version?
2 - In the Std-EXE version demo, at the start of each of the forms is code to call SetupVisualStylesFixes which resides int he aforementioned VisualStyles.bas module. Do we need to do this at the start of any/all our forms to get theming and visual styles or is that done automatically in the OCX version?
3 - If these are no specials subs to run at startup using the OCX version, then is there still the requirement that the program starts from Sub Main instead of going to a form? If so, what initialization code should we call before going to a form?
As a general comment, it might be nice to have a simple sample using the OCX version which would help us understand what we need to do besides side-by-side to get it to work with modern themes etc. If you want, I could cook up your Std-EXE sample for use with the OCX if you can help me understand the start-up things like in my questions above.
Thanks.
-
Jan 22nd, 2020, 04:59 PM
#61
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Originally Posted by MountainMan
Krool,
I have 3 questions regarding using the OCX version of the controls.
1 - What modules, if any, of the Std-EXE version need to be included when we use the OCX version? You have 3 modules int eh Std-EXE version that are general to all of the forms, Common.bas, Startup.bas and VisualStyles.bas. Are any of these needed to use the OCX version?
2 - In the Std-EXE version demo, at the start of each of the forms is code to call SetupVisualStylesFixes which resides int he aforementioned VisualStyles.bas module. Do we need to do this at the start of any/all our forms to get theming and visual styles or is that done automatically in the OCX version?
3 - If these are no specials subs to run at startup using the OCX version, then is there still the requirement that the program starts from Sub Main instead of going to a form? If so, what initialization code should we call before going to a form?
As a general comment, it might be nice to have a simple sample using the OCX version which would help us understand what we need to do besides side-by-side to get it to work with modern themes etc. If you want, I could cook up your Std-EXE sample for use with the OCX if you can help me understand the start-up things like in my questions above.
Thanks.
Using VBCCR16.OCX is no different than using COMCTL32.OCX. Again: No difference.
What do you do to get theming? You make a manifest file
What do you do to use COMCTL32.OCX regfree ? You make a manifest file, same for VBCCR16.OCX
VisualStyles.bas is only helping by fixing some issues with the theming, mostly for the intrinsic VB.Controls.
-
Jul 22nd, 2020, 02:25 AM
#62
Hyperactive Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
In the StdEXE version of these controls you added the VListBox on 6/23/2020 control and on 7/24/2020 you added the VListBox control. When I use the current latest version here (v1.6.126) of the OCX version I do not see these controls available for use. Have you not included them yet? If so, does that mean they won't be available until version 1.7?
-
Jul 22nd, 2020, 01:37 PM
#63
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Originally Posted by MountainMan
In the StdEXE version of these controls you added the VListBox on 6/23/2020 control and on 7/24/2020 you added the VListBox control. When I use the current latest version here (v1.6.126) of the OCX version I do not see these controls available for use. Have you not included them yet? If so, does that mean they won't be available until version 1.7?
Yes. 1.7 will be released soon and then all will be updated.
-
Jul 22nd, 2020, 03:37 PM
#64
Hyperactive Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Thanks. I am just about to release an update tot he compile utility and wanted to make sure I wasn't doing something dumb...
-
Aug 19th, 2020, 12:12 PM
#65
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Update released.
VBCCR17.OCX
-
Aug 19th, 2020, 10:12 PM
#66
Hyperactive Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
In your new OCX there are 34 controls but 64 GUID's. I am trying to get the updater fixed for this new version but I have a question about those GUID's that don't have control names associated with them. In previous versions, the order of the GUID's and controls were all in the same order but this time you changed them a lot. My basic question is can these GUID's not associated with a control name who up as such in someone's project? If not I can just upgrade controls from earlier versions to 1.7 and basically not pay attention to these GUID's but if they can show up in someone's code then I have to relate each one to the previous unnamed GUID's and I might need some help learning which ones go with which controls.
-
Aug 20th, 2020, 04:05 AM
#67
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Originally Posted by MountainMan
In your new OCX there are 34 controls but 64 GUID's. I am trying to get the updater fixed for this new version but I have a question about those GUID's that don't have control names associated with them. In previous versions, the order of the GUID's and controls were all in the same order but this time you changed them a lot. My basic question is can these GUID's not associated with a control name who up as such in someone's project? If not I can just upgrade controls from earlier versions to 1.7 and basically not pay attention to these GUID's but if they can show up in someone's code then I have to relate each one to the previous unnamed GUID's and I might need some help learning which ones go with which controls.
The GUID's are now sorted alphabetically. (beside CommonDialog class kept on top)
All unnamed GUID's belong to their "upper" control.
Example: the GUID C3853FC8-E7D9-43D4-88AA-4DF0651E66B1 is unnamed, but the prior GUID is stated VBCCR17.Animation. So their belong to each other.
And so on.
Code:
clsid="{068A3E97-D041-4248-AEEE-56B09D8D037C}" progid="VBCCR17.CommonDialog" />
clsid="{9602627B-40A9-4638-B4CD-39A365F85432}" progid="VBCCR17.Animation" />
clsid="{C3853FC8-E7D9-43D4-88AA-4DF0651E66B1}" />
clsid="{5F2AB905-9655-4A13-9F7E-433EDFF185F2}" progid="VBCCR17.CheckBoxW" />
clsid="{14959488-6EF6-4323-A7CB-7165F32D8CC2}" progid="VBCCR17.ComboBoxW" />
clsid="{A6C631D4-7449-44DC-9AD2-D86357554975}" progid="VBCCR17.CommandButtonW" />
clsid="{5B07381D-39B9-40BF-9EE3-AF0636276897}" progid="VBCCR17.CommandLink" />
clsid="{8AC46A3E-727E-48EC-A063-4FC42CB744F4}" />
clsid="{03F663A5-EF57-4F73-BDAF-31C5E673B739}" progid="VBCCR17.CoolBar" />
clsid="{1908EE8D-074B-4C73-A650-02BE9202D3A2}" />
clsid="{4BFD0894-5927-4DF9-B65C-19632904D2BC}" />
clsid="{ED9B663D-A5CA-4D5F-A35E-F337009BA0B9}" progid="VBCCR17.DTPicker" />
clsid="{B73EA339-27D1-46CF-9FE9-D166C46248DD}" />
clsid="{67E6130D-31EA-4462-8B7B-35C8D00B8878}" progid="VBCCR17.FontCombo" />
clsid="{2FDC9106-3494-4747-8FB2-61D379DD0A82}" progid="VBCCR17.FrameW" />
clsid="{3760E97F-F505-4A7E-A7B9-A5D4D475832E}" progid="VBCCR17.HotKey" />
clsid="{277DDA80-4A98-4736-A23D-A1C200E791A6}" progid="VBCCR17.ImageCombo" />
clsid="{04A8661E-B343-4EBC-AB7C-3910DFBE1B18}" />
clsid="{6993750D-0041-47C0-BF0F-7F82F68949C1}" progid="VBCCR17.ImageList" />
clsid="{6C56E631-FF75-42B2-B4B7-8B4031550584}" />
clsid="{CB5DEA21-63B5-480B-BEFE-5EE5314722C5}" />
clsid="{D717FCAC-DDEF-4CF3-BA30-FDEFC64C097B}" progid="VBCCR17.IPAddress" />
clsid="{3F8EFA5D-6EE2-4243-B181-997284B86913}" />
clsid="{E3C54ADB-EED1-4D03-9F7B-4D42EA7BFC7D}" progid="VBCCR17.LabelW" />
clsid="{9F562C7A-EC4B-4E02-85D2-CE42203EC994}" progid="VBCCR17.LinkLabel" />
clsid="{63904521-756C-4F8B-BFB8-4944B436C4BA}" />
clsid="{3E22EA9C-D403-4C3B-B5DA-96DD4AC8EC93}" progid="VBCCR17.ListBoxW" />
clsid="{172DFD6D-064E-4E31-9558-89096C3B2C07}" progid="VBCCR17.ListView" />
clsid="{34FC2451-FF36-4A5C-953F-6C5C79A1700E}" />
clsid="{0A1CF8E6-385A-4627-ABF7-87ADA3C542B0}" />
clsid="{0EBECF21-3927-421A-B70E-138694D86EB2}" />
clsid="{9AE1DA41-2B6E-495E-9403-69DB3C6B4D7A}" progid="VBCCR17.MCIWnd" />
clsid="{45A07E72-1CBF-43BB-804D-816A071DF623}" progid="VBCCR17.MonthView" />
clsid="{03DDF33B-3D29-4888-8EDC-70C02072CEEA}" />
clsid="{E7C8AA1C-5D9D-4E69-AA90-B271F3CD418B}" progid="VBCCR17.OptionButtonW" />
clsid="{8D5766F1-B256-46AF-8A55-4DEA235F71F1}" progid="VBCCR17.Pager" />
clsid="{8F839938-51C3-4558-916F-E4ED967E88EC}" />
clsid="{7331C00D-E101-4E1F-AE65-D56EB37263FD}" progid="VBCCR17.ProgressBar" />
clsid="{479EC666-5FF8-43C8-A2E6-D53853D0138C}" />
clsid="{71C2F1C5-7282-468B-9159-1BC4B7D3C90F}" progid="VBCCR17.RichTextBox" />
clsid="{D8707683-3AB9-41E2-B923-B32F3449A288}" />
clsid="{FE7B5DA6-4D26-41C1-B5E1-3FD2C26638CB}" progid="VBCCR17.Slider" />
clsid="{515D25BE-D6CF-4C3E-96EE-79DBDA944B34}" />
clsid="{A4822523-E1D8-4802-912F-6825CBCF7EA2}" />
clsid="{BE90171C-60AC-404E-91CD-48C36B7EB5D0}" progid="VBCCR17.SpinBox" />
clsid="{C5366161-D0E7-49F6-95F3-788BA9600617}" />
clsid="{73DEDEDA-B899-4B59-883C-C8F66C2C7A9B}" progid="VBCCR17.StatusBar" />
clsid="{560F8AC8-028D-4F88-BEEC-67FFEE357466}" />
clsid="{7C2A3132-2779-4D2B-B687-052B994E0602}" />
clsid="{FD6C1D42-591A-4D59-873B-3825E0F9A48F}" progid="VBCCR17.SysInfo" />
clsid="{5A449BC4-90AA-47FA-B2B5-D8B555EF91EF}" progid="VBCCR17.TabStrip" />
clsid="{00EC79F7-8382-4217-9943-3CC8A0B251A6}" />
clsid="{269A7AD4-CFE9-4655-A070-C1D3CC1AE00F}" />
clsid="{C08B5E24-A816-480C-A0D9-52173F420F3F}" progid="VBCCR17.TextBoxW" />
clsid="{B700EB90-2F14-4776-969D-40726357016A}" />
clsid="{BD34E876-94B4-4A0E-A9CC-CC64D0580F08}" progid="VBCCR17.ToolBar" />
clsid="{E441BD93-5F11-492E-A22C-C3F36DC07716}" />
clsid="{7476271E-C33F-4A1A-84ED-A4373AA7B9C6}" />
clsid="{4A1E23DB-0330-4BF9-8CB1-8DED96FF0A72}" progid="VBCCR17.TreeView" />
clsid="{B2B4454B-913E-40E4-8FE2-77B9BB082924}" />
clsid="{9C41E0AA-3074-497D-A552-FD9E2720AA36}" progid="VBCCR17.UpDown" />
clsid="{5AFF51F6-4021-4B90-82D3-F59A5F34CCB6}" />
clsid="{2FA19598-CAE7-4257-8892-6EE4DA1158E8}" progid="VBCCR17.VirtualCombo" />
clsid="{F1457E04-22FC-4D37-B4C1-E5126DF9DBDC}" progid="VBCCR17.VListBox" />
-
Aug 20th, 2020, 08:36 AM
#68
Hyperactive Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Thanks. Tha's what I thought you did. How about the earlier ones? For example, in VBCCR16.OCX the 4th one is {F37CEF7D-65C4-4F00-9874-B698A08EB948} and it is after UpDown but before TreeView. Was it part of UpDown?
-
Aug 20th, 2020, 08:52 AM
#69
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Originally Posted by MountainMan
Thanks. Tha's what I thought you did. How about the earlier ones? For example, in VBCCR16.OCX the 4th one is {F37CEF7D-65C4-4F00-9874-B698A08EB948} and it is after UpDown but before TreeView. Was it part of UpDown?
Don't know for VBCCR16. It wasn't sorted..
For VBCCR16 I would check with RegEdit.. For instance {F37CEF7D-65C4-4F00-9874-B698A08EB948} returns in RegEdit (CTRL+F find method) VBCCR16.PPTreeViewGeneral. So it relates to TreeView.
-
Aug 20th, 2020, 08:55 AM
#70
Hyperactive Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
It looks to me that in prior versions you had the associated GUID's before the named ones. For example, in prior versions, CommonDialog was listed first and there was always an unnamed one then UpDown so it never was clear to me whether the unnamed one went with DommonDialog or UpDown. It didn't matter because your order was consistent across versions so I could match between versions. Now that you have re-ordered the list it is important. CommonDialog is still listed first but now the 2nd entry is not an unnamed one but is Animation so it looks like CommonDialog doesn't have an unnamed one with it. So it seems that prior versions had the unnamed ones were associated with the following named one, not the prior named one. I am sorry for cluttering up the thread with this. I think it only means something to you and me (part of the upgrade utility) so if you want we can take the discussion to PM's.
-
Aug 20th, 2020, 09:13 AM
#71
Hyperactive Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Never mind. I am going through the registry as you suggested and it appears there is no rhyme or reason for the older ones, before or after so Ill just comb through the registry and manually match them in my program. Thanks.
-
Aug 26th, 2020, 02:41 AM
#72
Addicted Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Hey Krool
If a project already uses VBCCR16 ActiveX, what is the update process for switching to VBCCR17?
-
Nov 6th, 2020, 11:30 AM
#73
New Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Originally Posted by OldClock
Hey Krool
If a project already uses VBCCR16 ActiveX, what is the update process for switching to VBCCR17?
I have same issue .. seems all object need to recreated if wanted to use latest. @Krool can you elaborate on this ?
-
Nov 17th, 2020, 11:09 AM
#74
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Originally Posted by stanner_austin
I have same issue .. seems all object need to recreated if wanted to use latest. @Krool can you elaborate on this ?
You may use the Documentation and Update/Compile Utility from MountainMan to upgrade all references in all Forms from VBCCR16 to VBCCR17.
-
Jan 10th, 2021, 01:00 PM
#75
Addicted Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
I thought to start 2021 in a good way by upgrading my application to full Unicode support, using Krools Common Controls Replacement. Had noticed them before, but never had time to investigate / implement. Now I’ve read all the threads, and it all sounds great! To keep things simple, I started with the OCX (version 1.7), thinking that the StdExe option might be something for a later phase, if needed at all.
As my app has 65 forms, some simple, some with many controls on them, I wondered if there isn’t a quick way to replace the "old controls" with the new versions by simply editing the frm-files in a text-editor? Or is it really a matter of rolling up the sleeves, and going through each form replacing each individual control manually?
-
Jan 11th, 2021, 09:26 AM
#76
Junior Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Hi Erwin69, yes that is exactly how I did it, editing the frm files by hand. You have to edit all the control types / classes in the "header" section of the frm, but also you will have to change classes and enums elsewhere in code, typically event handlers.
Also there are some cases where data will be stored for the original in the FRX files and that will have to be manually reset. I recall taking screenshots of things like imagelists so that I could rebuild them later.
IIRC I studied the codebase first to try & ID all the cases I had, and then used regex search & replace for a lot of it.
I would recommend working in stages, keeping backups along the way, etc. Good luck!
-
Jan 31st, 2021, 10:13 AM
#77
Addicted Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Thanks Dave. It's an interesting exercise, and your suggestion to work in stages most definitely is an important one. I had hoped for a quick search and replace across all frm-files using Notepad++, but that was thinking too simple...
On top of it there is the additional challenge of converting the external text-files that contain translations in among others Korean and Russian into Unicode text-files, and then properly read and process them. (They now only work if the code page is set to those languages.)
Quite a few challenges ahead...
-
Feb 6th, 2021, 04:56 PM
#78
Addicted Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
OK, making some progress, but ran into something today:
In a frame I have 3 shapes, that visually show the status of something, traffic light style. Since shapes don't have events, I'm using the mousedown event of the frame to capture the X-, and Y-coordindates, and check those versus the position of the shapes.
This worked fine with the original Frame object, but with the FrameW object, the X and Y that the event returns, don't correspond with the coordinates of the shapes. My guess is that a different scaling is used?
Any advice is appreciated!
-
Feb 7th, 2021, 05:55 AM
#79
New Member
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
hi there
I downloaded the VBCCR17.OCX.rar.zip file and removed the zip extension, but got an error when I tried to extract it
can anyone help me?
-
Feb 9th, 2021, 08:17 AM
#80
Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)
Originally Posted by hmnader
hi there
I downloaded the VBCCR17.OCX.rar.zip file and removed the zip extension, but got an error when I tried to extract it
can anyone help me?
You can download it from Github also. (Without it being archived)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|