🚀 go-pugleaf

Bill,

Sorry I could not reply to your email before.  I've had email-out
problems but can use Free-Agent to post.  In any case, I still
can't see how you're getting your problem.

To convince you that it should all work.  Take a look at the circ2
or circ3 examples that come with VB3.0 Proffessional edition.

In the FireClickIn reoutine, add the following code.

char Msg[100];

wsprintf(Msg, "HTCL = %d", hctl);
MessageBox(NULL, Msg, NULL, MB_OK);

Now creae two circ2 controls.  When you click on each one, it
should show a different value.

I can only assume that you've made a user error.  Don't forget
that the VBX is a DLL and therefore shared by *all* controls using it.
So, your global variables are literally that.  If any instance needs to
reference info, make sure you set up an array and search based on
its hctl/hwnd.

Hope this helps.

Jon
----------------------------

mastbrook@duff.com (Bill Mastbrook) wrote:
>Does anyone know how the HCTL values passed to the main control
>procedure of a VBX are generated?
>Each instance of a VBX that I've created seems to be generating the
>same value for HCTL.  This is causing major problems because any
>events fired within the VBX are always fired in the instance of the
>VBX most recently created (i.e. the second of two VB applications
>started using the VBX).  I'm sure that I'm missing something very
>basic, but there doesn't seem to be any documentation on this.
>Everything I've seen says that these HCTL values are unique.  Period.
>And that's all it says.  ANY ideas of what I might be doing wrong
>would be greatly appreciated.
>Bill