Just for anyone that is interested, I try to sum it up:
1. The setters do return "The unmodified incoming value" [1]
1.1. They do so also in the "build version"[2].
2. They throw an assertion error and return void in case of a type/range
mismatch.
2.1. They don't throw an assertion error in the "build version" in case of a
type/range mismatch.
3. The multiple property setter method "set({Map})" does not return anything.
3.1. It throws an assertion error for 'the first'[3] key-value pair in case of
a type/range mismatch.
3.2. All 'previous' (see [3] on this as well) map key-value pairs will be
stored in case of a type/range mismatch on a 'following' one.
Cheers,
Peter
------
[1] See documentation of each setPROPERTY() method in the API viewer
(generated via 'generate api')
[2] "source version": generated via 'generate source' or 'generate source-all'
"build version" : generated via 'generate build'
[3] careful: What map-property will be "first" is not 100% predictable, so
don't rely on any order. Maps are _unordered_ key-value storages!
On 2010-07-02 10:24 MartinWittemann wrote:
> Hey,
> oh yes, seems to be right. I didn't use that because its a setter where I
> don't expect anything to be returned.
> Regards,
> Martin
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
