Page 2 of 2 FirstFirst 12
Results 41 to 64 of 64

Thread: [VB6] ActiveX CommonControls (Replacement of the MS common controls)

  1. #41
    New Member
    Join Date
    Oct 2018
    Posts
    7

    Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)

    Many thanks, I just tested, works perfect!!!!

  2. #42
    PowerPoster
    Join Date
    Jun 2015
    Posts
    2,224

    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!

  3. #43

    Thread Starter
    Frenzied Member
    Join Date
    Jun 2012
    Posts
    1,580

    Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)

    Quote Originally Posted by DEXWERX View Post
    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.

  4. #44
    PowerPoster
    Join Date
    Jun 2015
    Posts
    2,224

    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.

  5. #45
    New Member
    Join Date
    Sep 2019
    Posts
    8

    Question 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

  6. #46
    New Member
    Join Date
    Sep 2019
    Posts
    8

    Re: Name conflicts with existing module, project, or object library

    Quote Originally Posted by pramod9763 View Post
    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!

  7. #47
    New Member
    Join Date
    Sep 2019
    Posts
    8

    Re: Name conflicts with existing module, project, or object library

    Duplicate post

  8. #48
    New Member
    Join Date
    Sep 2019
    Posts
    8

    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!

  9. #49
    New Member
    Join Date
    Sep 2019
    Posts
    8

    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!

  10. #50
    New Member
    Join Date
    Sep 2019
    Posts
    8

    Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)

    Quote Originally Posted by pramod9763 View Post
    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!

  11. #51
    New Member
    Join Date
    Sep 2019
    Posts
    5

    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

  12. #52

    Thread Starter
    Frenzied Member
    Join Date
    Jun 2012
    Posts
    1,580

    Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)

    Quote Originally Posted by PauloFranc View Post
    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?

  13. #53
    New Member
    Join Date
    Sep 2019
    Posts
    5

    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.

  14. #54
    New Member
    Join Date
    Sep 2019
    Posts
    5

    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.

  15. #55
    New Member
    Join Date
    Jul 2017
    Posts
    4

    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.

    Name:  LinkLabel.png
Views: 388
Size:  45.1 KB

    I apologize for my poor English.
    Thanks
    Last edited by kavian; Oct 12th, 2019 at 03:46 PM.

  16. #56
    Addicted Member
    Join Date
    Sep 2015
    Posts
    181

    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 :

    Name:  notThemed.png
Views: 374
Size:  3.3 KB

    When loaded with the manifest (.manifest File or even Resource) it looks like this :

    Name:  Themed.png
Views: 371
Size:  4.0 KB

    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.

  17. #57

    Thread Starter
    Frenzied Member
    Join Date
    Jun 2012
    Posts
    1,580

    Re: LinkLabel Bug

    Quote Originally Posted by kavian View Post
    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.

    Name:  LinkLabel.png
Views: 388
Size:  45.1 KB

    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.

  18. #58
    New Member
    Join Date
    Jul 2017
    Posts
    4

    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).

    Name:  LabelW.png
Views: 352
Size:  25.1 KB

    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.

    Name:  ImageList.jpg
Views: 358
Size:  26.5 KB

  19. #59

    Thread Starter
    Frenzied Member
    Join Date
    Jun 2012
    Posts
    1,580

    Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)

    Quote Originally Posted by kavian View Post
    But two more. In 200% DPI:

    1. The label size doesn't change correctly (Autosize property is set to True).

    Name:  LabelW.png
Views: 352
Size:  25.1 KB
    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.

  20. #60
    Addicted Member
    Join Date
    Feb 2015
    Location
    Colorado USA
    Posts
    137

    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.

  21. #61

    Thread Starter
    Frenzied Member
    Join Date
    Jun 2012
    Posts
    1,580

    Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)

    Quote Originally Posted by MountainMan View Post
    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.

  22. #62
    Addicted Member
    Join Date
    Feb 2015
    Location
    Colorado USA
    Posts
    137

    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?

  23. #63

    Thread Starter
    Frenzied Member
    Join Date
    Jun 2012
    Posts
    1,580

    Re: [VB6] ActiveX CommonControls (Replacement of the MS common controls)

    Quote Originally Posted by MountainMan View Post
    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.

  24. #64
    Addicted Member
    Join Date
    Feb 2015
    Location
    Colorado USA
    Posts
    137

    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...

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width