Opened 13 years ago
Closed 12 years ago
#174 closed defect (fixed)
winswitch menu inconsistencies
Reported by: | pmarek | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | minor | Milestone: | 0.12 |
Component: | Client | Keywords: | |
Cc: |
Description (last modified by )
I'm using a manual "ssh -L 8022:host1:22
" to get winswitch to tunnel to another host2. Now, when that times out, winswitch doesn't seem to correctly "get" it - in the menu is the application listed as "Re-connect", although the server menu shows "Connect" (so the application entry shouldn't even be there - right?)
I think that the menu shouldn't show the application if the server is not connected.
Furthermore, «are you saying that you should not be able to connect to an app if you have lost connection to the winsiwtch server it is on? if so, yes, that should not be possible» too ;)
Change History (2)
comment:1 Changed 13 years ago by
Description: | modified (diff) |
---|---|
Milestone: | → 0.12 |
Owner: | changed from Antoine Martin to Antoine Martin |
Status: | new → accepted |
comment:2 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Note: See
TracTickets for help on using
tickets.
Should be fixed in r4957 - feel free to re-open if not.
Note: every other action was already disabled, only "re-connect" was missing the
server.is_connected()
check. Disconnect is still available, even when the server is not connected, because we generally just stop the client without needing anything else from the server (generally.. but not always...)