AB caches the updates information it retrieves, so changes to updates while
AB is running will NOT be retrieved again. However, if the initial check
times out, AB should be re-checking when the "Check for Updates" is
manually initiated again. It sounds like this is not behaving correctly, so
I'll look into it.
-Rob
At 10:46 AM 2/21/2005 -0600, you wrote:
>I think I may have found an issue. When I fired up ab3 with my laptop but
>was out of range to the wireless AP in our house, I couldn't get updates.
>No biggy.
>
>When I came back in range though and fired everything else up again (IM's,
>web browser, etc) they all worked. But the ab window I had left open
>because I was tinkering with was another issue.
>
>I clicked on the 'check for updates' button and it returned instantly with
>'could not contact the server'. I had to completely close the program and
>re-open it before it made a genuine attempt to go out and check and *gasp*
>found new things!
>
><EOL>
>Tib
---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 588-8252
Lone Wolf Development
www.wolflair.com