Oops, broken message, let me start from top.
[snip]
The window testtool then complains about as unexpected, is that same
window, "Templates and Documents". The second window it objects to is
"Untitled - OpenOffice.org Calc". I don't know why that has appeared,
unless testtool has opened it.
Let's play the testing program for a second. There's a (BAS) file the
program is reading through and at this moment it plans to test XYZ in
the let's say CALC document. So, well, it goes and first creates itself
a fresh, new file with File create new. How does the program know, the
newguinea pig file is there? It has no eyes like we do, so it goes
through the list of open tasks - pretty much the way all OS now are
built - checking, if there is something called ("having the caption
of...") "Neimenovano1" (please insert the vietnamese equivalent of
"Untitled 1" at this point). Now if the new document is NOT called (for
whatever reason)("Neimenovano 1" in the supposedly localized version but
say "Untitled ..."), the hell will freeze over, before the testing
program finds it. What we then got here, is "a failure to communicate":
a) a break in the testing routine and b) an orphan document, that - when
everything is over - is still hanging around.
Believe me, I had "Neimenovano - X" with X going from 1 to app 20 the
first time around. But it settled eventually. Of course, it could just
as well be, that the testing routine does not / can not clean up
correctly after a previous splash-down - that's why that horrible verb
kill.exe is used so much during the procedure.
From the practical point of view: if you have no errors, and there's
still some lonely unnamed file hanging around - "works for me".
Regards and sorry for the broken previous message.
smo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
