Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[6233638]

Am I missing something obvious here?
Glynor just linked to this post in another topic, and when watching his video I noticed that Theater View lists sub-categories on the main screen like this:


How do I create sub-categories in Theater View like this?
 
My Theater View items are nested, but you have to select a main category first, which lists the sub-categories across the top of the screen, rather than below the main category on the top-level view.
 

[Hendrik]

You have to add a "Category" type item in the Theater View config (first element in the "Add" menu here), only then will it show this nested level on the main screen.

[6233638]

OK, I think I see why this was giving me problems before.
 
For some reason when I do this I have to use "secondary roller" as my main category (e.g. Audio) rather than "primary main roller".
When items are nested below a "Category" rather than a "Root Library Item" all customization options disappear.

[glynor]

OK, I think I see why this was giving me problems before.
For some reason when I do this I have to use "secondary roller" as my main category (e.g. Audio) rather than "primary roller".
When items are nested in below a "Category" rather than a "Root Library Item" all customization options disappear.

Yep.  That's how it works.

The Secondary Roller type is oddly named, but that's what it does.  You apply it to the PARENT view, and then it makes the view nested underneath into a "secondary roller".  It seems named backwards to me (and always has) but that's how it works.

[glynor]

I guess the idea is that it is a Type of Root View that has a secondary roller.

The "primary" one should be called something like "solitary roller" or something though.

[6233638]

Yep.  That's how it works.

That seems like a bug.

I guess the idea is that it is a Type of Root View that has a secondary roller.
The "primary" one should be called something like "solitary roller" or something though.

What is the difference between a "Root Library Item" and a "Main Roller" then?
 
 
Now that I've tried setting things up that way, I think I preferred how I had it before anyway. The secondary roller implementation is quite ugly, as everything is listed before you make a selection, and it does that stupid case-changing that so many sections of Theater View do.
 
The only thing I don't like about the way things were working before is that you have to go to the top of the list to select the sub-categories.
I would prefer it if hitting back on the remote took you to the sub-category selection rather than the top-level view, and selecting a top-level item would have the selection focused on the sub-categories rather than the first item in the list by default.
 
Similarly, pressing back on the top-level view should present you with the "exit" options (or there should at least be an option to enable this) rather than requiring you to hit Esc or add an "Exit" item to the view.

[glynor]

That seems like a bug.What is the difference between a "Root Library Item" and a "Main Roller" then?

The whole thing is clunky, but I think it actually works as designed.  I'm not right at a machine where I can look it up, though, and it has been some time since I did it.

I'll try to comment later, but really we need a better wiki article written up.  I'd been long hoping they'd finally see the light and use my long-standing "put them back in Standard View in a special section" idea.

[JimH]

I'd been long hoping they'd finally see the light and use my long-standing "put them back in Standard View in a special section" idea.

It's in the Intercom file.

[6233638]

The whole thing is clunky, but I think it actually works as designed.

When I nest it under a "categories" view, the options to customize the view disappear, but navigation in Theater View itself is still using those customizations.
To customize the view I have to un-nest it and nest it under a "library" view.
 
I don't see why the options should disappear.

[rudyrednose]

I'd been long hoping they'd finally see the light and use my long-standing "put them back in Standard View in a special section" idea.

I agree, all views should be defined in the same area, be it a view for STD, TheaterView or Gizmo. 

And pleeeeease give us (optional) inheritance 

[glynor]

I agree, all views should be defined in the same area, be it a view for STD, TheaterView or Gizmo. 

And pleeeeease give us (optional) inheritance 

They do inherit, same as the Standard Views.  Or do you mean the ability to break the inheritance chain, like you can in Standard View?

That would be good, I agree.

[rudyrednose]

Break the inheritance

[glynor]

I don't see why the options should disappear.

I remember a bit of oddness here too.

The Categories disappear because you can't show Categories at the root level.  That makes sense.

But if I remember right, more hides than is needed, or something weird.

[glynor]

It's in the Intercom file.

Sounds like someone is asking for more pets. 

[6233638]

I remember a bit of oddness here too.
The Categories disappear because you can't show Categories at the root level.  That makes sense.
But if I remember right, more hides than is needed, or something weird.

I added images to my post here, which you may have missed: http://yabb.jriver.com/interact/index.php?topic=88323.msg605439#msg605439
All that has changed in these images is the item that the "Albums" view is nested under.
 
I understand that you would lose those options as a root-level item, but I don't see why you would if it's nested below a category view - especially when those customizations are still applied.

[JimH]

Oh, please....

[MrC]

When I nest it under a "categories" view, the options to customize the view disappear, but navigation in Theater View itself is still using those customizations.
To customize the view I have to un-nest it and nest it under a "library" view.
 
I don't see why the options should disappear.

Somewhere I mentioned this issue, in a thread where a user had trouble customizing a view.  No matter what the user did, the wrong things were occurring.  It wasn't until I stumbled upon this problem that we worked it out.  It's really bad.

[glynor]

Yeah, I remember the thread too.

It only applies when you un-nest "full-fledged" views back down to the Root Level, and then forget they used to be nested, if I remember right.  But I remember I did test it as I read that thread and confirmed it.

I think the issue is that it hides the Files to Show entry, but still applies the contents.

But, I really shouldn't talk since I don't know and I can't check right now.

[MrC]

If I recall, it can also happen in Standard View.  I wrote out the details, but I can't find the thread.  I think I posted it in a build thread also, but I've given up trying to find it.

[Hendrik]

I've always wondered why they can't be customized, when clearly customizations do apply and in some setups also make sense.
In fact, I have an empty view in between these days (which MC skips diligently), just to avoid having to mess with nesting when I want to modify it. (This is the solution Matt proposed when I asked about it, not sure what the case was against making them customizable)

[glynor]

If I recall, it can also happen in Standard View.  I wrote out the details, but I can't find the thread.  I think I posted it in a build thread also, but I've given up trying to find it.

You can certainly hose yourself in Standard View if you try to be too clever, because of some of the special hidden functionality.

I remember a VERY old version of my Library had a filter on the "real" Root Library item (which you can't see at all in any modern version of MC), and it was filtering my stuff even though it was invisible.

I had to nuke my Library to get rid of it.  But that was eons ago (I think we're talking circa MC12-13)...

At least you don't have the magic "hiding" Advanced view anymore.  That messed me up more than once.

[glynor]

Yeah... I was able to confirm the problem.

Views in Theater View at the Root, lose access to the Set Rules for File Display button, but any items already entered into the View in question (when nested "more deeply") still apply.

All of the Views in Theater View seem like, essentially, the same "thing", internally, I suspect.  The only way they differ is in their level of nesting, and which features they show in the Editor, depending on that level of Nesting.

[MrC]

Right, that was it.  The user couldn't get sorting to work, because the Set rules for file display were absent.

I think Matt hates writing UI code (as much as I do).  It is so freakin' mundane.