From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: *
X-Spam-Status: No, score=1.3 required=5.0 tests=BAYES_00,INVALID_MSGID,
	MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,2c48d6c9a7b6d52b
X-Google-Attributes: gid103376,public
From: jboulais@my-deja.com
Subject: Re: Generic Package & Win32
Date: 2000/03/27
Message-ID: <8bocfn$l5i$1@nnrp1.deja.com>#1/1
X-Deja-AN: 603065052
References: <8bntfs$3pv$1@nnrp1.deja.com>
X-Http-Proxy: 1.0 x21.deja.com:80 (Squid/1.1.22) for client 140.76.187.210
Organization: Deja.com - Before you buy.
X-Article-Creation-Date: Mon Mar 27 19:23:56 2000 GMT
X-MyDeja-Info: XMYDJUIDjboulais
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.08 [en] (WinNT; I ;Nav)
Date: 2000-03-27T00:00:00+00:00
List-Id: <comp.lang.ada>

Actually, for anyone that cares, I found the answer. I was using the
same class name for each instantiation (internal to the generic). There
is probably a better solution that allows me to retain that common
class name, but I fixed the problem by creating a unique class name
based on the caption that is supplied when you instantiate the generic.
Apparently once I registered one instance of the generic with that
class name, all of the windows messages sent to any of the
instantiations were going to the first instantiation. I'd be interested
in hearing from anyone with other possible solutions.
Jeffrey Boulais


Sent via Deja.com http://www.deja.com/
Before you buy.