Hello Eric, i see your problem now. But i dont get the intension behind your code. Why dont you just use the mode data including the selection of the controller. That way you don't have to bother yourself with the widgets anymore and you can attach the value to your model data. I guess storing the value in the model and using the selection of the controller could have the same result because the selection of the controller always works with model items instead of widgets. Have you thought of that?
Best, Martin Am 15.05.2009 um 14:18 schrieb Dacquay, Eric: > Hi Martin, > > Here is the scenario: > > I have a select box which is populated with a list of entries > (ListItems > in this case). Every ListItem has an associated display string and > value. I am trying to create a bidirectional binding between on the > value of the selected element and the bound variable. Before the > change > in the API, I could bind the variable to the value property of the > select box. With the new API however, I can't do this anymore and I > need to supply an array containing the ListItem which I need > selected to > set the selection property. The ideal solution for me would be some > way > of automatically having this conversion from value to its associated > ListItem and vice versa for the reverse binding. > > Thanks > > Eric > > -----Original Message----- > From: Martin Wittemann [mailto:[email protected]] > Sent: Friday, May 15, 2009 3:19 AM > To: qooxdoo Development > Subject: Re: [qooxdoo-devel] Bidirectional binding with array element > > Hello Eric, > > on which widget are you using the new selection API? Could you supply > some more details on your issue, please? Perhaps I can have a > suggestion on how i would solve this after i did understand the whole > problem / context. > > Best, > Martin > > > Am 14.05.2009 um 18:40 schrieb Dacquay, Eric: > >> Hi Martin, >> >> The fix worked correctly but ever since the change to the form API, >> I've >> been having some issues with this. The original code was bound to >> the >> value property which is what was in the model. However, the new >> selection API uses the selection property which wants an array of >> Widgets instead of the value. I have thought that I might be able to >> get around this by using a converter but it seems to me like there >> might >> be a lot of almost identical code. Is this something of which you >> are >> aware? >> >> I see that the demos have been updated to use the new form API but >> there >> are no demos which do what I am trying to do. I would appreciate any >> suggestions you might have as to how best approach this. >> >> Thanks >> >> Eric >> >> -----Original Message----- >> From: Martin Wittemann [mailto:[email protected]] >> Sent: Wednesday, May 06, 2009 3:11 AM >> To: qooxdoo Development >> Subject: Re: [qooxdoo-devel] Bidirectional binding with array element >> >> Hello Eric, >> >> looks like this is a bug in the single value binding. Thanks for the >> report! >> I have opened a bug for that issue: >> http://bugzilla.qooxdoo.org/show_bug.cgi?id=2339 >> >> In fact I already have fixed it. If SourceForge is back i'll commit >> it >> to the trunk. >> >> Best, >> Martin >> >> Am 05.05.2009 um 16:46 schrieb Dacquay, Eric: >> >>> Hi Martin, >>> >>> Here is the code which is causing the problem: >>> >>> this.__objectController.addTarget(this.__fieldInstances["category"], >>> "value", "category[" + (this.getPosition()-1) + "]", true); >>> >>> If I have the same line but I don't try to do a bidirectional >>> mapping: >>> >>> this.__objectController.addTarget(this.__fieldInstances["category"], >>> "value", "category[" + (this.getPosition()-1) + "]", false); >>> >>> then I have no problems. However this also means that changes to >>> the >>> control don't update the model. Let me know if you need anything >>> else >>> but I don't think there is anything else relevant to this particular >>> issue. >>> >>> Thanks >>> >>> Eric >>> >>> -----Original Message----- >>> From: Martin Wittemann [mailto:[email protected]] >>> Sent: Tuesday, May 05, 2009 3:12 AM >>> To: qooxdoo Development >>> Subject: Re: [qooxdoo-devel] Bidirectional binding with array >>> element >>> >>> Hello Eric, >>> >>> sounds like a problem in the data binding itself. Could you pleas >>> show >>> us the code you are using. Perhaps i can find the problem in the >>> binding or some workaround for wou with the specific code piece. >>> >>> Best, >>> Martin >>> >>> >>> Am 04.05.2009 um 18:20 schrieb Dacquay, Eric: >>> >>>> Hi, >>>> >>>> So far I've been able to use the data binding feature with relative >>>> ease. However, I am having some issues with the bidirectional >>>> mapping. >>>> I have an array which I am using to bind a particular element from >>>> the >>>> array to a control. This works fine in this direction where the >>>> array >>>> element sets the control value. However, when it tries to >>>> establish >>>> the >>>> reverse binding, it complains because it cannot find: >>>> >>>> target["set" + qx.lang.String.firstUp(lastProperty)](value); >>>> >>>> This is not completely surprising as it tries to generate a method >>>> name >>>> like setArray[0](value) which does not work. Does anyone have any >>>> suggestions as to how to get around this? The list controller is >>>> not >>>> appropriate in this case since I am not binding the array itself to >>>> the >>>> control, but only a single element. >>>> >>>> Thanks >>>> >>>> Eric >>>> >> >> >> > ------------------------------------------------------------------------ > ------ >> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! >> Your >> production scanning environment may not be a perfect world - but >> thanks to >> Kodak, there's a perfect scanner to get the job done! With the NEW >> KODAK i700 >> Series Scanner you'll get full speed at 300 dpi even with all image >> processing features enabled. http://p.sf.net/sfu/kodak-com >> _______________________________________________ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> > > > ------------------------------------------------------------------------ > ------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
