Text alignment was resetting the position in the article list of the reader because we were restarting the reader activity to reinitialize all fragments. Rather than do that, now we tell all the fragments to update their text alignment.
I cleaned up a little bit the Reader activity as some functions were really confusing. I kept all that in a separate commit in case you wish to revert.
Tested in simulated API versions 25, 34 and 35. All tests pass.
I'll point out: after #84 I'm now getting a bunch of messages appearing about connectivity coming and going. Often when opening the home I have to force it to load articles as none will appear. I'm not opening an issue just because I did not install it on physical device yet and I just experienced this in the emulator.
## Types of changes
- [x] I have read the **CONTRIBUTING** document.
- [x] My code follows the code style of this project.
- [ ] I have updated the documentation accordingly.
- [ ] I have added tests to cover my changes.
- [x] All new and existing tests passed.
- [x] This is **NOT** translation related.
This closes issue #179
Text alignment was resetting the position in the article list of the reader because we were restarting the reader activity to reinitialize all fragments. Rather than do that, now we tell all the fragments to update their text alignment.
I cleaned up a little bit the Reader activity as some functions were really confusing. I kept all that in a separate commit in case you wish to revert.
Tested in simulated API versions 25, 34 and 35. All tests pass.
I'll point out: after #84 I'm now getting a bunch of messages appearing about connectivity coming and going. Often when opening the home I have to force it to load articles as none will appear. I'm not opening an issue just because I did not install it on physical device yet and I just experienced this in the emulator.
When changing alignment in the reader we were restarting the reader activity to reload. Doing this led to reloading the article which was initially opened every time you changed alignment. Now, when changing the alignment we retain all existing fragments but command all of them to update their alignment setting.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Types of changes
This closes issue #179
Text alignment was resetting the position in the article list of the reader because we were restarting the reader activity to reinitialize all fragments. Rather than do that, now we tell all the fragments to update their text alignment.
I cleaned up a little bit the Reader activity as some functions were really confusing. I kept all that in a separate commit in case you wish to revert.
Tested in simulated API versions 25, 34 and 35. All tests pass.
I'll point out: after #84 I'm now getting a bunch of messages appearing about connectivity coming and going. Often when opening the home I have to force it to load articles as none will appear. I'm not opening an issue just because I did not install it on physical device yet and I just experienced this in the emulator.
Thanks for the heads-up. I may have fixed the issue here
Build is failing for some api token misconfiguration.
Could you try rebasing your PR ?
4a55bc0f1dtoc3ee07dd85Just tried it. It seems to be working fine.