Titanium JIRA Archive
Appcelerator Community (AC)

[AC-1928] Alloy ListView TextField in Item Template with events causing a runtime error

GitHub Issuen/a
TypeBug
Priorityn/a
StatusClosed
ResolutionFixed
Resolution Date2014-01-15T18:47:42.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsAlloy
Labelsn/a
ReporterDarren Haligas
AssigneeTony Lukasavage
Created2014-01-15T18:30:16.000+0000
Updated2016-03-08T07:40:51.000+0000

Description

When adding a TextField in the ListView ItemTemplate that has events extra code is created that causes a runtime error.
"'undefined' is not an object (evaluating '$.__views.number.addEventListener')";
<ListView id="transForm" defaultItemTemplate="pickerTpl" style="Titanium.UI.iPhone.ListViewStyle.GROUPED">
            <Templates>
                <ItemTemplate name="pickerTpl">
                    <ImageView bindId="icon" id="icon"/>
                    <Label bindId="label" id="label"/>
                </ItemTemplate>
                <ItemTemplate name="numberTpl">
                    <ImageView bindId="icon" id="icon"/>
                    <TextField bindId="number" id="number" onChange="numberChange" />
                </ItemTemplate>
            </Templates>
            <ListSection id="numSection">
                <ListItem template="numberTpl" number:hintText="-" />
            </ListSection>
        </ListView>

Attachments

FileDateSize
app.zip2014-01-15T18:30:16.000+00003381028

Comments

  1. Tony Lukasavage 2014-01-15

    I just tried this with alloy 1.3.1-beta3 and got no runtime error. Can you please try that version and tell me whether you still get an error?
       [sudo] npm install -g alloy@1.3.1-beta3
       
  2. Darren Haligas 2014-01-15

    That works. When is that dropping?
  3. Tony Lukasavage 2014-01-15

    Already resolved in 1.3.1 beta
  4. Shak Hossain 2014-01-17

    Darren, Is there anything else you need on this issue? If not, can we close this ticket? Thanks, Shak
  5. Darren Haligas 2014-01-20

    Shak, I will have to wait for Alloy 1.3.1 for the fix. Currently i have a workaround for now using 1.3.0.

JSON Source