A customer reported that they were trying to have 2 switches be\nlinked to each other so that when one value changed the other\nswitch changed. The below code, when run, causes many many events\nto fire when the window is opened. This was run on the iphone, sdk\n4.0.2 & 1.4.1
\n
var win = Titanium.UI.currentWindow;
\n
var sw1= Titanium.UI.createSwitch({ value:false,\nleft:215,top:100});
\nwin.add(sw1);
\n
var sw2= Titanium.UI.createSwitch({ value:true,\nleft:215,top:200});
\nwin.add(sw2);
\n
sw1.addEventListener('change',function(e){
\n
\nsw2.value = !sw2.value;\n
\n
});
\n
sw2.addEventListener('change',function(e){
\n
\nsw1.value = !sw1.value;\n
\n
});
The problem is that this causes an infinite loop, REGARDLESS of\nwhen the event is triggered. Switch value 'change' events are fired\nwhenever the value is set, and this includes creating a switch with\na 'value' property.
\n
Every time a switch was flicked for this window, the following\nwould happen, regardless of when:
\n
s1 -> s2 -> s1 -> s2 -> s1 ->...
\n
The customer needs additional logic in their code to ensure that\nno switch is flipped twice by this requirement.
This happens when just loading the window, without touching a\nswitch. So you are saying that just by having 2 switches with\nlisteners to each other, and not touching either one, this will\nhappen?
I can see how the listeners would cause an infinite loop, but\nwhen a control is created and a value is set, IMO, should not fire\nthe change event. This is backwards from what most expect.