Support Team wrote:
The only difference with 3.X is that if all parents folders of an item have "Use Cache" set to false, Ranorex does not use the repository structure, but immediately searches the absolute path of the item using the "Effective Timeout" for that item, that is the sum of the item's timeout and the timeout of its parent folders.
Why was this change made? I had been told to set the cache to false in order to deal with some other problems we were having a while back. I don't remember exactly which thing it fixed. Are you telling me if I set the folder cache settings to true that the timeouts will be taken from the repo item itself rather than combining that timeout with the timeout of the parent folder/form?
Support Team wrote:
I'm curious, what is the use case of setting such a low timeout? Do you want Ranorex to stop searching after 2 seconds?
Yes I do want it to quit searching for the item after 2 seconds. It will either be there immediately or it won't be there at all in my case. I don't want it to slow down the test by sitting there waiting 30 seconds every time this function gets called. I also don't want to set the parent items search timeout down as it is used for other items that won't necessarily be there immediately. My only solution has been to move it to the top.
I don't just use Ranorex for GUI testing I actually use it to enter data on one GUI and then transmit data over ethernet or serial connections to another system which I am also logged into with another GUI and I validate that the data was received and that it matches the data that was sent.
The case I need this for is when I delete an item I want to make sure it purged within a specific timeout across the wire. If it wasn't purged I want to log and error and attempt to purge it again. The problem is if it works properly which it almost always does I'm sitting there for whatever the parent items timeout is waiting to move onto the next step, in this case it is an error if it exists.