Hello, Yes, in version 0.7.2 value for ListItem can be only a string because appropriate check was added to property declaration in ListItem class. It is not noticed in release notes and may lead to some hard-to-detect problems in existent applications (as it was in our case).
In our application we have class that is subclass of ListItem. In this class we redefined matchesValueExact to allow search by arbitrary values. As a result of new check in ListItem we had to hack our class to save its functionality. In particular, we had to add getValue and setValue methods in class and obviously this is not good. It would be useful to have abstract parent class, for example BaseListItem, for list items. It would allow to create and implement list items with arbitrary values and arbitrary search rules. Best wishes, Denis -- View this message in context: http://www.nabble.com/Problem-whith-findValueExact-tf4267749.html#a12798337 Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
