Sorry, I'm not following you. If you can be more explicit about what did and didn't work (i.e., what's in the body of the function, and how you call it), I can probably explain what's going on.
- Gordon -----Original Message----- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Jonas Windey Sent: Thursday, February 09, 2006 1:26 AM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Flex 2.0 beta TextArea question Thanks, validateNow() did the trick. Still weird though that calling the same function from a button did the event, but from code didn't work. Probably because all client-events trigger the validateNow() function automatically? -----Original Message----- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Gordon Smith Sent: donderdag 9 februari 2006 8:29 To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Flex 2.0 beta TextArea question There should be no need for callLater() or a Timer. These are workarounds from Flex 1.X that we want to banish in Flex 2. Mac Martine wrote: > I believe you will find a detailed answer in the thread > from Feb 1 with > the Subject: > [flexcoders] Scrolling a TextArea to the bottom? This thread explained that setting a property like the 'text' of a TextArea does not immediately update other properties such as maxVPosition; by default this happens latter, for performance reasons. However, you can force all properties to update immediately by calling validateNow() on a UIComponent. So if you set the text, call validateNow(), and then set the vPosition to the maxVPosition, it should scroll to the bottom. If there are problem with making this work, please file bugs. - Gordon -----Original Message----- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Manish Jethani Sent: Wednesday, February 08, 2006 12:10 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Flex 2.0 beta TextArea question On 2/8/06, Manish Jethani <[EMAIL PROTECTED]> wrote: > Okay, the problem is that the TextArea's maxVPosition is 0 even after > the text is set. The new value of maxVPosition is calculated only on > the next screen update. ..... and the solution for now is to use callLater() or a timer or something. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
