Detecting the end of validation? [message #1735062] |
Wed, 15 June 2016 07:20 |
Larry LeBron Messages: 124 Registered: October 2015 |
Senior Member |
|
|
In my xbase project, I'm doing some custom tracking of resources which have been "affected" between build cycles.
I then query this tracking in a custom extension of DerivedStateAwareResourceDescriptionManager.isAffected() which is called repeatedly during the validation cycle.
My question is, how can I detect that such a cycle is complete so that I can clear my tracking? I've tried tracing the calls to the method, but I haven't been able to find a clear hook to trace when validation or build is complete.
For example, when I edit a file in my project and then save, I see a full validation run, along with a number of calls to isAffected() for the given deltas. How can I detect when this series of calls is complete?
Thanks!
[Updated on: Wed, 15 June 2016 07:20] Report message to a moderator
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03680 seconds