Home > Software engineering >  Pulled to maintain VB6 code, want to will be packaged into a OCX, several control of cites several *
Pulled to maintain VB6 code, want to will be packaged into a OCX, several control of cites several *

Time:10-24

A control reference olelib TLB, another control reference oleguids3. The TLB,
Terrible is that both TLB conscientiously, diligently, has realized a lot of the same interface:

IoleClientSite
IoleControlSite
IoleInPlaceActiveObject
IoleInPlaceFrame
IoleInPlaceSite
IoleInPlaceUIWindow
IoleObject
IoleWindow
IUnknown

Two TLB define the parameters of the interface, however, are completely different!
Trying to package to generate OCX, the nuptial interface, call different controls, has messed it!
For example:
A control that reference oleguids3. TLB IoleObject, IoleInPlaceActiveObject, IoleInPlaceSite, everything is all right;
B controls that reference olelib. TLB IoleObject, IoleInPlaceActiveObject, IoleInPlaceSite, everything is all right;
After packed into a project, however, seems to be one and only one IoleObject, IoleInPlaceActiveObject, IoleInPlaceSite is preferred to use, and then becomes:
A control incorrectly cited olelib TLB IoleObject, IoleInPlaceActiveObject, IoleInPlaceSite, all it is not normal.

Have no way to specify A control reference and can only reference oleguids3. The TLB zhangs interface? VB, for example, is there any grammar something like this:
Olelib: : IoleObject, olelib: : IoleInPlaceActiveObject, olelib: : IoleInPlaceSite
Oleguids3: : IoleObject, oleguids3: : IoleInPlaceActiveObject, oleguids3: : IoleInPlaceSite
That is, using "namespace" to distinguish between interface?

For help warrior, is there any way to solve the problem of the same name?

CodePudding user response:

Controls A control B compiled respectively, then the new control C reference controls to show A and B, respectively
Then apply the reference control completes the C...
  • Related