Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VFP8 does not support themed Common Controls ActiveX ?!?
Message
De
22/04/2004 07:10:04
Arlei Silva
Chevron Oronite Brasil Ltda.
Capuava, Brésil
 
 
À
20/04/2004 13:56:39
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00896096
Message ID:
00897150
Vues:
20
>
>Openfile() and getfile() works themed on VFP8 without manifests files.
>The problem I am facing is that the ListView object does not render themed.
>And I cannot use the ListView from version 5 because this version does not
>have the new "group" feature that COMCTL32.DLL have.
>

>
>I think that there is a misunderstanding.
>
>When you get a ActiveX,
>if you select a Microsoft ... Version 5 (SP2)
>you load a COMCTL32.DLL control.
>
>This can to be load by COMCTL32.DLL v.5.82.XX ( not themed ) or COMCTL32.DLL v.6.0XXX ( themed )
>On VFP7 i try to implement a Manifest, and the result is :
>- Open VFP7 without manifest:
>- define a form
>- add a Treeview, a Progress Bar, a ListView
>- save
>- run GetFile() -> no themed
>- run the form -> no themed
>- close VFP7
>
>Now, define VFP7.exe.manifest into VFP7 directory.
>Run VFP7
>- run GetFile() -> themed
>- run the form -> themed
>
>On VFP6 you have the same behaviours.
>
>Now run VP8 without VFP8.exe.Manifest,
>- run GetFile() -> themed
>- run the form -> themed
>
>Then VFP8 support OCX Themed directly.
>
>But when you load Microsoft ... Version 6 (SPX)
>you load MSCOMCTL.OCX 6.XX.XXXX and this is not Themed.

>
>Then no solution exists until a new MSCOMCTL.OCX is released,
>or a new COMCTL32.DLL support MSCOMCTL.OCX improvements.
>
>
>* manifest
><?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
><assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
>  <description>Windows Forms Common Control manifest</description>
>  <dependency>
>    <dependentAssembly>
>      <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="X86" publicKeyToken="6595b64144ccf1df" language="*" />
>    </dependentAssembly>
>  </dependency>
></assembly>
>
Hi Fabio,

Interesting, I haven't noted that...
I wonder why MS released COMCTL32.DLL and MSCOMCTL.OCX. Maybe we can find a way to tell VFP link to COMCTL32.DLL.

But thanks for the info, now I am able to understanding...
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform