Xref: utzoo comp.os.vms:16047 comp.windows.x:11672
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!purdue!decwrl!asente
From: asente@decwrl.dec.com (Paul Asente)
Newsgroups: comp.os.vms,comp.windows.x
Subject: Re: Unresolved routines in HP Widget set
Message-ID: <1599@bacchus.dec.com>
Date: 20 Jul 89 17:10:58 GMT
References: <2619@quanta.eng.ohio-state.edu>
Organization: DEC Western Software Lab
Lines: 13

In article <2619@quanta.eng.ohio-state.edu> DAVISM@kcgl1.eng.ohio-state.edu (Michael T. Davis) writes:
>	I'm attempting to port the HP Widget set to DECwindows under VMS.
>I have almost everything compiled except for two references in the code:
>_XtPopup (which is probably some form of macro from the Xt that DEC chose
>not to include in the Dwt (DECwindows Toolkit))

Nope.  _XtPopup is an internal routine in the intrinsics, not an exported
interface.  HP deserves a slap on the wrist for using it in their widget
set.  As it happens, on Unix you can't hide procedures like this from
applications, but on VMS you can (and we rightly did).

	-paul asente
	    asente@decwrl.dec.com	decwrl!asente