Register / Login | Desktop view |
James Bucanek wrote:Clearly, you've turn on the firewall.
Leopard is confused.
I have no idea why it thinks QRecall implements any network services. This version of QRecall doesn't creating any incoming TCP sockets.
The only network communications at the moment is via the Sparkle framework that checks for version updates. Sparkle works over HTTP (port 80) and doesn't require any incoming access.
So in the end, it doesn't matter if you answer Deny or Allow, QRecall should work just fine. I'm trying to find out why Leopard thinks QRecall accepts network connections and how to get it to stop asking silly questions.
James Bucanek wrote:QRecall 1.0.0(53) resolves this issue.
Bruce Giles wrote:Confirmed.
QRecall launches *extremely* quickly now. ... (To be fair, I've been running it on an Intel Mac for only a couple of weeks, and most of that was automatic schedules, so I hadn't spent a lot of time actually launching QRecall or opening archives.)