[davidfor]

Originally Posted by Nick_1964

I didn't ment that ALL changes in firmware are not good, only the 2 I called are not in my opinion.
See https://www.mobileread.com/forums/sho...&postcount=112 for the explaining of the read stats when powering off.

And I disagreed. I think the light staying on a bit is useful. And my bet is that it was a one-line change in the code.

We have some disagreement on the bug fixes (but hey,we are behaving people so we don't gonna fight on it ) because some bugs are really for long on that list and I think you must show at least more priority about solving them.
A known bug can interfear with a new option or introduce a new bug.
The paragraph bug is one of those bugs that was there still several new firmwares later.
Annoying enough to made patches for it.

The long paragraph bug is a bad example. The bug was not in code that Kobo controlled. It was actually in the RMSDK. To fix that bug meant that Kobo had to wait until it was fixed by Adobe, take the new version of the libraries involved, do all the testing that is needed to make sure that nothing else was broken and was compatible with their code. Against that, they have to decide if the risk is worth the fix. Personally, I had to go out of my way to trigger this bug. In the time it was in the firmware, I saw it in at most 10 books that I read. And I think only two of them had more than two paragraphs that triggered it. If those were the stats presented to me when prioritising a bug, it would be way down the bottom of the list.

And using the patch as proof that Kobo could fix it doesn't work. The patch broke other things and meant the book wasn't displayed correctly. People had to decide which was the preferred behaviour.

I know they can't put every feature in it but lets say you want to scroll 5 pages back.. try to do that with the slider in a big book, it will drives you crazy because you can't enter page numbers or even return to the page you was left.
Remember the small bug about the light, it is still there..2 times 28%, look at the huge difference between 50 and 51, still 2 times at 56.. and there is your own list of still present bugs (this small one isn't on it ) it is just sloppy to leave it there.

I think choosing five pages doesn't help your case. Tapping back five times is probably less work than bringing up a dialog, doing the maths in your head, typing the number in pressing the go button. But, I suppose you mean, go to a particular page number. To be honest, the only times I ever do that is from the ToC or the index of a paper book. Both of those say to use some sort of linking system to get where I want. But, I am surprised Kobo don't have it. Of course, for the kepubs which until now have had a per-chapter numbering system, it wouldn't have been very useful. For them page 100 doesn't mean much if the chapter doesn't have 100 pages.

As to my bug list, yes, it and fixes is very ego-centric. It lists things I notice or have been shoved in front of me recently. And I stated it in my post. And I've stated it every time I have made a post like that.

As to the missing numbers in the light levels, I really don't care about them. Is fixing them the best use of the Kobo developers time? I don't think so. And, as you think Kobo is concentrating on issues/features that are for a small number of people, how many people would actually notice this? Or care.