![]() ![]() Mac: If a session prompted for a log file, after the file location was selected, focus did not return to the SecureCRT window.Mac: If the global option "Host key database location" was changed to a different path, the new path was not saved.Mac: The session option "Use ALT as meta key" was not always honored.Windows: If the global option "Minimize to Activator in system tray" was set and SecureCRT was closed, if "Connect" was selected from the Activator menu, the icons in the Connect dialog were not mapped to the correct actions.Windows: When switching between tiled and tabbed sessions in a maximized window, the terminal area was 24x80 instead of the full window area.SSH1/SSH2: If a session used a dynamic tunnel on port 10080 and another SSH1/SSH2 session went through the first session's SOCKS proxy and used a dynamic tunnel on port 1080, SecureCRT crashed when data went through the second tunnel.Serial: The stop bits were not logged correctly in the trace output.When enough tabs were open to require the scroll control on the tab bar, if the right-most tab was activated and renamed, the tab bar shifted to the left and the active tab was no longer visible. ![]() If a session that contained ANSI color text in the scrollback was disconnected and reconnected, the ANSI color attributes were no longer in the scrollback.If "/Serial" or "/Tapi" (Windows only) was specified on the command line, it was not honored.If the "Automate logon" items for a session were re-ordered, the changes were not saved.Opening the default session in a script caused SecureCRT to crash.In the Connect dialog, if a folder was renamed to a string that ended in one or more "." characters, the sessions in the folder were deleted. ![]()
0 Comments
Leave a Reply. |