The last few updates have all been focused on adding more and more features. To change things up a bit, this release will be focused on improving the quality of the app: fixing long-standing issues, addressing pain points, improving performance.
Changes so far
- Save and restore post feeds on app recreation. This should make the app behave in a more predicable way. Eg. if you leave the app for extended period and come back, the app should now preserve exactlyn where you were before you left. No more losing your spot!
- Add setting to toggle save/restore post feeds on app recreation.
- Fix issue where some images won't load.
- Fix issue where user profile screen doesn't change when current account changed.
- Fix issue where "save post" button state doesn't reflect actual state of whether the post has been saved or not in certain cases. Eg. if the post is saved, the save post button should be filled.
- Fix navigation rail bugs when the navigation rail is on but large screen support is off.
- Continue to improve error messages.
- Fix a bug where comment timestamps do not update on refresh.
- Manually add a workaround to get
img.gvid.tv links to work in the app.
- Slightly improved text editor.
Update
Aiming for this to be a simple update. I am testing the changes. Should have a release by tomorrow.
Update 2
Final round of testing underway. Release imminent.
There is a new bug in the current version if you use a Galaxy fold big screen, kind of hard to describe so here is a screenshot:
As always, thanks for your great work!
oh that is an interesting combination of settings I did not test for a while. You must have rail on Auto or On but have Large screen support Off for this to occur I think. Or have a weird screen size such that the app thinks a nav rail is best but not large enough to trigger large screen support.
In either case I will fix this for the next release.
As far as I can tell, rail mode is off and large screen is on?
For reference the resolution for the folded out display is 1856 × 2160 pixels and it happens in "portrait" mode, where the resolution will be weird I guess.
If I switch to landscape the issue is not present, I didn't think to test for that until you mentioned "weird screen size".
Thanks for looking into it, and it's probably a corner case since the foldable screens are not all that common, at least not yet.
From your screenshot, rail mode should definitely be on since the navigation rail is active in your screenshot (its the left side bar). I'm surprised that screen aspect ratio doesn't trigger Large screen mode though.
Here is a screenshot of the setting, and if I read this correctly it's off, which makes sense for me as I mostly use the app in "small screen mode" where I prefer it to be on the bottom.
The problem surfaces when used in unfolded (big screen) portrait mode, as for landscape view of the same unfolded screen, it's split and works as usual.
I checked the code and it looks like if "Large screen support" is on then "Navigation rail mode" is ignored. This is to give the feature "Large screen support" more of a say on how to lay out larger screens. Your device must have just been slightly too narrow to actually trigger the split display though which looks like:
Yes, this is the layout I get in landscape, but it's not picked up in portrait, so that it's just a bit too narrow would make sense for it not to be picked up as a large screen as the resolution is kind of weird when tilted into portrait instead of landscape.
Do you need anything more from my part? If so, or if you want me to test/change anything, let me know, I am happy to supply with whatever I can to help 🙂
No, I think I have everything I need here to fix the issue reported. Thanks for the report!
Just happy to help 🙂