dojo - Distinguishing between onChange events
During an upgrade from dojo 1.1.1 to 1.6.1, I found that dijit.byId('someWidget').set('value','someNewValue')
, was causing the onChange event to fire for the input.
To prevent onChange from firing when the .set method is used, a third parameter priorityChange is used. Setting priorityChange to false prevents the onChange event from firing.
The updated code is: dijit.byId('someWidget').set('value','someNewValue',false)
A sed command to update the code. In this case the setValue or attr(’value’) calls had already been translated to set:
sed --in-place "s/\.set\ *([\"|']value[\"|']\,\ *\([^\)]*\))/.set('value',\1,false)/g" js/code.js
Print article | This entry was posted by elvis on 09/14/11 at 03:54:00 pm . Follow any responses to this post through RSS 2.0. |