Good point. Thanks a bunch Alex. I thought I have to do comparsions only after itemEditEnd as it's the only point dataProvider will be updated. Compare direct value of that item and do other tasks manually could be solid and effective, better than waiting a final dataProvider update.
George Alex Harui wrote: > itemEditEnd will shut down the edit session and starting up a new one > will take time so you probably don't want to do that. But if you do, > you'll need 2.0.1 hotfix2 or 3.0 and set editeditemposition=null > > > > I would extend NS and watch the VALUE_COMMIT event and do your > comparisons then. > > > > ________________________________ > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of George > Sent: Wednesday, November 21, 2007 2:26 PM > To: [email protected] > Subject: [flexcoders] How could force itemEditEnd event manually when > using NumericStepper as itemRenderer? > > > > Hi guys, > > I got exhausted today struggling with NumericStepper. In DG I have a > NumericStepper component used as > itemRender (editable). > > I tried two kinds of NS components. > 1. extended NS. > 2. use VBox to contain a NS inside. > > What I want is, each time when user click NS, I need an itemEditEnd > event at once and comparing original values of DG, so user could get > immediate response it changed or not. But I found the NS has quite weird > > behavior. > > My experiment is to force focus moving outside from current itemRender > instance when NS vlaue changed. I got this method worked for Combox, > Checkbox renderers, but not NS this time. NS has a TextField, it never > lose its focus. So itemEditEnd event not dispatched at _first _ change, > but _second_ value change on NS? itemEditEnd event fired! > > Any help appreciated. > George >
