Hitcher Wrote:This returns empty when in the root -
I know, I was aiming more for a check in the including stage, but I realize it's not possible as it's only executed when the window loads.
I got around it by using the including method you posted, and then having two separate layouts with a visibility condition to check if I'm at the root. So, I'm still using a visibility condition, but at least I'm using it less.
I found some more ways to avoid them and the amount of code for my list view for example is less than 50% of what it was before
jmarshall Wrote:I can easily add Content(Root) or some more appropriate flag - note that there is more than just "root" here - eg with flatten off you also just get a bunch of nodes listed, which I suspect you'll want to use the same view type for.
Yeah I was thinking about that later too. Right now I'm using ![Container.Content(movies) | Container.Content(tvshows),etc] to separate those from the higher level nodes. So I guess I would still need to do that if Content(Root) was available.
If Content(Root) would apply to the files node too, it would be a good substitute for using stringcompare(Container.folderpath,sources://video/) though.
Let me think about it as I work on this, I wouldn't want you to spend time on it if there's not enough need for it.
One that I could definitely use would be a substitute for