Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!amdahl!pccuts!acs From: acs@pccuts.pcc.amdahl.com (Tony Sumrall) Newsgroups: comp.windows.x Subject: Re: Problems with Athena Dialog Widget in R4 Message-ID: <963@pccuts.pcc.amdahl.com> Date: 12 Jan 91 02:14:27 GMT References: Reply-To: acs@pccuts.pcc.amdahl.com (Tony Sumrall) Distribution: comp Organization: Amdahl Corporation, Sunnyvale CA Lines: 24 In article curtiss@truffula.umiacs.umd.edu (Phil J. Curtiss) writes: > 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? I had the same problem with multiple text widgets in a shell widget. What I ended up doing was: * monitor FocusIn events to the shell widget and grab the focus, * monitor FocusOut events of the shell and ungrab the focus, * for each text widget, set up translations for Return and Tab which will cause it to invoke an action routine to move the focus to the "next" widget. I did all of this with the assistance of Wcl but you can certainly do it "manually". I dunno if this is a "good" way to do it but it works! >Domain: curtiss@umiacs.umd.edu Phillip Curtiss > UUCP: uunet!mimsy!curtiss UMIACS - Univ. of Maryland > Phone: +1-301-405-6744 College Park, Md 20742 -- Tony Sumrall acs@pcc.amdahl.com <=> amdahl!pcc.amdahl.com!acs [ Opinions expressed herein are the author's and should not be construed to reflect the views of Amdahl Corp. ]