Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!bierstat.scd.ucar.edu!morreale From: morreale@bierstadt.scd.ucar.edu (Peter Morreale) Newsgroups: comp.windows.x Subject: Re: Problems with Athena Dialog Widget in R4 Message-ID: <9890@ncar.ucar.edu> Date: 11 Jan 91 17:49:02 GMT References: Sender: news@ncar.ucar.edu Reply-To: morreale@bierstadt.scd.ucar.edu (Peter Morreale) Distribution: comp Organization: Scientific Computing Division / NCAR, Boulder Co. Lines: 33 In article , curtiss@truffula.umiacs.umd.edu (Phil J. Curtiss) writes: > > Does anyone know of a work around for this (outside of rewriting the > Dialog widget itself) or can confirm that this is true or not? Can't help you with this, never used a dialog. I create my forms by placing a label and text widget in a form widget. Then I manipulate the form as a whole. (which is probably exactly what a dialog is anyway...*-) > > Is there a way to make the keyboard focus move to the next Dialog > widget when a key is typed (like a return or arrow key)? Possibly by moving > the mouse to the XtN{x,y} location of the next Dialog widget? > > How do other people design entry forms and deal with this problem? > What I did was to register a translation for the associated text widgets and use "XWarpPointer()" to move the pointer upon the user hitting RETURN. I can send code upon request.... -PWM -- ------------------------------------------------------------------ Peter W. Morreale email: morreale@ncar.ucar.edu Nat'l Center for Atmos Research voice: (303) 497-1293 Scientific Computing Division Consulting Office ------------------------------------------------------------------