Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!rex!ginosko!uunet!software.org!software.software.org!lai
From: lai@software.software.org (Kwo-Long Lai)
Newsgroups: comp.windows.x
Subject: Dwt and R3 Instrinsics
Keywords: Intrinsics differences
Message-ID: <356@sunny.software.org>
Date: 13 Sep 89 21:56:15 GMT
Sender: usenet@software.org
Reply-To: lai@software.software.org (Kwo-Long Lai)
Organization: Software Productivity Consortium, Herndon, Virginia
Lines: 40

Any Xpert out there familiar with the differences between 
Dwt Intrinsics(VMS5.1) and R3 Intrinsics?  (Destroy Procedure, in particular)

I have a client which runs fine on Unix(SunOS4.0.3) but it failed on VMS5.1
with the following error message:

X error event received from server: not a valid window ID
	Failed request major op code 4 X_DestroyWindow
	Failed request minor op code 0 (if applicable)
	..
	..
	..

I traced it on VMS and found the problem resided in XtDestroyWidget(in
Phase2Destroy when calling WindowObj's destroy procedure. (There is a 
loop which calls XDestroyWindow[on popup_list] in Dwt but not on R3 Intrinsics.
Is this a bug? If so, is it fixed in VMS5.2?)

The activities involved in this client are: popups a few shell widgets which have
several children(HP widget[popupMgr and menus stuff] and SPC widgets based on 
HP's manger/primitive widgets) when a particular push button is pressed.  
A callback is arranged to call 

	XtPopdown(shll_widget); 
	XtDestroyWidget(shell_widget);

when user press a particular push button.

Any hints would help.  Thanks in advance!

Kwo-Long Lai
Software Productivity Consortium
2214 Rock Hill Rd.
Herndon, VA 22070
(703) 742-7244

uucp: uunet!sunny!lai
CSNET: lai@software.org
ARPANET: lai%software.org@relay.cs.net  OR
         @relay.cs.net:lai@software.org