What do you want to know? In theory, showing/hiding groups could perform better than doing a full card transition because the region to be updated is smaller than the card. You may need to play with enabling or disabling accleratedRendering if performance is poor.
Remember that you can also restrict card transitions to a defined rect, which is key for any UI that includes fixed controls (i.e. navbar, toolbar). You don't want your fixed controls scrolling out of view during a transition. Unfortunately, we can't (yet?) combine multiple visual effects to achieve the combination of scroll+dissolve that takes place on iOS, and sometimes Android. This is sorely needed to provide native-looking user experience. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 5/17/13 12:44 PM, "Mike Kerner" <[email protected]> wrote: >Before I spend all weekend playing with this, has anybody done any >experiments on showing and hiding groups on cards instead of doing >transitions between cards on mobile? I'm specifically wondering about >folks using MobGUI or tmTools, which I would imagine require more >resources >than projects that don't use those skinning tools. > >The main thing that I'm wondering about is transition speed. Some of the >card transitions on mobile are...pokey. > >-- >On the first day, God created the heavens and the Earth >On the second day, God created the oceans. >On the third day, God put the animals on hold for a few hours, > and did a little diving. >And God said, "This is good." >_______________________________________________ >use-livecode mailing list >[email protected] >Please visit this url to subscribe, unsubscribe and manage your >subscription preferences: >http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
