Hey,
Oops, I should have thought to try a standard control first (sorry, it was the
end of a long day…)
No problem, at least I already know the topic we are talking about. ;)
My widget implements ISingleSelection and I found that because ISingleSelection
and IMultiSelection controls are handled differently, if I use a SelectBox
instead of a List then the SelectBox will always keep the n-th selection; my
demo is http://tinyurl.com/2uz5hz4.
That should be a restriction of the select box, not the binding nor the
interface, as you also said!
This kind of makes sense for SelectBox because it does not have the concept of
an empty selection, but IMHO the ISingleSelection interface implies that an
empty selection is valid for some types of control, in that it doesn't
specifically exclude empty selections and it has a resetSelection() method.
Could MSelection._updateSelection call target.resetSelection() if there is
nothing to be selected?
Well, I am currently not that into that mixin. But if it does not reset the
selection, it is sure a bug. So could you please open up a report and i will
take care of it some time?
Best,
Martin
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
