If I have the orion window maximized, and select a game from the games tab. The number of items that shows up is 25. After browsing the code there is a hard coded number of query items displayed. However, my window can display far more that 25 items (91 items on my 1440p monitor) checkScrolled() does not get called because, I can not scroll. The only way that I can get more results to polulate is to click on another tab and click back to the channels tab.
IMO, the number of items being fetched from the inital query (and likely all subsequent queries) should be calculated from the number of items that can be displayed on the screen plus some buffer. (Ideally in increments of the number of items to fill a row)
As a wish list item it would be nice if the next set of results could be fetched when the scrolling position is say... 50% of the way through the list rather than when you reach the bottom (true infinite scrolling)
If I have the orion window maximized, and select a game from the games tab. The number of items that shows up is 25. After browsing the code there is a hard coded number of query items displayed. However, my window can display far more that 25 items (91 items on my 1440p monitor) checkScrolled() does not get called because, I can not scroll. The only way that I can get more results to polulate is to click on another tab and click back to the channels tab.
IMO, the number of items being fetched from the inital query (and likely all subsequent queries) should be calculated from the number of items that can be displayed on the screen plus some buffer. (Ideally in increments of the number of items to fill a row)
As a wish list item it would be nice if the next set of results could be fetched when the scrolling position is say... 50% of the way through the list rather than when you reach the bottom (true infinite scrolling)
Cheers