You are not using VB6.
I would suspect that the thinking was, if the developer/user wishes to see
objects beneath their custom control then they will want to interact with
those objects, so rather than have to pass messages to the objects beneath
they will create shaped controls in order that the other control can receive
the messages directly, thus saving valuable resources and helping to fix one
of the major complaints about VB(VB apps are too slow).
Why do you want a control that is Transparent rather than shaped?
If you just want to be able to set a MaskColor then add this property to
your usercontrol and use that color to remove from the region instead of
Color.Transparent.
"Noozer" <po********@127.0.0.1> wrote in message
news:0MbHb.838300$6C4.169526@pd7tw1no...
"Mick Doherty"
<EX***********@AND.REMOVE.SQUAREBRACKETS.[mdaudi100#ntlworld.com]> wrote
in message news:eq**************@TK2MSFTNGP10.phx.gbl... whether the image is loaded dynamically or at design time makes no
difference. If it was going to look right on a transparent background
then it quite obviously has transparent pixels. Use the OnPaint() subroutine
to create a region from the non transparent pixels of the image and apply
it to the usercontrol.
Why can't I just set a transparency mask colour the same way I did in VB6?
