How to refresh/redraw visuals in a mobile view

Question

I have an issue with a list properly sizing itself.  Here's my basic layout:
<s:Scroller width="100%" height="100%" >
        <!-- required b/c scroller can only handle one component -->
        <s:Group width="100%" >
            <s:layout >
                <s:VerticalLayout gap="0" />
            </s:layout>
               <!-- text blocks -->
               <s:List width="100%" id="textBlocks"
                                    dataProvider="{calendar.taskDetails}"
                                    itemRenderer="components.BBWListMultilineRenderer">
                <s:layout>
                    <s:VerticalLayout variableRowHeight="true" gap="0" horizontalAlign="justify"/>
                </s:layout>
            </s:List >
            <components:BBWHeaderSubComp label="Team Members"/>
            <s:List width="100%"
                         dataProvider="{calendar.taskLogins}" />
The issue is with how the list handles the test block area.  My custom renderer allows for multiple lines of text.  Let's assume I've got two "blocks" of text (two rows within the list each with multiple lines of text) as shown in the screen shot below.  If the first text block is larger than the second then the second block is drawn reserving the same height as the first.  As you can see below, the second block "ends" and there is still more space to make up for the difference in size.
HOWEVER, if I make an orientation change (emulator or device) then the list instantly snaps everything to the right size. 
Here is how it looks after the orientation change:
So, how do I get the visuals to update via code as I can't just tell users to switch their orientation?  Thanks!

Answer 1

take a look at this:
Diagnosis
    In the view, not all of the mandatory fields were included as key
    fields. The key of the view therefore is not unique.
System Response
    All the fields are regarded as key fields in order to guarantee that th
    key lengths are unique.
Procedure
    For views with a large number of fields, this could have a negative
    effect on the performance for the language construction described below
    In this case, all the mandatory key fields should be included in the
    view.
regards