Article View: comp.windows.open-look
Article #2811Re: Weird XView 3.0 XV_KEY_DATA problem
From: Stan Friesen
Date: Thu, 28 Jan 1993 16:33
Date: Thu, 28 Jan 1993 16:33
14 lines
1061 bytes
1061 bytes
In article <RICKG.93Jan25125945@irondude.eng.sun.com>, rickg@eng.sun.com (The Tankster) writes: |> |> anyway, the deal is that the XView library itself uses |> XV_KEY_DATA extensively, so you must be certain that the |> key you use is unique. the methodology for doing this is |> to obtain the key from the function xv_unique_key(void). |> Another approach, one that I often use, is to use a pointer to some application datum. This is extremely unlikely to match any key used internally by the library. -- sarima@teradata.com (formerly tdatirv!sarima) or Stanley.Friesen@ElSegundoCA.ncr.com
Technical Details
Message-ID:
<1798@tdat.teradata.COM>Path:
arc1-ca.pugleaf.net!sparky!uunet!tdat!tools3!swfReferences:
<1993Jan22.132748.50171@ccvax.ucd.ie> <RICKG.93Jan25125945@irondude.eng.sun.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!tdat!tools3!swf From: swf@tools3teradata.com (Stan Friesen) Newsgroups: comp.windows.open-look Subject: Re: Weird XView 3.0 XV_KEY_DATA problem Message-ID: <1798@tdat.teradata.COM> Date: 28 Jan 93 16:33:40 GMT References: <1993Jan22.132748.50171@ccvax.ucd.ie> <RICKG.93Jan25125945@irondude.eng.sun.com> Sender: news@tdat.teradata.COM Distribution: world Organization: NCR Teradata Database Business Unit Lines: 14