Hi, Klaus. Sorry, as usual I was out. I tried your code that works, of course. But, it was a problem of my test only (the fact that I tried to scroll having not inserted a new line in the scrollview). If things were like in that my example, clearly there is (perhaps) no sense in scrolling down without a new line inserted.(. but ..who knows..). Anyway let's fix that scrolling works, according the fact that the ScrollView contains a new line and the ScrollToNow is called inside a delayed call. As a "counter-example", see the attached app, with a direct call. You can see the "mess" that happens, just calling directly ScrollToNow.. (Hope there is not an error of mine, again, but I just commented the two CallDelayed, substituting them with direct calls). First "Amazing thing" is that if somebody hopes that issuing a ScrollToNow call, after filling a ScrollView, will show a the ScrollView at the end position, he will be disappointed. As a matter of fact the initial appearance of the ScrollView is without any scroll. Then see what happens adding lines...
Thanks for your patience. Your suggestions resolved, and hopefully somebody else can benefit from our discussion. It remains the doubt about the fact that perhaps these "hidden" mechanisms requesting a delayed call could involve other functions... Thanks again.
Thanks for your patience. Your suggestions resolved, and hopefully somebody else can benefit from our discussion. It remains the doubt about the fact that perhaps these "hidden" mechanisms requesting a delayed call could involve other functions... Thanks again.
