[ALOY-353] Titanium proxies built from markup should support all Backbone eventing
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | Medium |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2012-11-05T15:28:17.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Alloy 0.3.2, 2012 Sprint 22 |
| Components | Runtime |
| Labels | notable |
| Reporter | Tony Lukasavage |
| Assignee | Unknown |
| Created | 2012-10-30T19:35:43.000+0000 |
| Updated | 2018-03-07T22:25:58.000+0000 |
Description
Titanium proxies should support the on(), off(), and trigger() Backbone eventing functions. These functions should wire seamlessly into the eventing functions built in to Titanium proxies, meaning:
* on === addEventListener
* off === removeEventListener
* trigger === fireEvent
In this ticket, a bug was also resolved that was firing event listeners set with *on()* multiple times. The wiring between Backbone eventing and Titanium proxy eventing has been fixed and on(), off(), and trigger() behave as expected when used by proxies.