FVS: Applied Settings

[admin]

In FVS Edit, we have these settings that can be independently ticked:
- View (Details, Thumbnails...)
- Sort Order
- Column Positions and Widths
- Column Visibility
- Line Number Visibility

I could imagine to join #3 and #4 like this:
- View (Details, Thumbnails...)
- Sort Order
- Column Layout (Positions, Widths, Visibility)
- Line Number Visibility

Or even include Line Number into Columns (I'd think this is expected):
- View (Details, Thumbnails...)
- Sort Order
- Column Layout (Positions, Widths, Visibility)

What do you think?

[j_c_hallgren]

Personally, I can't see why one would want to retain col pos/width but not their visibility or the reverse...so combining those seems perfectly reasonable.

And even though line nbr isn't really a column, I suspect most everyone would likely think so (as we've seen), so combining that for same reason as above also appears fine IMO.

[jacky]

Well, seems fair yes.

(What about what has been discussed before : that when switching tab then only column widths & pos would be restored, not visibility ? Would that be any different ?)

[admin]

Well, seems fair yes.

(What about what has been discussed before : that when switching tab then only column widths & pos would be restored, not visibility ? Would that be any different ?)

Code: Select all

  *** Tabs: Now the List column visibility is handled per-tab! Before, 
      it was global.

soon in the shops...

[TheQwerty]

From: http://www.xyplorer.com/xyfc/viewtopic. ... 839#p24839

You will have noted that I have left a lot of space in the "Applied Settings" frame.

To be honest I am thinking you should have used a tree view with check boxes. If implemented now it would prevent you from possibly having space issues later, and it would allow for a way of categorizing the settings.

I still stand by this thought.

It would have the added ability of making issues like this extremely easy to deal with.
You'd just put them all under a Columns node:
Columns
-Position
-Visibility
-Width

Then we could toggle the state for all Columns settings or individual ones.

[jacky]

It would have the added ability of making issues like this extremely easy to deal with.
You'd just put them all under a Columns node:
Columns
-Position
-Visibility
-Width

Then we could toggle the state for all Columns settings or individual ones.

I'm not sure that would change anything here, it could still be done that way with 3 checkboxes. The real question is, would there anyone interested in having some but not all of those columns settings remembered ?
It seems that either you don't want it, or you want it all : position, width & visibility.

[TheQwerty]

I am very much against combining these.

I can see cases where I might like to use different settings for each, and I think it would be stupid to remove it now, and have us go back through the hoops of requesting it later.

What is gained by combining them is very little and could be achieved through other means.

[Pagat]

I'd go for your option number 3:

Or even include Line Number into Columns (I'd think this is expected):
- View (Details, Thumbnails...)
- Sort Order
- Column Layout (Positions, Widths, Visibility)

[admin]

I am very much against combining these.

I can see cases where I might like to use different settings for each, and I think it would be stupid to remove it now, and have us go back through the hoops of requesting it later.

What is gained by combining them is very little and could be achieved through other means.

What is gained is usability. Why offer an option that's unlikely to be useful?

[TheQwerty]

I am very much against combining these.

I can see cases where I might like to use different settings for each, and I think it would be stupid to remove it now, and have us go back through the hoops of requesting it later.

What is gained by combining them is very little and could be achieved through other means.

What is gained is usability. Why offer an option that's unlikely to be useful?

And there are other ways to gain usability.

I do have a set of folders where I'd like them to remember the positions of the columns but not what is visible because it allows me to continue using the columns I currently use but place the size or modified column closer to the name than usual. Remembering the positions but not the visibility removes the annoying hassle of having to toggle the Attribute column (or others) back and forth.

[j_c_hallgren]

I do have a set of folders where I'd like them to remember the positions of the columns but not what is visible

Oh..ok, so you're wanting kind of a half-FVS then, in some cases? Where some settings are restored but others are left as is...hadn't really thought of that but now that you've explained the reasoning, I do see your point.

But, from your POV, is there any issue with combining line nbr visibility with columns?

[TheQwerty]

I do have a set of folders where I'd like them to remember the positions of the columns but not what is visible

Oh..ok, so you're wanting kind of a half-FVS then, in some cases? Where some settings are restored but others are left as is...hadn't really thought of that but now that you've explained the reasoning, I do see your point.

Is that not the whole point of allowing the user to change the settings of what's remembered?

But, from your POV, is there any issue with combining line nbr visibility with columns?

To tell you the truth I've been completely lost on all the special treatment the line number column has. I haven't followed why it's not just treated like the others. But I also haven't minded since I don't use it.

[admin]

To tell you the truth I've been completely lost on all the special treatment the line number column has. I haven't followed why it's not just treated like the others. But I also haven't minded since I don't use it.

The line number column is special:
- cannot be sorted
- cannot be moved
- cannot be clicked
- cannot be sized (I admit that this could make sense)
- it's data is not a property of a file but of the list

That's why I treated it different from all other columns.

[TheQwerty]

To tell you the truth I've been completely lost on all the special treatment the line number column has. I haven't followed why it's not just treated like the others. But I also haven't minded since I don't use it.

The line number column is special:
- cannot be sorted
- cannot be moved
- cannot be clicked
- cannot be sized (I admit that this could make sense)
- it's data is not a property of a file but of the list

That's why I treated it different from all other columns.

Yes, but what I mean is... why is it all those things, just because it's not file data?

I would think it should be tied to column visibility, but as I said, I don't use it, so I'm in no position to speak of how others should.

[admin]

Back to applied settings!

With the recent BETA v7.40.0020 you have per tab List Style (which includes Line Numbers) and per tab Column Visibility.

So, in FVS we now can offer the following applied settings:

Code: Select all

- View (Details, Thumbnails...) 
- Sort Order
- Column Layout (Positions, Widths, Visibility)
- List Style (Line Numbers, Auto-Size, Grid)

Any objections here?

Of course, I also would like to know how you like the new per tab experience? Is it maybe too much? Do you miss global settings (you still can have them now, but only when you hold Shift)?