OCX container 'border'

[Haakon Birkeland]

The approximate grid sized white canvas/border around the OCX control in the OCX container. Does it have to be there during design time, or are there any way to get rid of it. It's "fine" once running the compiled EXE.. But then it has to be wrongly sized in design-time. Seems like we can't have it both ways..?

[TechSupport]

Nope, can't have it both ways in this case. We need the border around the OCX in order to allow us to resize or move the OCX. There are just too many different types of OCX's. I tried to subclass the OCX to catch the mouse messages for resize, etc... both it is not successful in all cases. The container approach is a compromise.

[Jose Roca]

Better don't try, Paul. There ase also windowless ActiveX controls

[Haakon Birkeland]

So it's got to be that wide.. Guess we can't have it all (yet)..