[TIMOB-16449] Android: When touchEnabled and enabled properties are set to false the event listener added to the view stops working

Issue description

To enable and disable the buttons developer use the touchEnabled and enabled properties of the Titanium View's. Many of the buttons created this way start off in a disabled state so touchEnabled and enabled are both set to false. Clicking on the button in this state does nothing which is expected. When ready we set touchEnabled and enabled to true to enable touch events on the view and to fire the attached event listeners such as a touchstart event. In the 3.1.3.GA SDK this works perfectly however on the 3.2.0.GA SDK it appears that once those 2 properties are set to false the event listener added to the view stops working.

Test Case Steps:

Launch Bug_Testing_TC sample with the 3.1.3.GA on an android device.

Tap the Pink Rectangle -> Nothing happens, that is expected since the view is disabled.

Tap on the Blue Square -> Notice an alert pops up indicating that touchEnabled and enabled are set to true now for the pink square.

Click OK

Now Tap on the Pink Rectangle Again -> Notice that there is an alert that says PINK VIEW CLICKED!! that is expected since the view is now in an enabled and touchenabled state. Also notice that both of those states are now set to false so the view is again disabled.

Click OK

Tap on the Pink Rectangle Again -> Notice nothing happens since it is disabled. That is how we expect it to work.

Change the TiSDk to 3.2.0.GA

Launch Bug_Testing on an android device.

Tap the Pink Rectangle -> Nothing happens, that is expected since the view is disabled.

Tap on the Blue Square -> Notice an alert pops up indicating that touchEnabled and enabled are set to true now for the pink square.

Click OK

Now Tap on the Pink Rectangle Again -> Notice that Nothing happens

Repeat 10-12, notice that the pink rectangles touchstart event is not firing, it should be firing since touchEnabled and enabled are both set to true.

Tested on

This was reproduced on the Samsung Note 10.1 2014 MN: SM-P600 running Android 4.3 and Galaxy Nexus 4.1.1. It could not be reproduced this on a Saumsung Note Phone MN: SGH-I717 running Android 2.3.6.