On Fri, Dec 3, 2010 at 00:08, aditya siram <[email protected]> wrote:
> This approach is good for reading the value of a row but what about
> changing it? It seems as though the setValue() function in the model
> is does more book-keeping.
>
Yes. If you want to set data in the model, you should be using the
setValue() method. It sounds like you're looking at the source code (good!)
so a review of the __set() method which setValue() calls shows you that it
must maintain the sorts of the various views when data is changed.
Derrell
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
