Vidalia shouldn't warn about control socket not being connected after hitting "Stop Tor"
When I start the TBB and hit "Stop Tor" a second later (because I want to configure bridges), Vidalia tells me a few seconds later: "Vidalia was unable to register for some events. Many of Vidalia's features may be unavailable. Control socket is not connected."
That message will confuse most users who don't know what an event is and why we would want to register for them.
But that message could also easily be suppressed by checking if Tor is supposed to be running or not.
The even better would be to stop the thread that tries to connect to Tor when the user hits "Stop Tor".
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information