> Short of switching back to a more "obvious" (in my mind) API, I think
> this problem has to be solved with lots of documentation. As I was
> trying to help solve Mathew's problem a couple days ago, I looked at the
> "changeSelection" event declaration, the fireDataEvent() method call
> (which, unfortunately, got its data from elsewhere so wasn't obvious
> that it was an array), Widget.js where the low-level _indexOf() method
> being called was comiong from, and a bunch of other places. If any of
> them had clearly stated, "This method always returns an array even if
> only one element can be selected at a time," I would have realized what
> was going on. The event, also, should be documented this way.
At least the API documentation of "getSelection" is clear about it:
"Widget[] getSelection()
Returns an array of currently selected items."
Wouldn't that be the place to look for what a selection is about?
T.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
