I think Prof. Michael Stiber wrote: > > What I did was to _not_ call firePropertyChange() multiple times. > Instead, I concatenate all of my bean's old and new properties into two > Strings, then compare them to see if any property has changed. If so, > if call firePropertyChange() _once_, with a PropertyChangeEvent that > has a null property name.
Nope, nothing wrong with that. I think the JavaBeans spec even talks about this kind of "event coallescing." Java painting automatically works this same way. --------------------------------------------------------- Ernest Friedman-Hill Science and Engineering PSEs Phone: (925) 294-2154 Sandia National Labs FAX: (925) 294-2234 PO Box 969, MS 9012 [EMAIL PROTECTED] Livermore, CA 94550 http://herzberg.ca.sandia.gov -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
