Firmware 4.18.13737 released

[MGlitch]

Originally Posted by JSWolf

I didn't think you could be any more wrong. But you are even more wrong then before. You are so wrong I don't know if it's possible to be any more wrong. But I think you'll probably surprise me and be even more wrong yet again. The level of wrongness you are showing is staggering.

Anyway, page numbers are much more efficient at the bottom. When you change the page, most of the time you look at the top of the screen. So if you want to see the number of screens left in the chapter or the time or the %, it's there at the top where your eyes are looking. At the bottom, you then have to shift your view back to the bottom and then back to the top to continue reading.

Oh poor Often Wrong Jon, can’t even back up his claim that I’m wrong with any evidence. And is only able to cite an opinion to back up yet another goal post shift.

Wrong Jon Silver, the discussion wasn’t what you find most beneficial. It wasn’t even about what most people do or do not prefer. No, Wrong Jon Silver, it was about you saying page numbers have only ever been at the bottom of the page/screen.

You’ve been wrong from the get go. You’re probably so wrong you don’t know what right feels like anymore. You’re so sadly wrong that the Guinness World Record people want to talk to you about featuring you as the most wrong person. I can see it now “Wrong Jon Silver Wrongest Man Alive: this man insisted on something so much that even when he himself provided a statement with contrary information he went on insisting he was right”. Kids the world over will use you as a benchmark of being wrong. I would be surprised if there was ever again a person so wrong.

Anyway as the natural inclination is to return to the top of the page/screen upon finishing a page the top of the screen is a perfectly viable place for page numbers. Some will prefer it, others will prefer the bottom. But the fact remains this is a matter of opinion there is no one place page numbers must be, nor is there only place they have exclusively been going all the way back to when page numbers were first used (since Wrong Jon Silver likes using previous usages as precedent for how things should be). Even narrowing the company down to just Kobo shows a history of different places.

[John F]

I inadvertently updated my Forma. Did they take away the option to hide the footer and header, I don't see the option?

[MGlitch]

Originally Posted by John F

I inadvertently updated my Forma. Did they take away the option to hide the footer and header, I don't see the option?

they didn't remove them, just renamed them. They're in reading settings as book and chapter progress.

[4691mls]

Originally Posted by John F

I inadvertently updated my Forma. Did they take away the option to hide the footer and header, I don't see the option?

Go to the settings for Chapter Progress and Book Progress and set those to Off

Editing to say I see mglitch and I posted at the same time - oh well

[davidfor]

Originally Posted by JSWolf

I like the way it's done with ePub. I get ADE page numbers for the entire eBook and for the chapter I get how many screens.

What magic did you invoke to achieve that? Here, the page numbering for the chapter and book in epubs uses exactly the same method.

[Phil_C]

I'm seeing a problem with the Reading Progress information screen in this firmware. The current and next chapter times remaining and the chapters graphic all "stick" where they start. They do not change as I progress through chapters and the book. They will reset to the proper information if I go to the home screen and back to the book. Then they stick right there again until I repeat the home screen trick.

I set the header and footer to show time remaining, and those progress correctly as I read. But the Reading Progress screen still does not.

The cause is not any of the patches, because I briefly went back to the original 4.18 FW without patching. Same problem.

This is on a Clara with kepubs converted from epub via calibre transfer.

Am I missing something? I'm surprised that no one else has reported this.

[MGlitch]

Originally Posted by Phil_C

I'm seeing a problem with the Reading Progress information screen in this firmware. The current and next chapter times remaining and the chapters graphic all "stick" where they start. They do not change as I progress through chapters and the book. They will reset to the proper information if I go to the home screen and back to the book. Then they stick right there again until I repeat the home screen trick.

I set the header and footer to show time remaining, and those progress correctly as I read. But the Reading Progress screen still does not.

The cause is not any of the patches, because I briefly went back to the original 4.18 FW without patching. Same problem.

This is on a Clara with kepubs converted from epub via calibre transfer.

Am I missing something? I'm surprised that no one else has reported this.

I can replicate this on an H2O on 4.18 which never had 4.18 patches applied. Though I was using a kobo purchased kepub. I’ve not tested yet on my Forma though I’d wager it’s an issue there as well.

[davidfor]

Originally Posted by rashkae

It's quite possible, (I would say likely) that an oversized internal file will cause problems like this. But it's probably not the book size or book whole book progress that causes the problem. I just tested with a 1700000 word book, and the Kobo did not even seem to notice or pause on anything..

My test book is 3407994 words. Kobo says the book in question is 187436K. So an order of magnitude larger.

(I was expecting a longer Import on disconnect, since that's where the individual file sizes used to estimate pages would be calculated, but that zipped right by.)

The import doesn't do the word count. It does gets the ToC, and it might check if the file a ToC entry exists, but it doesn't do the word counts. These are done the first time the book is opened. And that can take a while. With previous firmware versions, you could see when it was finished as that was when the page count was displayed in the footer. The timing is a bit different since 4.17.

[issybird]

To MGlich and JSWolf: have done with the back and forth on the location of page numbers. Take it to PM if you must continue. Further posts that repeat what has been said will be deleted.

[JeanPierre]

Originally Posted by issybird

To MGlich and JSWolf: have done with the back and forth on the location of page numbers. Take it to PM if you must continue. Further posts that repeat what has been said will be deleted.

It would have been great if you could have split it all out into another thread. I cannot believe how much puerile nonsense I just had to skim through to catch up on the discussion.

Meanwhile geek1011 announced a patch that actually solves the problem and it's completely lost amidst the inanity.

[MGlitch]

Originally Posted by JeanPierre

It would have been great if you could have split it all out into another thread. I cannot believe how much puerile nonsense I just had to skim through to catch up on the discussion.

Meanwhile geek1011 announced a patch that actually solves the problem and it's completely lost amidst the inanity.

Except geek1011 also posted about that patch over in the instructions for patch 4.18 https://www.mobileread.com/forums/sh...=323419&page=2 hardly lost for anyone who patches their devices.

[Terisa de morgan]

Originally Posted by geek1011

For those who have been asking for a header/footer swap patch, I just figured out how to do it efficiently. Here is the patch, which will be in the zips for v54 in a week (jackie_w and I are still taking a break): https://github.com/geek1011/kobopatc...19c58338406a31.

Thank you very much! And enjoy your well deserved break!

[poczynek]

EDITED OUT.

[JSWolf]

Originally Posted by davidfor

What magic did you invoke to achieve that? Here, the page numbering for the chapter and book in epubs uses exactly the same method.

So that's why the page numbers for the chapter seem buggy. They aren't. It's just using ADE page numbers. Thanks for that bit of info.

[MeiGuddet]

Originally Posted by ratinox

In before JSWolf is an ass about illumination, again.…

I hope you mean ace