Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!mimsy!mimsy.umd.edu!curtiss From: curtiss@truffula.umiacs.umd.edu (Phil J. Curtiss) Newsgroups: comp.windows.x Subject: Re: Problems with Athena Dialog Widget in R4 Message-ID: Date: 10 Jan 91 20:36:24 GMT References: Sender: news@mimsy.umd.edu Distribution: comp Organization: University of Maryland Institute for Advanced Computer Studies Lines: 27 In-reply-to: curtiss@truffula.umiacs.umd.edu's message of 10 Jan 91 01:22:58 GMT After investigating this some more, it appears that the Athena Dialog widget sets the resource useStringInPlace to FALSE when it creates its AsciiSrc. It also appears that one can not change the useStringInPlace resource after an AsciiSrc has been created for the Text widget. Further, the Length resource has no effect unless the useStringInPlace resource is set to TRUE. 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? On a larger note, what I have done is to create a number of Dialog widgets and arranged them in a fill-in-the-blank style. However, while entering data into this fill-in-the-blank form, I have to keep moving the mouse pointer into the different Dialog widgets to move the keyboard focus to the Dialog in which I wish to enter data. 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? Any help is appreciated. Thanks. Phil! -- Domain: curtiss@umiacs.umd.edu Phillip Curtiss UUCP: uunet!mimsy!curtiss UMIACS - Univ. of Maryland Phone: +1-301-405-6744 College Park, Md 20742