Vidalia .15/.16 don't detect already running TOR

[vidalia]

I'm categorizing this as a bug, altough the developers might've implemented this as a feature :)

Tested on Windows 2000 SP4 Server with official Vidalia bundles 0.2.0.8-alpha-0.0.14, 0.2.0.9-alpha-0.0.15, 0.2.0.12-alpha-0.0.15, 0.2.0.18-alpha-0.0.16 and 0.2.0.19-alpha-0.0.16 and the result is clear - Vidalia 0.0.15 and 0.0.16 won't detect a running instance of TOR (executed from commandline, not running as a service, altough from previous usage I do recall that it didn't work in this mode eighter) if "start TOR when Vidalia starts" is deactivated. When "Start TOR" is clicked (or "start with Vidalia" is active) then a connection is made to the running instance and everything works as expected (includig shutting down this instance). 0.0.14, on the other hand, does detect independantly started TOR, regardless whether it's made to launch TOR or not.

While not too serious it does look a little odd when Vidalia proudly claims "TOR is not running", even if T. is working, but was simply started outside Vidalia :D

[edmanm]

Vidalia doesn't constantly poll whatever control port is configured, hoping that it finds a running Tor. It only probes for a running Tor when 'Start Tor' is clicked.