Loosing listener after popping

[mikerudra]

Hi, here is what I have, am not sure is my mistake or a bug:

1. create a main app with controller and view etc.
2. add a container, auto-created from a reference in the main controller
3. push this container at a certain moment and listening to one of its button tap events

what happens
1. the reference is set to autocreate, so I push it to the navigationview, works good, the container pops, the event of the button tap is sent to the controller
2. I pop out this container
3. I push it again and the event is not catched anymore in the controller, however, I added a local event to the button, and AFTER the first push the event is triggered in the local button events.

I want to be able to catch this event form the controller all the times as normal. I get the feeling somewhere the autocreate / autodestroy clear my listeners or something. Please help.
Thanks.

[mikerudra]

Check out the attachment.

[jjohnston]

Hi, thanks for posting. The .xds file alone doesn't hold the data needed to open your project, could you please send us an archive of your entire project directory so we can open it? Thanks.

[mikerudra]

Here is the archive with my example. Thanks guys! (btw... I could not add it in .tgz format. What kind of limitation is that?) :o)

[jjohnston]

Thanks, I see the issue you are talking about. This doesn't seem to be particular to using Designer, so I've moved it into the Touch 2.x forum so that the Touch team can take a look at your example.

[mikerudra]

Thanks, I will follow it there... I mean here

[mitchellsimoens]

I recommend against the usage of id. There are much better ways to resolve components using ComponentQuery. For instance replace id with action : 'test' on your button and updating the controller to use 'button[action=test] it will work no problems.

[Jamie Avins]

We'll take a look at it.

[mikerudra]

Here is my workaround for this too:

- I actually reassigned the tap events to the buttons just after I used them the first time and I am keep assigning them after every use... lame, I know, but efficient, at least it works.
- You should check your "single" property, looks to me it triggers even tho is not set... just thinking loud here...