Hi Brian,

I have a question about tabs and window-sizes.

Under size and behavior, most of my TNT files are 80x24 (AUTOMATIC). My global setting for "save on exit" is to prompt me every time. It's what I'm most comfortable with.

Say I've got 4 tabs open, different TNT files, A thru D:
- using the mouse, I resize tab A, to make it taller.
- I notice it resizes tabs B, C and D also. No problem - I'm OK with this.
- file A is flagged as being "modified". That's OK too. Perhaps I'll save it, or perhaps I won't. Depends on the weather and my mood.
- but it's also flagging files B, C and D as having been modified, which really wasn't my intention at all. When I close these tabs, I'm forced to deal with a bunch of extraneous prompts asking me if I want to save this file; a file which I had never intended to modify.

Any thoughts or suggestions?

Sincerely,

-- Dennis Carroll
The Rubicon Group

PS. I'm using version 6.01RC5.

[size=1][ August 09, 2007, 02:35 PM: Message edited by: Brian T. Pence ][/size]

I understand what you are saying. It is a rather unusual and unfortunate side-effect of having all of the terminal sessions inside of a single window. Changes to the global window size can affect not only the currently selected tab, but all of the other tabs as well.

I've got a few comments and one suggestion. I'm open to your (or anybody elses) suggestions on how to change behavior.

First, as of version 5.44, changes to the window size are not immediately applied to all tabs. For example, if you open Tabs A, B, C and then resize C and exit, only session C will be flagged as modified and prompt you to save. However, if after resizing C you open tabs A and B, all three will be flagged as modified and require you to save. Prior to version 5.44, size changes were applied to all tabs immediately.

See, B and C have no way of knowing whether changes to their size do/don't require the (modified) flag to be set. It would be difficult, if not a bit presumptuous, for Absolute to try to determine which sizing actions the user wants saved and which ones they don't. That's what we have the autosave (yes/no/prompt) option for.

My only suggestion is to set 'save on exit' to 'NO' and only save changes that you explicitly make. Not the best solution, but it will do as a workaround if those save prompts are driving you crazy.

This will be alleviated a bit in the future with the implementation of tab-groups (or workspaces). With a workspace, the screen size will likely be an attribute of the workspace rather than each individual tab. Workspaces will be implemented in the first 6.XX full release and are coming soon to a BETA near you...

Another possible change would be to ignore changes to screen size entirely when calculating the (modified) flag, at least for tabbed mode. Classic mode would remain the same. However, this may be contradictory to what some people would expect.

Well... That's the state of things at the moment, but I'm not entirely happy with how this is coded and I'm open to suggestions.

Brian

One annoying thing that comes to my attention while testing this is that the prompt that tells you that something is modified and asks you to save it gives you this message: "The current connection file has been modified..." but it does not tell you which file. It is not immediately obvious which connection file it is that you're saving.

That's got to be fixed......

Brian,

I'll follow your suggestion and change my Save on Exit to No. Aside from a mild case of cognitive dissonance, it's not a big deal.

But I must say, I like your suggestion of changing the program to "ignore changes to the screen size entirely when calculating the (modified) flag". Perhaps a new Global option. . .

-- Dennis