Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instead of creating a new tab, use current connection to do reconnection #77

Closed
wants to merge 1 commit into from

Conversation

NCTULouis
Copy link

@NCTULouis NCTULouis commented May 23, 2016

Hi all,

When click the reconnection button, the previous version will create a new tab(a new connection) to do reconnection.
Instead of doing this, we use the current connection(current tab) to do reconnection.

Fix issue #33

Thank you!

else
_this->NewCon( con->m_Site.m_Name, con->m_Site.m_URL, &con->m_Site);
con->Reconnect();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You have to follow the consistent coding style.

@NCTULouis NCTULouis changed the title Solve Reconnection Problem Instead of creating a new tab, use current connection to do reconnect Jun 6, 2016
@NCTULouis NCTULouis changed the title Instead of creating a new tab, use current connection to do reconnect Instead of creating a new tab, use current connection to do reconnection Jun 6, 2016
@@ -1759,12 +1759,11 @@ void CMainFrame::OnEmoticons(GtkMenuItem* mitem UNUSED, CMainFrame* _this)
void CMainFrame::OnReconnect(GtkMenuItem* mitem UNUSED, CMainFrame* _this)
{
CTelnetCon* con = _this->GetCurCon();

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't change the coding style.

When click the reconnect button,
the previous version will create a new tab(a new connection) to do reconnection.

Instead of doing this, we use the current connection(current tab) to do reconnection.

Fix issue pcman-bbs#33
Copy link
Contributor

@holishing holishing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tested this PR, I think this feature change will cause user to let current connect "appeared" by accident, unless you pop a dialog to confirm this action when current connection is still up.

@holishing
Copy link
Contributor

another problem of this PR is that when we "click reconnect button"(or Ctrl+R/Ctrl+Insert), the old active telnet/ssh connection is "active but hidden". This behavior will cause lots of problem, for e.g., fork too much telnet/ssh process in background. So it's not proper to accept this changes. Closed this.

@holishing holishing closed this Jun 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants