[GUI Plugin] View Manager

[ownedbycats]

A slight problem I have with the tab-switcher is that I have a 'Default' view shared between 3 different VLs. Do I have to create 3 different VLs sharing the names?

EDIT: Also it doesn't seem to work. I disabled the Action Chain, set a view On Device to change when On Device VL tab selected, it didn't change.

[BetterRed]

Originally Posted by JimmXinu

Works for me. I only did minimal testing of the new features, though.

IMO — the General options group should precede the other three groups, viz:



As can be seen I don't use the Search & Layout options.

BR

[ownedbycats]

Also rendering glitch here with ampersands

[kiwidude]

Hi - thx for the feedback.

@BetterRed - the intended reason for that ordering is it keeps all the settings that were view specific together, then General Options was supposed to be things that are library level (i.e. not view specific). "Jump to the top when applying this View" changed from being a library level to a view level setting a long time ago without being moved sections, I fixed that now. Really the General Options should be on their own "tab", but with only one option it wasn't worth it.

@ownedByCats. the rendering ampersand thing is a Qt thing, I have added a workaround for this to escape it when rendering your view name in the menu.

Sharing a view across multiple virtual libraries is an interesting edge case I hadn't thought about. With the previous build you would indeed have to duplicate the view for each VL. I was thinking of adding (another) checkbox option to deal with this but then decided I could more simply instead tweak the code.

Currently the logic works like this:
1. IF the user is switching to a named virtual library, AND a view is defined that specifies that same VL name AND the view has the apply on tab change checked, THEN apply that view
2. IF the user is switching to the All Books virtual library/current search, AND find the first view defined that has NO VL name specified AND the view has the apply on tab change checked, THEN apply that view.

Which leaves a hole for the third case which I can fill like this:
3. IF the user is switching to a named virtual library, AND there is NO view with that VL name specified, AND there is a view with NO VL name specified AND the view has apply on tab change checked, THEN apply that view.

So that means you can pick your "default view", not have to tie it to a specific VL/duplicate it and simply tick the apply on tab change option. That will apply it to the default "all books" or VL tabs (cases 2 and 3). If you additionally have a specific view you want to use on just one of those VL tabs that is fine too, that is case 1 above - just specify the VL name for that view only.

As for your "OnDevice didn't work" - I need more to go on than that All my testing has the view switching applying as I expect. Possibly you haven't configured it as I would expect? If you can share screenshots of your two views (default and ondevice) I can take a look...

New version attached. I will update the help page once there is some feedback confirming it is working as people expect.

[ownedbycats]

I have most of my view names (except Default and Series) match a virtual library. None work

[ownedbycats]

Oddly, in my Wishlist library (which I was using to test), if I click "Cozy Mystery" tab it switches to the Star Trek VL

EDIT: In my main library, after renaming Default to a blank it now switches every VL to Currently Reading

[kiwidude]

@ownedbycats - it only makes sense to tick the "Apply this view when matching to a VL tab" to a *single* view that has no VL switch setup for it. Shown above you have it ticked for both Star Trek and Cozy Mystery, but neither of those is actually associated with a VL (by using the "Switch to this Virtual Library" dropdown).

I havent looked through your previous post screenshots yet to see if that has a similar issue (after 1am here) but will look tomorrow. I did contemplate whether to put some sort of dialog prompt warning or have it "untick" silently where there is a conflict in views like your second post but opted not to as yet to see how it went without it. As I described in my "logic" post above, it finds the "first" view (with the expectation that there is only one for that criteria) - if you have multiple you can end up with the one you don't expect as you saw.

EDIT: Just from a quick skim at a couple of screenshots in your previous post I see the same issue. Looks like I should add the dialog warning to the plugin to explain what is going to happen when you try to click the checkbox on a second view with the same "scope" (i.e. second view with no VL switch dropdown selection, or second view with a Switch VL selection to the same VL name). If the user proceeds from my warning dialog it will have to untick that checkbox on your other view that has the conflict. Also I will of course have the Help page to try to explain this if it isn't clear.

[ownedbycats]

My views I don't have associated with a VL because sometimes want to use them in different VLs - e.g. using the On Device view in my Fanfiction VL, or any other view in Cleanup so I can see the specific associated columns. Instead I use the restrictions.