Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No specific view by page. #29

Open
rjousse18 opened this issue Jan 3, 2024 · 9 comments
Open

No specific view by page. #29

rjousse18 opened this issue Jan 3, 2024 · 9 comments
Labels
cannot reproduce Issue can't be reproduced, so fixing it not possible. Might be an user error, might be not. help wanted Extra attention is needed

Comments

@rjousse18
Copy link

rjousse18 commented Jan 3, 2024

When I change to another view for a specific page, like the resume page, it changes the view for all page of the add-on. It's a bit annoying since some pages are better in some view and other page are better on other view. Why is it global and not specific per page ?

@smirgol
Copy link
Owner

smirgol commented Jan 3, 2024

When did you update the last time? There were some changes that might have caused that. I have rolled back the changes now, it should behave like before. Please let me know if the problem is still there.

@rjousse18
Copy link
Author

Nope, same as before, if I change the view on "anime > popular", it changes the view for all the pages.

@rjousse18
Copy link
Author

Update : some pages are not affected.

@rjousse18
Copy link
Author

rjousse18 commented Jan 3, 2024

After some tests, it seems that "queue" page, "history" page and "resume" page share the same view mode.
Home page, "animes" page and all sub-page of "animes" share another same view mode.

@smirgol
Copy link
Owner

smirgol commented Jan 3, 2024

I actually never realized, because I use the same view for everything. I think it's more of a Kodi thing and not sure if that can be changed easily. I'm curious if that is the same for other addons, like Disney+ or Netflix - I assume it is.

I had a look at the page-types used for the views and it matches with what you have tested:
"queue", "history" and "resume" use the "episodes" display type of Kodi, as these are listing episodes.
most of the ones under "anime" uses "tvshows" - with the exception of the seasons listing, which uses the "seasons" view

I assume that Kodi saves the display type per one of these types. Not sure what can be done about that, other than somehow adding options to the settings to enforce specific display types, but that's easier said than done.

@smirgol
Copy link
Owner

smirgol commented Jan 4, 2024

I've checked it and I can set a different view for every menu item and it stays that way. Not sure if it is because of my changes to the lists today, though. I will ping you when I finished my work on that and updated staging with it, so you can give it another try.

@smirgol
Copy link
Owner

smirgol commented Jan 5, 2024

New changes are on staging. Let's hope it resolves your issue :)

@smirgol smirgol added the question Further information is requested label Jan 8, 2024
@rjousse18
Copy link
Author

I tested yesterday, and it seems it same as before. When I change the view style of crunchylist for example, it changes the view style for the main page too. Pretty annoying, especially if we compare with Netflix add-on where each page can be change individually.

@smirgol
Copy link
Owner

smirgol commented Jan 10, 2024

Hm I'm out of ideas right now. For my skin (Aeon MQ) I can change the layout of every page and they will all be different. Have to investigate further, but changing my skin for testing purposes is problematic :)

@smirgol smirgol added the help wanted Extra attention is needed label Feb 12, 2024
@smirgol smirgol added cannot reproduce Issue can't be reproduced, so fixing it not possible. Might be an user error, might be not. and removed question Further information is requested labels Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cannot reproduce Issue can't be reproduced, so fixing it not possible. Might be an user error, might be not. help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants