Karl,
> I don't think it's a bug. The property to listen for
> is collapsed. If animated and you need to know when
> the animation is complete, then you can listen for
> animationState. Different properties for different
> purposes.
how could I have guessed that we disagree here <g>
The problem is, that if there is no animation because the animated property is false, client code is not notified that the collapse/expand is really finished. Whatever the property name, there must be a single property to listen to which notifies about the "really-finished", independent of whether or not the process is animated. So the options are
- either fire a collapsed only at the very end, that is when the animation has ended
- or fire a animationState ended even if there has not been an animation
- or maybe a third I can't think of?
My preference would be the first because
- more in line with the spirit of how property change notification is supposed to happen, that is only after all internal update is ready.
- one property is simpler than two :-)
CU
Jeanette
[Message sent by forum member 'kleopatra' (
fastegal@...)]
http://forums.java.net/jive/thread.jspa?messageID=367296---------------------------------------------------------------------
To unsubscribe, e-mail:
jdnc-unsubscribe@...
For additional commands, e-mail:
jdnc-help@...