If you check the current demo of WebApp.Net you'll see that scrolling position is kept when you go back so that you return to the previous selection Don't know about the hang you mention but this problem doesn't occured in WAn
On May 23, 11:23 pm, davidroe <[EMAIL PROTECTED]> wrote: > Both iUI and WebApp.net seem to handle this in a similar fashion, or > rather they both seem to suffer the same problem: when a screen slides > in from the side, the active screen is first scrolled to the top. If > the user has selected a list item that exists further down the screen, > that whole screen is re-scrolled back to the top, the selected item > becomes no longer visible and the whole experience is not as smooth as > one would hope. > > What do other developers think about this? Are they willing to let it > slide? Sorry, bad joke. Has anyone taken a stab at a solution? Is > anyone being asked to come up with a solution? Are you pushing back? > > I personally have already wasted a lot of time trying to come up with > a way of handling this and, although I got the math right, the > experience becomes slow and awkward because of the amount of > processing required, not to mention (my early 1.0.2 version of) Safari > intermittently hangs in the middle of the setScroll loop, depending on > the amount of off-screen content (probably that buffered zone that > doesn't get rendered immediately). > > /dave --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
