#46 Missing Cancel Button in 2.0b1


Ok, this might be connected to the "Extranous Cancel Button" bug,
but anyway. Jason told me to also submit it to this site, so I guess
this is where to put it (deleting the thank-yous):

At this time I see no way of canceling a incorrectly typed or non-
responding connection request other than waiting for a timeout.
Changing the button into "Cancel" and/or supporting CMD-period
would be a good thing. Changing the button (either to "Cancel" or
at least disabling it) after pressing it, would be good anyway.



  • Marc Stefan Huy

    Marc Stefan Huy - 2004-08-23
    • summary: Missing Cancel Button in 2.01b --> Missing Cancel Button in 2.0b1
  • Jason Harris

    Jason Harris - 2004-08-23

    Logged In: YES

    Moving to Feature Requests.

  • Jason Harris

    Jason Harris - 2004-08-23
    • labels: 466025 -->
  • Jared McIntyre

    Jared McIntyre - 2004-08-24

    Logged In: YES

    This is actually an issue of the connection not being run either threaded
    or asynchronous. So, there isn't currently a way to stop a connect
    (which is why you get the spinning beachball as well).

  • Jim

    Jim - 2008-03-19

    Logged In: YES
    Originator: NO

    Could you ping the address first, and if there is no response then ask "There is no response to a ping, are you sure you wish to processed with this connection?"

    You could also add a Preference for each Server:

    [] Don't ping check

    Default to off


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks