Lines get cut off in Android app
-
Hi there,
I have recently switched phones, and now on my OnePlus 6 the text gets cut off in the app. See below. I can't be sure if there's more text, so it's unusable :(
I hope you guys can fix this!
Regards,
-
@rosenbrandt I assume you're not using the beta version, right? As a stop-gap measure, you could try either
- checking if the beta version of the app already fixes your issue
- use @_08's app (https://forums.j-novel.club/topic/636/unofficial-windows-phone-win10-android-rokujouma-reader-now-in-the-faraway-corner-of-windows-store)
- or use mine (https://forums.j-novel.club/topic/940/a-new-unofficial-reader-application-for-j-novel-club-now-also-for-android)
You can't spell Keikaku without Kei – Vote for Sagrada Reset!
-
@jaquobus Thanks for your reply. I have tested the official beta app, and this doesn't solve the problem. See below. Note that a line is missing, which is even more obvious on the cut between page 2 and 3.
Even the webapp has this issue apparently, but only for the title page as far as I can see right now.
So @jnovelclub, pleas fix this :)
Regarding unofficial app, I'm a bit hesitant, as I'd have to login. I bet there's a way to pull data from a webview with JavaScript.
-
Click the arrow on the top of the screen.
Set the text to continuous flow rather than pages. (you scroll down rather than flip pages)
This should fix the issue.
-
@village-idiot Thanks for the tip. This solves the problem only partially. I'm still missing the last line of the chapter. While it doesn't cut as much text away, it's still an issue.
Furthermore, the fetching/rendering of the next "continuous" part while scrolling down is really slow, so I'd prefer the paged version to work correctly.--
Edit: also tiny point of feedback for the beta app if @jnovelclub is reading this: implement feedback on applying changes in text settings. I assumed the checkmark meant "ok" as in "apply & close". So seeing no changes (I changed paging to scrolling) and not closing made me wonder what was going on. Whereas the X made me think it meant "cancel".Edit 2: while I'm at it: update the progress in the release list when coming back from reading. When reading chapters consecutively, this would help a lot in pointing users to the next chapter without doubles or skipping any. This should be fairly easy in react I think? Looking at it, you implemented pull to refresh, which sort of solves this.
-
This also affects the iOS app. Sam has said he's aware of this issue in the Last/First Idol thread.
In vertical mode you can hold the page before releasing, and then you can see the text continued onto the next page. The text overlaps, but you can still read basically read it.
