Hey,
sorry for the late answer. Just came across this post and read that you would
need some feedback on here from us.
We are aware of that and know that it could be confusing because in the non
virtual widgets, the changeSelection event is the only one you need.
Nevertheless, we took that decision because we had to break with at least one
expectation. On the one hand, we name every change event of a property
change<name> but on the other hand it does not map with the feature known from
non virtual widget. Additionally to that, the data binding controller which are
in the data namespace for the old widgets do have the same behavior like the
current virtual select box (which was the main reason to do so).
Removing the event is not an option because if you want to use data binding,
you might need that event in case someone sets a whole new array as selection.
Propagating the change of the array to the changeSelection event of the
widget... also not a good idea because it would also break the compatibility of
the binding and would cause a lot of traffic. And with all that arguments, we
should keep in mind that its not only for the virtual select box, its also for
all data binding controllers and all other virtual widgets like tree and,
combobox and list.
In the end, its a tradeoff I'm not really happy with myself because I know it
could be confusing but considering all the circumstances, I think its the best
solution we currently have.
Regards,
Martin
Am 01.11.2011 um 13:26 schrieb Benjamin Dreux:
> I have no scrit answer to that, since as you are, I'm just user of qooxdoo.
> The 1und1 team could clearly make a decision about this.
> As you said, i don't see a cas for the use of the changeSelection
> event, except at the creation of the widget.
>
> Regards
>
> Le 31 octobre 2011 09:06, omrihar <omri...@gmail.com> a écrit :
>> Hi Benjamin,
>>
>> thanks for your reply. As you can see in the playground - I know that it is
>> possible to use .getSelection().addListener("change",...). I also realize
>> that strictly speaking, there is no bug since the property "Selection" does
>> not change when the selection content changes (because it simply points to
>> the array whose content does change).
>> However, I think that it does not make much sense conceptually to have a
>> changeSelection event which is only fired when the pointer to the Selection
>> array changes (which I guess does not happen very often, if at all). Since
>> this behavior is different from the other (non-virtual) widgets I think it
>> is worth contemplating. Perhaps the change event from the Selection Array
>> should bubble up and trigger a "changeSelection" event on the
>> VirtualSelectBox, as this is what one would expect it to do (unless one
>> knows the implementation details of the widgets).
>>
>> Best wishes,
>> Omri
>>
>> --
>> View this message in context:
>> http://qooxdoo.678.n2.nabble.com/Possible-bug-with-VirtualSelectBox-changeSelection-event-not-working-tp6947645p6948088.html
>> Sent from the qooxdoo mailing list archive at Nabble.com.
>>
>> ------------------------------------------------------------------------------
>> Get your Android app more play: Bring it to the BlackBerry PlayBook
>> in minutes. BlackBerry App World™ now supports Android™ Apps
>> for the BlackBerry® PlayBook™. Discover just how easy and simple
>> it is! http://p.sf.net/sfu/android-dev2dev
>> _______________________________________________
>> qooxdoo-devel mailing list
>> qooxdoo-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>
>
>
> --
> Benjamin Dreux
> Analyste-Programmeur
> Chaire de logiciel libre-Finance Social et solidaire
> UQAM
> Montréal
>
> ------------------------------------------------------------------------------
> RSA® Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
