Remove now superfluous feature

[admin]

Menu View | Columns:
"Define Current Column Setup as Default" and
"Restore Column Setup from Default"

Does anybody use this at all???

By any means it will be even less necessary when FSS is there.

Any objections against removing it?

[jacky]

uh, what?

Does anybody use this at all???

Yes, I do. Granted I usually don't have to, but on occasions I've found myself with columns not the way I want them to be (for some reason), and I liked to only have to use one command to restore everything.

Now I don't know what/how FSS will work, and if you say it'll take care of it then I'm fine of course, but I'd like to still have a way to "restore column setup", since I've had to use that a few times in the past.

[ivan]

I use this. Currently, I see this as a XY's equivalent of WE's Apply To Folders so I like to be able to use this default command.

[j_c_hallgren]

Does anybody use this at all???
Any objections against removing it?

Yes, I use it...ok, rarely, but when I need it, I depend on it!
I've used mainly when I want to try an alternative look and then get it back to my standard.
If there will be a FSS equivalent, then it could be swapped over at that time.

[Pagat]

i stored my favorite column setup but i rarely apply it via this command since i take care of my columns

If FSS turns out the way i hope than it will be superfluous for me...

[serendipity]

Maybe this can be useful for somebody. I like the fact that everything about columns can be accessed from Views>Columns which is very user-friendly way to do it. And if we are going to have default FSS (which is user customizable) then:
1. "Define Current Column Setup as Default" will update the default FSS with current column setup. and
2. "Restore Column Setup from Default" is not required since FSS is here but can be changed to "Restore Column Setup to factory Default" which will use XY's fresh install default.
Just thinking out loud.

[j_c_hallgren]

2. "Restore Column Setup from Default" is not required since FSS is here but can be changed to "Restore Column Setup to factory Default" which will use XY's fresh install default.
Just thinking out loud.

I may be missing something but I still see this as useful in the original form, because if one temporarily modifies some settings in a folder but does not save them to FSS, and then wants to undo those temp settings, wouldn't this function be the one to do so?

[admin]

Okay, I keep it.

[serendipity]

2. "Restore Column Setup from Default" is not required since FSS is here but can be changed to "Restore Column Setup to factory Default" which will use XY's fresh install default.
Just thinking out loud.

I may be missing something but I still see this as useful in the original form, because if one temporarily modifies some settings in a folder but does not save them to FSS, and then wants to undo those temp settings, wouldn't this function be the one to do so?

Aah OK, that might be useful then. But I was thinking about an auto-save feature in general for FSS. I dont know if its good or bad, because on one hand it might suck more memory each time user changes something but on the other hand user has to manually save changes he/she made. hmmm
Not too sure at this time. Don might know if its good for XY to have an auto-save feature.

[j_c_hallgren]

But I was thinking about an auto-save feature in general for FSS. I dont know if its good or bad, because on one hand it might suck more memory each time user changes something but on the other hand user has to manually save changes he/she made. hmmm
Not too sure at this time. Don might know if its good for XY to have an auto-save feature.

I definitely think auto-save would need to be a user defined preference setting(s), as I may not want it to save anything other than when I explicitly ask it to...and I could see it split into a couple of groups (general/default vs specific folders, etc).

[serendipity]

But I was thinking about an auto-save feature in general for FSS. I dont know if its good or bad, because on one hand it might suck more memory each time user changes something but on the other hand user has to manually save changes he/she made. hmmm
Not too sure at this time. Don might know if its good for XY to have an auto-save feature.

I definitely think auto-save would need to be a user defined preference setting(s), as I may not want it to save anything other than when I explicitly ask it to...and I could see it split into a couple of groups (general/default vs specific folders, etc).

I agree.