Latest build thoughts...

[dcomo]

Let me first say what has been on my mind since I installed the latest build
about an hour ago... WOW! I was throughly impressed with the amount of
features (and cleanup) has gone into the latest build. Keep it going!!

I have been playing with the build for about an hour now, and besides being as
solid as ever, I have the following comments:

- There should be a keyboard shortcut to close a tab.

- On the menu that appears when right-clicking an active tab, there should be an option to open up a SSH tab, not just a sFTP tab.

- On the tab that is 'active' or the most forward, the text should be bold or a different color.
(On a really bright monitor, it is occasionally difficult to see what tab is the most forward.)

- When you type the word 'exit' within a telnet or ssh session, the tab should close.
(This may be a toggable option to keep the tab open for reconnection or to close the tab entirely.)

As I play with the program more and more, I'm sure that I will be able to report more and more.

So far, so good!!! (I'm very pleased!)

[Maureen]

Thanks for the great suggestions.

- There should be a keyboard shortcut to close a tab.

This has also been suggested in another thread. We'll look into adding a keyboard shortcut. In the meantime, you can map a key to MENU_TAB_CLOSE.

- On the menu that appears when right-clicking an active tab, there should be an option to open up a SSH tab, not just a sFTP tab.

We are considering adding "Clone" to the right-click tab menu. This would open a new tab and connect to the same session (or host for Quick Connect). For SSH2, it would use the same channel. Would this meet your needs?

- On the tab that is 'active' or the most forward, the text should be bold or a different color.
(On a really bright monitor, it is occasionally difficult to see what tab is the most forward.)

Great suggestion! I'll see what we can do.

- When you type the word 'exit' within a telnet or ssh session, the tab should close.
(This may be a toggable option to keep the tab open for reconnection or to close the tab entirely.)

I'd like to get more feedback before adding a new option. What do people expect to happen when "exit" is typed in a tabbed session?

Maureen

[dcomo]

Maureen,

Thanks for the comments. I believe I originally suggested the 'clone' tab option, and still believe that would be a great addition, however I think that you should be able to right click on a tab and be able to choose 'New SSH session'. (This functionality would be the same if you clicked on the tab icon on the toolbar.)

I'm looking forward to seeing what the other users have to say about the 'exit' option.

Looking forward to the next release!!!

[toloughlin]

I don't know how the Development team would address the 'exit' comment. Possibly :
Global Options ->
Settings ->
Exit closes tab

Sometimes I type 'exit' too many times, and exit a session - that's why the 'reconnect' feature in a tab was so important.

If exit closed the tab on me (by default, with no way around it), i'd be in a world of hurt ... I'd have to reorganize all of the tabs to make up for my fast fingers.

[MrC]

I feel that exiting a shell ("typing exit") should cause the tab to disappear if Close on Disconnect is set and the tab to remain otherwise. To me, a tab is just a simplified, compact UI entity representing an entire window. As such, it should follow the paradigm already in place when possible.

[Maureen]

That sounds reasonable to me. Does anyone disagree?

Maureen

[toloughlin]

Ah - didn't see the close on disconnect box before.
Agreed

[weaver6244]

Agree, the setting is already there, just use it.

[Maureen]

This has been implemented and will be in the next alpha.

Maureen

[richardsugg]

I saw the previous post about the active tab being a different color. I think that is an awesome idea. The tab bar seems to blend into the menu bar when you have the tool bar turned off, so anything that brings out the tab bar would be great.

Thanks,
Richard

[c0w]

I agree with richardsugg the change in this latest version is very impressive.

i will give it a good run in and see if i can find anything wrong =)


c0w

[Maureen]

Thanks for the feedback about having the active tab stand out more. This is something we'd like to do for 5.0.

Maureen

[undef]

- If you cover the SecureCRT window with other windows, redraw problems will often occur when the window gets focus again. Often the window seems blank when it's not.

- Redraw problems on resize (related to the problem mention over?). If I resize the window while using Emacs, Emacs seems to lose "orientation". The cursor is placed somewhere else on the screen than what emacs thinks.

- It's nice to see SecureFX integrated on the context menu like sFTP, but the implementation leaves a little to be desired: Is it possible to open SecureFX with the same active session as the active tab (as is the case with sFTP)? As it is now I have to enter my password one more time, so the integration is only half way there.

- Tabs: Should tab titles be [optionally] truncated in any way? I often have long window titles, and some of the tabs becomes very long with path information, load data, etc. displaying.

- I occasionally experience that port forwarding dies unexpectedly. This is not the case with 4.1. Logging out and logging in again does not restore port forwarding. I have to exit SecureCRT 5.0 completely and start fresh to make it work again.

[Maureen]

Originally Posted by undef

- If you cover the SecureCRT window with other windows, redraw problems will often occur when the window gets focus again. Often the window seems blank when it's not.

- Redraw problems on resize (related to the problem mention over?). If I resize the window while using Emacs, Emacs seems to lose "orientation". The cursor is placed somewhere else on the screen than what emacs thinks.

I'll enter these issues in our development database. We may ask some follow up questions if we have trouble reproducing these.

- It's nice to see SecureFX integrated on the context menu like sFTP, but the implementation leaves a little to be desired: Is it possible to open SecureFX with the same active session as the active tab (as is the case with sFTP)? As it is now I have to enter my password one more time, so the integration is only half way there.

In a future version of of SecureCRT and SecureFX, we'd like to support having SSH2/SFTP connections to the same session share the transport, which means reauthentication wouldn't be necessary. This might be a ways away. In the meantime, something we could possibly do is cache the password and send it to the session. I think we could only support this for SSH1, SSH2, SFTP, and possibly FTP. This would be similar to saving passwords, but they would only be in memory and would go away when the app went away. Do people feel this would be useful and would it be better than saving passwords, which is already supported?

- Tabs: Should tab titles be [optionally] truncated in any way? I often have long window titles, and some of the tabs becomes very long with path information, load data, etc. displaying.

I think we could make truncating tab titles an option. What do people think about this?

- I occasionally experience that port forwarding dies unexpectedly. This is not the case with 4.1. Logging out and logging in again does not restore port forwarding. I have to exit SecureCRT 5.0 completely and start fresh to make it work again.

This sounds like something I was seeing up until recently (and in 4.1). When you get in this state, is the shell locked?

Maureen

[undef]

Originally Posted by Maureen

This sounds like something I was seeing up until recently (and in 4.1). When you get in this state, is the shell locked?

No, the shell continues to work fine for me. I'm not quite sure, but I have the feeling that this occurs if I open a second session to the same server/profile.