hid.lst is removed from sources
References: <[email protected]>
 <[email protected]>
In-Reply-To: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Mathias Bauer wrote:
> Thorsten Bosbach wrote:
> 
>> - If the package 'TestTool' got selected during installation of OOo,
>>    the file hid.lst is found in basis-program directory.
>>    TestTool recognizes this and copies it to the default location
>>    (testautomation/global/hid/).
> 
> Can you explain why the testtool does not load the hid.lst from the
> "program" folder? If the problem is the pain to fiddle out the path: we
> could add a function to the automation libary that returns the path to
> hid.lst for the office being automated. I assume that the hid.lst is not
> needed to have a short communication about that.
> 
> I think copying files should be avoided where possible as it always
> bears the risk that the files get out of sync.

This is only the last fallback, to try to run a test;
Main goal is to use the packages, provided by Maho, which contain
the hid.lst at the correct location and where no additional action is 
needed.

The other way would be to just stop at the moment where the hid.lst is 
missing and telling the user to change the path to the hid-directory in 
  the VCL TestTool settings.

I tried to be nice and give it a last chance:
During runtime I can not change the path to the hid-directory, so if I 
find it somewhere else, I need to copy it to the expected location, the 
current instance of VCL TestTool expects it.

I compute the location of the hid.lst during runtime, that's no problem.

A further action would be to make the hid-directory configureable during 
runtime, but this needs a new VCL TestTool release, which we handle very 
conservative. So it might be adjusted this way in the next VCL TestTool 
release.

cheers
Thorsten

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to