Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!unido!tub!tubopal!opal!simon From: simon@bear.UUCP (Simon Leinen) Newsgroups: comp.windows.x Subject: Re: Athena asciiStringWidget questions Message-ID: Date: 29 Nov 89 10:57:59 GMT References: <8911272047.AA05542@expo.lcs.mit.edu> Sender: news@tubopal.UUCP Organization: TU Berlin, Fachbereich 20 (Informatik) Lines: 26 In-reply-to: kit@EXPO.LCS.MIT.EDU's message of 27 Nov 89 20:47:58 GMT To: In article <8911272047.AA05542@expo.lcs.mit.edu> kit@EXPO.LCS.MIT.EDU (Chris D. Peterson) writes: [ in reply to another message (????): ] > I have an application (the Info browsing widget, for the curious) > that uses an ascii string widget to display a section of text > from a large allocated chunk of memory. The text widget's > "window" into this chunk of memory (and often the chunk of memory > itself) changes frequently. This is what I did: > ... ... you are misinterpreting the function of the length resource ... In programming my version of the Info browsing widget, I ran into the same problem, of course. The solution that worked for me is setting the buffer limit explicitly using ``XtTextSetLastPos'', like XtTextSetLastPos (w->info.text_buffer, w->info.node->length); Unfortunately, I can't seem to find the original message, So I don't know whom I am replying to. I would like to contact its poster (via EMail) if he likes, because we are seemingly implementing the same kind of widget, and I am sure I'm doing many things in a wrong way. -- Simon Leinen.