Hi Peter,
[edited]
I'm sorry for the confusion.
I found there was another function call that caused the 10 second delay.
Validate.NotExists() indeed works as expected.
Thanks,
Eyal
Search found 4 matches
- Thu Jul 29, 2010 7:37 am
- Forum: Bug Reports
- Topic: Validate.NotExists timeout too long
- Replies: 6
- Views: 3756
- Wed Jul 28, 2010 2:45 pm
- Forum: Bug Reports
- Topic: Validate.NotExists timeout too long
- Replies: 6
- Views: 3756
Re: Validate.NotExists timeout too long
No, still no change.sdaly wrote:What about? Validate.NotExists(repo.fldAddEditDST.winNewDSTInfo.AbsolutePath,200);
- Wed Jul 28, 2010 2:28 pm
- Forum: Bug Reports
- Topic: Validate.NotExists timeout too long
- Replies: 6
- Views: 3756
Re: Validate.NotExists timeout too long
sdaly wrote:This works for me....
validate.NotExists(path,200)
Thanks.
I tried that and the behaviour is the same. The timeout is still 10 seconds, eventhough the output is:
Element for path '/form[...]' does not exist (No element found for path '/form[...']' within 200ms.).
- Wed Jul 28, 2010 1:56 pm
- Forum: Bug Reports
- Topic: Validate.NotExists timeout too long
- Replies: 6
- Views: 3756
Validate.NotExists timeout too long
I'm trying to shorten the timeout when looking for non existing windows from 10 seconds to 2 seconds. I set SearchTimeout of 'winNewDSTInfo' to be 2000ms, and used the following code: Validate.NotExists(repo.fldAddEditDST.winNewDSTInfo.Path,repo.fldAddEditDST.winNewDSTInfo.SearchTimeout,"DTS window ...