Page 2 of 2
Re: Precedence of View Settings
Posted: 09 Jul 2014 16:53
by Stef123
I obviously can enable list styles 1) globally 2) per tab 3) FVS - all at the same time
Concerning these overlaps - is there any documentation I can read instead of pestering you with a battery of questions?
admin wrote:No, this is not documented I think. Never found the time.

Nor do I have the time figure it all out, I cannot even tell when I hit a bug or whether it's intended precedence
SammaySarkar wrote:I believe the order is : FVS -> tab -> tabset -> global
nerdweed wrote:I don''t know the complete order but Tabs > FVS (though I would have wanted higher precedence for FVS)
Are you two saying the same thing?
I sometimes get mixed results - FVS>Tab but also Tab>FVS - so I figured this whole thing may be more complex than I thought.
Re: Precedence of View Settings
Posted: 09 Jul 2014 17:06
by nerdweed
Here's what Don said -
http://www.xyplorer.com/xyfc/viewtopic. ... 95#p101742
admin wrote:What you are probably not aware of: Tab layouts have precedence over FVS. FVS sets in when you change location within a tab.
So, this may give you an hint why you see contradicting behaviour
When you switch Tabs. Tabs get higher precedence over FVS
When changing folders within tabs, FVS is applied as tab setting don't come into picture.
BTW, do you have Column Layouts unticked for Remember settings per Tab. I found that to be the culprit for me. I recently ticked it back since we now have option to save/load column layouts.
Re: Precedence of View Settings
Posted: 09 Jul 2014 17:31
by Stef123
nerdweed wrote:So, this may give you an hint why you see contradicting behaviour
When you switch Tabs. Tabs get higher precedence over FVS
Now the puzzle pieces begin to fall into place. Once again I doubt I am the only who cannot figure out the seemingly erratic behavior. The many support requests about <default> FVS Don talked about may be due to other users doing the same I did: Desperate measures to get a consistent look.
nerdweed wrote:
BTW, do you have Column Layouts unticked for Remember settings per Tab. I found that to be the culprit for me. I recently ticked it back since we now have option to save/load column layouts.
Yes indeed

You found them to be the culprit for what?
Re: Precedence of View Settings
Posted: 09 Jul 2014 17:50
by nerdweed
I was adding some soft columns to particular folders - Availability column for One drive folder which didn't make sense for any other folder and hence created a FVS for it. If I changed tabs from the One Drive folder, this would come up in the other tabs.
Similarly, if I moved from other tabs to the OneDrive folder in another tab, the Availability column wouldn't appear until I navigated within the folder or restored the FVS.
Thats what I meant by saying I would like to have FVS > Tab, plain and simple. No If and Else required for explanation either.

Re: Precedence of View Settings
Posted: 09 Jul 2014 20:09
by admin
In the next version "Always Show Path Column" will overwrite any column settings in a Default FVS. Taking "Always" seriously...

Re: Precedence of View Settings
Posted: 09 Jul 2014 22:18
by nerdweed
admin wrote:In the next version "Always Show Path Column" will overwrite any column settings in a Default FVS. Taking "Always" seriously...

No. Don't push FVS down under. It should be the topmost. File Management is about Files and Folders. Tabs are enabler. Settings specific to Folders should have the highest preference
Re: Precedence of View Settings
Posted: 10 Jul 2014 07:14
by bdeshi
nerdweed wrote:No. Don't push FVS down under. It should be the topmost. File Management is about Files and Folders. Tabs are enabler. Settings specific to Folders should have the highest preference
Yes, I agree.
(I'd have asked for it if I knew tabs get higher prio.)
Re: Precedence of View Settings
Posted: 10 Jul 2014 09:04
by admin
Sure. It just affects the *Default FVS*.
Re: Precedence of View Settings
Posted: 10 Jul 2014 09:55
by nerdweed
admin wrote:Sure. It just affects the *Default FVS*.
I trust you mean Always show Paths only affects the *Default FVS*
Or are you giving FVS the precedence it deserves.
