Pachli 1.1 is now available.
This is a bug-fix release, with fixes including:
- Fix crash on entering MainActivity on tablets (#25)
- Ensure refreshing does not create a gap in the timeline (#43)
- Restore the user’s home timeline position (#44)
- Show the FAB according to the user’s preferences (#29)
- Fix toolbar flickering when scrolling lists (#26)
Read on for more details about the changes in this release.
Fix crash on entering MainActivity on tablets
Richard Merren noted the same crash on Samsung tablets, and Sebastiano Poggi reported the crash on Pixel Fold tablets.
Both issues are fixed.
Ensure refreshing does not create a gap in the timeline
Pachli was forked from another Mastodon client, Tusky, and inherited a bug triggered when you refresh your timeline.
In certain circumstances the refresh would leave large gaps in the timeline. For example, if you leave the app overnight, and refresh in the morning, it’s likely that many posts that arrived overnight will not be shown, despite appearing in the Mastodon web UI.
This is fixed.
Restore the user’s home timeline position
When you re-open the app after a period away it should restore your reading position to the same post you were looking at when you left, assuming that post is still visible to your account (it’s not been deleted, you haven’t muted or blocked the poster, etc).
Pachli is now better at doing this.
Some issues still remain, and are tracked in issue #53.
Show the FAB according to the user’s preferences
The “FAB” is the “Floating Action Button” at the bottom right of the screen that allows you to create a new post or otherwise perform some action.
There is a preference to hide this button when you are scrolling lists, and it wasn’t honoured in many cases.
DoKo reported this, and it is now fixed.
Fix toolbar flickering when scrolling lists
I noticed that scrolling some lists would result in the toolbar at the top of the screen flickering. This should now be fixed in all cases.
There have been related cosmetic changes; I noticed some colours were incorrect, and Jener reported a significant accessibility issue with preference colours which is also fixed.
Thank you to everyone who took the time to report issues and provide additional followup information and screenshots.