Full Screen

[toloughlin]

I found out that switching from a 'maximized' (practically full screen) window to 'full screen' (alt+enter) triggers tabs to register activity ... is this how it's supposed to work? It happens both ways (to and from full screen).
Kinda caught me off guard.

I thought, if I went from a smaller window ... 25x80, and then to full screen - the lines wouldn't wrap at 80 cols, and continue across the screen to 132, denoting a change in the screen state.

However, nothing goes even remotely close to the end.

[bocks]

Hi toloughlin,

From the behavior that you are describing, it sounds like you have the "Retain size and font" option enabled in your sessions options, under the category Terminal / Emulation.

Can you verify this?

In order to have the number of columns used change to accommodate the increased screen size, you may what to enable the "Synchronize view to size" option instead.

Another factor that can affect the number of columns available is the Global option "Maximum Columns" located in the category Terminal / Appearance. This option defines that maximum number of logical columns that can be displayed by all sessions. If this option is set to 80, then no matter how big the screen size gets, the maximum number of columns available is still eighty.

The traffic that you see is the server being notified of the change in screen dimension. This is sent when the screen is resized. I believe that this happens even if the logical number of rows and columns stays the same.

Do you see the same behavior with the "Synchronize view to size" option enabled?

Thanks,

-bocks

[Maureen]

I found out that switching from a 'maximized' (practically full screen) window to 'full screen' (alt+enter) triggers tabs to register activity ... is this how it's supposed to work? It happens both ways (to and from full screen).
Kinda caught me off guard.This is the expected behavior, but not necessarily the desired behavior. When the window is resized, SecureCRT sends a message to the remote side and a message gets sent back, which is what's triggering the activity notification. Our programmers looked at this during the beta cycle and it's not easy for SecureCRT to distinguish between these types of messages and other messages that really do indicate activity, so we weren't able to fix it. It is currently in our development database, but I don't know whether or not we're going to be able to do address this issue.

Maureen

[toloughlin]

From the behavior that you are describing, it sounds like you have the "Retain size and font" option enabled in your sessions options, under the category Terminal / Emulation.
Can you verify this?
No, I have Sync. View to Size

Another factor that can affect the number of columns available is the Global option "Maximum Columns" located in the category Terminal / Appearance. This option defines that maximum number of logical columns that can be displayed by all sessions. If this option is set to 80, then no matter how big the screen size gets, the maximum number of columns available is still eighty.
I don't think that is correct:
25x80 normal:
# stty -a
speed 38400 baud; rows 25; columns 80; line = 0;
--
25x80 initial, then 'maximized'
# stty -a
speed 38400 baud; rows 56; columns 132; line = 0;
--
25x80 maximized then full screen:
# stty -a
speed 38400 baud; rows 66; columns 132; line = 0;
[/QUOTE]


The traffic that you see is the server being notified of the change in screen dimension. This is sent when the screen is resized. I believe that this happens even if the logical number of rows and columns stays the same.

OK - makes sense.


It is currently in our development database, but I don't know whether or not we're going to be able to do address this issue.

No problem - just checking.