Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!bloom-beacon!dont-send-mail-to-path-lines
From: rick@pbi.COM (Richard M. Goldstein)
Newsgroups: comp.windows.x
Subject: Re:  XView notify problem
Message-ID: <9103261232.AA13127@marvin.pbi.com>
Date: 26 Mar 91 12:32:31 GMT
Sender: tytso@athena.mit.edu (Theodore Y. Ts'o)
Organization: The Internet
Lines: 36


	    if (xv_get(file_ip->popup, FRAME_CMD_PUSHPIN_IN) == FALSE)
    		 xv_destroy_safe(file_ip->popup);

	Problem:
	--------
	If you enter a filename and hit <Return> twice in a row quickly,
	the program crashes. What happens is, after the first <Return>, the notify
	procedure gets called. After it returns, it gets called again, for the
	second <Return> ! During the second call, the program crashes when we
	check the FRAME_CMD_PUSHPIN_IN attribute.

"xv_destroy_safe()" is a *poorly* documented form of "xv_destroy()" that,
i quess, waits until it gets around to it to destroy something (as opposed
to destroying it immediately).

my experince is that i get highly unpredictable results whenever i have
tried to use it (just like you), and these problems go away as soon as
i switch to xv_destroy(). 

Give it a try.

rick

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%                                                %
% Richard M. Goldstein                           %
%                                                %
% Perfect Byte, Inc.       Phone:  (402)554-1122 %
% 7121 Cass St.            Fax:    (402)554-1938 %
% Omaha, NE 68132          email:  rick@pbi.com  %
%                                                %
% "If I knew what I was doing,                   %
%       d'ya think I'd be in Omaha?"             %
%                                                %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%