When setting an image for an era or event, the dialogue window from which to choose the image does not accommodate extremely long gallery lists and while it is possible to scroll to the bottom of the window, it is not possible to scroll to the top. Notably, it also does not display the bottom of the gallery list either (Linebound has Galleries after 'P'), cutting it off to display the All / Recent images section.
1. Make a really long list of image galleries on a world. 2. Open the image dialogue on Standard Timelines. 3. Try to get to the top of the list. 4. Check the bottom of the list to see if any image galleries have been excluded.
It may also be worth noting that this applies when setting the image at the top of a new style timeline as well (I expect it is shared logic) and that the search function within the dialog doesn't seem to pick up all images, even if all images are selected at the bottom, so you can't pull in images from unlisted galleries.
All your galleries should now be visible and scrollable. Please have a look and let me know if the fix has, uh, fixed the issue.
Thanks for the fix. It kind of works but not completely (at least for me). I do now see my galleries listed from the first one, which is good, and I suspect that all the galleries are being loaded for display, but I can't scroll to the bottom of the list so I don't have the ability to select from the ones at the end. What happens is that the scroll bar actually disappears from the bottom of the screen, so you can't drag on it anymore. This might actually all work fine with a mouse with a scroll wheel to be honest (I haven't got one of those to test with at the moment) but if you are using a track pad and the UI to drag the scroll bar, you can only go so far down the list before you lose the scroll bar.
Don't thank me for half a fix. How did I miss that? It should be all fixed now. There, you can thank me for the whole fix(I hope, otherwise this is embarrassing...)
All looks good to me now! I'm always polite to developers, since I am one myself :-) As far as I am personally concerned, this bug can be closed but I was not the original person who raised it, I've just jumped on their bug report since I had the same issue.
Yes, fixed now. Thank you very much.