LC/iOS Scroller Fix

[Rick Harrison]

Hi Guys,

Ok so I almost had it all solved, and then I noticed
that scrollers from other cards were "bleeding through"
to current cards since we are no longer deleting them
upon closeCard.  

The final solution I came up with is just to
set the visibility of the scroller to "false" when
closing the card.  Make it visible (true) when
re-opening the card after checking for scroller
existence.  That prevents the "bleed through" effect.

That solved everything!

Cheers,

Rick

On Jul 17, 2012, at 4:08 PM, Rick Harrison wrote:

> Hi Dixie, Jacque, etc.
> 
> Here is the fix!
> 
> Since scroller IDs are not deleted even though the
> scroller itself is deleted what needs to be done is to:
> 
> 1. First check for the existence of a scroller ID control.
> 
> 2. If it doesn't yet exist - then create it.
> 
> 3. When you closeCard do not delete the scroller (you'll need it again when you come back.)
> 
> 4. Go to your next card and come back to the original card with the scrollers.
>    (This time when the check for existence happens we don't create any new scrollers so they still work fine!)
> 
> 5. When exiting the stack - Now delete the scroller controls and clean up after things.
> 
> I tried it, and it works!
> 
> Thank you for your help!
> 
> Rick
> 
> On Jul 17, 2012, at 1:29 PM, John Dixon wrote:
> 
>> 
>> Jacque...
>> 
>> 2 cards in a stack
>> Each card has a list field using a scroller
>> 
>> The scroller will work on card 1
>> Go to the second card
>> The scroller will work on card 2
>> Go back to the first card
>> The Scroller will not scroll
>> Go to the second card
>> The scroller will not scroll
>> 
>> This has been the case for an awful long time... This is not a problem when scrolling groups on multiple cards using scrollers, only it seems when an LC list field is involved.
>> 
>> be well
>> 
>> Dixie