Programming Forums - View Single Post

Rory · Jan 14th, 2005, 9:24 PM

Because VB DLL's subclassing is "emulated" (i.e. the parent-child heirachy is not provided by windows as for a control on a form) there does not seem to be any direct method of accessing the parent's object collection, without the child process (DLL) being passed a pointer (byref collection) by a sub from the parent (as you said). I found this when trying to program ActiveXDLL Documents for IE that re-sized to the container height: because IE like many host applications does not expose its objects to clients, the only way I could simply get the window dimensions was by cheating using the GetWindowParent API.
Maybe someone else here can cast some light on the matter.

Jan 14th, 2005, 9:24 PM	#2
Rory Expert Programmer Join Date: Jan 2005 Location: London Posts: 542 Rep Power: 4	ActiveX DLL Parent Because VB DLL's subclassing is "emulated" (i.e. the parent-child heirachy is not provided by windows as for a control on a form) there does not seem to be any direct method of accessing the parent's object collection, without the child process (DLL) being passed a pointer (byref collection) by a sub from the parent (as you said). I found this when trying to program ActiveXDLL Documents for IE that re-sized to the container height: because IE like many host applications does not expose its objects to clients, the only way I could simply get the window dimensions was by cheating using the GetWindowParent API. Maybe someone else here can cast some light on the matter.