I created a bugreport for it with id 1474136
(http://sourceforge.net/tracker/index.php?func=detail&aid=1474136&group_id=119783&atid=684975).
Regards,
Dave
Johan Compagner wrote:
hmm that is not as easy is i thought it would be.
Can you make a bug report for this?
CheckGroup is also such
hmm that is not as easy is i thought it would be.Can you make a bug report for this?CheckGroup is also such a component that doesn't set the collection back.johan
On 4/21/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
ahh now i rember what the problem was.ModelChanging/ModelChanged is called 2 time
ahh now i rember what the problem was.ModelChanging/ModelChanged is called 2 times thenthis we do now: modelChanging(); selectedValues.clear(); selectedValues.addAll
((Collection)getConvertedInput()); modelChanged();i can't call setModelObject(selectedVal
i could just get the collection/clear it/fill it and then set it back with the same instance.i guess that is fine.johanOn 4/21/06, Dave
<[EMAIL PROTECTED]> wrote:
Thanks Johan, that did the trick. However, that behaviour did changesince snapshot 20060302.More on a philosophic note though, for all
Thanks Johan, that did the trick. However, that behaviour did change
since snapshot 20060302.
More on a philosophic note though, for all components I have used sofar,
when there is a Property-model backing those components, there are
getters and setters called to set or retrieve values into th
we don't set the values. We only do that when there is nothing returned in the getIf a collection is returned by the get that collection is filled with the values.But as far as i know we always did that, there is some code changed i think but we couldn't just
set a List in it. Because who is tellin
