Results 1 to 11 of 11

Thread: No licence for old versions?

  1. Mar 7th, 2001, 12:24 PM #1
    Jhd.Honza
    Jhd.Honza is offline

    Thread Starter
    Hyperactive Member
    Join Date
    Apr 1999
    Location
    Prague, Czech Republic
    Posts
    350

    No licence for old controls?

    How is it possible I can normally use Common Controls version 6.0, but for version 5.0 the licence is not found?

    Can I force VB to use the old version?

    I have VB version 5!!
    (running on W2K)
    Last edited by Jhd.Honza; Mar 7th, 2001 at 04:28 PM.
    Reply With Quote Reply With Quote
  2. Mar 7th, 2001, 01:42 PM #2
    Zaf Khan
    Zaf Khan is offline
    Fanatic Member
    Join Date
    Jan 1999
    Location
    UK
    Posts
    554
    Maybe because you have liscence for ver 5.0 and when using ver 6.0 your control is UPGRADED....


    DocZaf
    {;->
    Reply With Quote Reply With Quote
  3. Mar 7th, 2001, 04:26 PM #3
    Jhd.Honza
    Jhd.Honza is offline

    Thread Starter
    Hyperactive Member
    Join Date
    Apr 1999
    Location
    Prague, Czech Republic
    Posts
    350
    Ok. So no chance to use the old version?
    Reply With Quote Reply With Quote
  4. Mar 7th, 2001, 06:19 PM #4
    Zaf Khan
    Zaf Khan is offline
    Fanatic Member
    Join Date
    Jan 1999
    Location
    UK
    Posts
    554
    Sorry, That was just a guess, I may be wrong....

    DocZaf
    {;->
    Reply With Quote Reply With Quote
  6. Mar 7th, 2001, 06:34 PM #5
    Arcom
    Arcom is offline
    Addicted Member
    Join Date
    Aug 2000
    Location
    Croatia
    Posts
    200
    When you upgrade your control(s) they overwrite the old versions with the new ones, so...

    BTW: Why do you need to use the older control?
    Reply With Quote Reply With Quote
  7. Mar 8th, 2001, 08:21 AM #6
    Jhd.Honza
    Jhd.Honza is offline

    Thread Starter
    Hyperactive Member
    Join Date
    Apr 1999
    Location
    Prague, Czech Republic
    Posts
    350


    In developing the VB6 common controls, the VB development team stopped using comctl32.dll as its basis for functionality. Instead, the team took the unprecedented steps of removing the VB OCX dependency upon comctl32.dll, and opted (wrongly in this author's view) to rewrite the functionality available in comctl32.dll v4.72 as the new VB6 mscomctl.ocx. This redesigned OCX is not dependant on the original Windows' common control dll, and no longer relies on it for any functionality. And in creating the OCX, its implementation has been tweaked to the point where some methods that do work against the VB5 common control implementation (which uses comctl32.dll) no longer function as expected using the VB6 common control (mscomctl.ocx).
    That's the reason...
    Reply With Quote Reply With Quote
  8. Mar 8th, 2001, 08:33 AM #7
    Guest
    Why use the .ocx at all? I always use the comctl32.dll ...

    in other words, use the GetOpenFilename and GetSaveFilename API functions.

    Gerco.
    Reply With Quote Reply With Quote
  9. Mar 8th, 2001, 01:31 PM #8
    Jhd.Honza
    Jhd.Honza is offline

    Thread Starter
    Hyperactive Member
    Join Date
    Apr 1999
    Location
    Prague, Czech Republic
    Posts
    350
    Emm... that's nice Gero, but I need TreeView...

    Yes, I have the code how to create it through API, but I mean it is too complicated (for simple app) and the reason why I am trying to use old version will not be solved.
    Reply With Quote Reply With Quote
  11. Mar 8th, 2001, 03:03 PM #9
    Guest
    Sorry, I thought you meant comdlg32.ocx and .dll...

    I kinda misread the name... What has changed in the treeview since version 5 then? What do you need from the treeview?

    I use the new version treeview all the time, and have found no odd behaviour...

    Gerco.
    Reply With Quote Reply With Quote
  12. Mar 8th, 2001, 03:17 PM #10
    Jhd.Honza
    Jhd.Honza is offline

    Thread Starter
    Hyperactive Member
    Join Date
    Apr 1999
    Location
    Prague, Czech Republic
    Posts
    350
    The whole challenge is to change background and text color of the TreeView.
    I found I can use TVM_SETBKCOLOR and TVM_SETTEXTCOLOR messages, but I also found this didn't work properly in 6.0 version (see the quotation).

    Any other ideas?
    Reply With Quote Reply With Quote
  13. Mar 8th, 2001, 03:25 PM #11
    Guest
    Hmm, didn't try... can't you just set the properties for that? Or doesn't the treeview have backcolor and textcolor props?
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

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