Hello,
Analysis (v2) was doing a project.checkAllValid() call as part of the Save
(and Save As). This was to make sure that we were not saving an invalid
project. Now of course a project should never be invalid (since the API
is supposed to guarantee that), so in some sense this was redundant. And
we discovered yesterday that this checkAllValid() was really slowing down
a save of some project. So I've now removed this as part of the Save.
Instead I have added a Validate option to the Project menu. This is a
slightly more general check in that it asks you whether or not you want to
do a "complete" checkAllValid(). I forget the details (Rasmus could say)
but the "complete" checkAllValid() will do even more and potentially
time-consuming checks (e.g. it will load stuff off disk that is not
already loaded). So generally not doing "complete" is fine.
And in general you shouldn't ever need to do this check. But at some
point we might ask you to do it if we're trying to figure out some bug or
other. Or if you observe some funny behaviour happening you could do this
check as well (but most of the time it will be something else).
Wayne
|