
Some parts of this message have been removed.
Learn more about Nabble's
security policy.
I could be wrong here, but I'm pretty sure that the calculation receives it's notification as part of the event pipeline processing, which means that the event would arrive on the thread that initiated the list change (so locks don't really come into play). Instead of hitting a totally new thread, I was thinking more along the lines of SWT's equivalent of the event dispatch thread... (more along the line of the Timer suggestion posted earlier today).
Or toss a transaction or freezable list at it...
The thing is, these are 'live' lists, so the primary use-case would involve the calculations updating as the lists change...
- K
----------------------- Original Message -----------------------
Cc:
Date: Thu, 25 Jun 2009 12:00:17 -0700 (PDT)
Subject: Re: re: Calculations.count notfies its listeners on each change of the list during a GlazedLists.replaceAllSorted
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@...
For additional commands, e-mail:
users-help@...