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
Add support for md_thumbnail & md_marquee #634
Conversation
supersquared
commented
Jan 30, 2020
- Added support for md_thumbnail in VideoGameListView
- Added support for md_thumbnail & md_marquee in DetailedGameListView
Anyone have any issues with these changes? |
I don't know if I can answer since I am the person who made the changes, but I'm using it since almost one month and half without any issue (many games with and without md_thumbnail and md_marquee) |
Read the code and have a question about the behavior for themes that don't specify the thumbnail - even if the gamelist.xml might have one for the games, as a result of scraping. Other than that, no objections. Sorry for the delay. |
Just committed the changes to have thumbnail off the screen by default. is that ok ? |
@jrassa how do I squash the commits? |
@supersquared you need to do a rebase. Here is a pretty good tutorial. Let me know if you need any additional help. |
You never call setVisible(true), so If you do it that way, theme designers will have to add true in the theme for the elements to be visible : It should not be required Maybe add something like that :
To squash 6 commits do that : |
- Added support for md_thumbnail in VideoGameListView - Added support for md_thumbnail & md_marquee in DetailedGameListView
@fabricecaruso There shouldn't be a need to explicitly call When applying any other theme properties, visible will be set to true unless explicitly set to false. This was tested and verified when visible was added. |
Squashed! @fabricecaruso @jrassa thank you for the help on squashing ;) |
You're absolutely right, sorry. Everything's fine. |
Add support for md_thumbnail & md_marquee