Fix misbehaviour when connecting a session with an empty hostname #476
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. Use real session data instead of empty one 2. Pressing Cancel prevents connection 3. Pressing Ok acts the same as Connect 4. Remove redundant code
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a saved session has an empty hostname, connecting to such a session brings up a session edit dialog (to fill missing parameters), but this dialog is not based on the saved session data. Also, pressing
Cancelin this popped up dialog does not prevent connection, but pressingOkprevents connection.This PR makes this fixes/changes:
Cancelprevents connectionOkacts the same asConnectif hostname is not empty, otherwise it prevents connection