Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!bionet!agate!ucbvax!hplabs!hpfcdc!hpfclp!diamant From: diamant@hpfclp.SDE.HP.COM (John Diamant) Newsgroups: comp.windows.x Subject: Re: Popup Dialog box: Some Questions!! Message-ID: <9740102@hpfclp.SDE.HP.COM> Date: 21 Aug 89 06:29:55 GMT References: Organization: HP SESD, Fort Collins, CO Lines: 24 > > 1. Where are XtNinput and XtNallowShellResize described? > > Intrinsics Section 4.1.3 "ShellPart Default Values" > > Setting the input resource of the shell widget to true lets the window > manager know that your application expects to receive user keyboard and/or > mouse events. Some window managers will not pass on events to the > application unless the application has indicated that it takes input. Donna, maybe you could shed some light on a question I've had about XtNinput. I understand what it's for and why it's needed. What I'd like to know is why the default is false. It seems to me that most Xt Intrinsics applications are likely to take input in most shells and that it would have been easier to put the burden on the exceptional applications which don't take user input rather than the ones that do. Is there some reason for this default that I'm not seeing? So far, about the only application I know that doesn't take input is xclock! Thanks in advance, John Diamant Software Engineering Systems Division Hewlett-Packard Co. Internet: diamant@hpfclp.sde.hp.com Fort Collins, CO UUCP: {hplabs,hpfcla}!hpfclp!diamant