Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!pasteur!helios.ee.lbl.gov!ucsd!ucsdhub!hp-sdd!hp-pcd!hpcvlx!gabe
From: gabe@hpcvlx.cv.hp.com (Gabe Begeddov)
Newsgroups: comp.windows.x
Subject: Re: XtSetKeyboardFocus
Message-ID: <100920163@hpcvlx.cv.hp.com>
Date: 9 Feb 90 19:12:37 GMT
References: <7898@pt.cs.cmu.edu>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 52


   / hpcvlx:comp.windows.x / moore@cs.cmu.edu (Dale Moore) / 12:34 pm  Feb  8, 1990 /

   This bug appears to be present in the X11-R4beta release.

Try it with the R4 release. The keyboard logic has undergone large changes.
   
   Below is a program that should cause the error.
   
   Am I halucinating? Or is it really a bug?  Does anyone care?
   Does anyone want a fix?  Does anyone have a fix?

If it's really a reasonable bug rather than the place an already sick program
happens to expire, then I'm sure *someone* cares. Now to some comments on the
program. I am not familiar with the Xaw widgets (especially after some of the
dramatic improvements that Chris Peterson et al have made for R4) but it 
seems like your logic for the dialog creation is way off. You are creating the 
dialog (which is a form subclass) as another child of your box. Do you want it
there or in a seperate popup? Either way it should be managed (via XtManageChild) 
rather than realized (which should usually be reserved for the roots of widget
hierarchies). If you still see strange behavior then send a bug report to:

	xbugs@expo.lcs.mit.edu 

there's a form in the /doc (?) directory of the X11 distribution.


   static void button_callback (w, client_addr, client_data)
   {
       dialog = XtCreateWidget (
   	"dialog",
   	dialogWidgetClass,
   	XtParent (w),
   	args,
   	num);
   
>       XtRealizeWidget (dialog);
>       XtMapWidget (dialog);

use     XtManageChild(dialog); 

   ----------
   
Gabe Beged-Dov   
Iterface Technology Operation   
Hewlett-Packard