Closed bergmanngabor closed 12 years ago
@szabta89 please provide some status report on this issue.
@szabta89 ninja'ed a Worksforme solution. The "Future TODO" part will be bumped to the next milestone.
FYI, wipe()
is now available. If the patterns are reloaded, there is no need to completely dispose the engine, it is enought to wipe it (keeping the base index built directly on the EMF model).
@szabta89 I'm moving this back to 0.6, let's include this improvement.
UI-related tasks delegated to #238 and #239
When (a) a model is unloaded or (b) the patterns are refreshed, the query explorer should dispose the old engine, to get rid of the old matchers which would otherwise linger in memory.
Further motivation: when re-registering a changed .eiq file, there will be lots of errors once #128 is resolved, since the old matchers are not disposed. One would have to quit & restart to resolve this. Can be reproduced using the sanitization branch.
Future TODO (after #9): instead of total disposal, use a smart wipe instead that will preserve the base index.