home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!decwrl!csus.edu!csusac!unify!openlook!openlook-request
- Message-ID: <ztaf3ap@openlook.Unify.Com>
- Newsgroups: comp.windows.open-look
- Distribution: world
- Date: Fri, 21 Aug 92 06:59:08 pdt
- From: mattb@ssc-vax.boeing.com (Matt Baney)
- Sender: news@Unify.Com
- Subject: Re: Notify_client numbers
- Lines: 34
-
- >From shearson!shearson.com!fgreco@uunet.UU.NET Thu Aug 20 16:09:32 1992
- >Date: Thu, 20 Aug 92 14:06:38 EDT
- >From: fgreco@fis1026.shearson.com (Frank Greco)
- >To: mattb@ssc-vax (Matt Baney)
- >Subject: Re: Notify_client numbers
- >> DOes anyone know if there are any restrictions or key numbers you
- >> shouldn't be using??
-
- > Restriction #1:
- > Avoid 0, 1, & 2
- > Restriction #2:
- > Numbers must be unique *per object*
-
- > Frank
- =-=-=-=-=-=-=-=-=-=
- Thanks for the info!! I'm trying to help some other people convert
- an OW2.0 XVIEW application to OW3.0, without any of the OW3.0
- documentation. Someone else had mentioned using xv_unique_key which
- I couldn't find anywhere in the OW2.0 documentation.
-
- My only question is what does "*per object *" mean?? Obviously if I
- create 1000 buttons I shouldn't have to use unique keys for all
- 1000, should I?? Or does that mean that I can't use the same key
- for a Frame, a Panel, and a Button?? If I'm attaching the same data
- to a Frame, Panel, and Button it would make sense to use the same
- key, but if they had to be unique that would be something I could
- live with??
-
- Thanks again for the help!!!
-
- matt,
-
-
-
-