View Single Post
Old 10-09-2019, 09:39 PM   #87
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 7,045
Karma: 4604637
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Three (presumably unrelated) issues with the new reader I've seen:


1) The Home and End key short cuts (mapped to "Scroll to the beginning/end of the current file" formerly "Scroll to the beginning/end of the current section" in v3) don't behave the same for me in Win10.

When I use End, instead of the bottom of the current file/section, I'm placed at the beginning of the next file. Unless I'm already in the last file, then nothing happens.

When I use Home, I'm placed at the beginning of the current file, unless I'm already there, in which case I'm placed at the end of the previous file.


2) The new scrollbar doesn't respond as I expect to clicks in the areas above and below the slider. I expect them to behave like most scrollbars, equivalent to PageUp/PageDown in this case.

Instead, clicking below the slider on the scrollbar jumps to the next section start(or TOC entry?) and clicking above the slider acts like PageDown.

Also, holding the button down above and below the slider doesn't repeat as usual.


3) Depending window/font/spacing sizes, a line of text can be cut off vertically at the top or bottom of the display frame. Sometimes the same line of text will be cut off at the end of one 'page', and again at the top of the next, resulting in never having a clear view of it. It would be nice if that didn't happen. I can provide images showing it happening, if desired.


Sorry if these have already been reported. I'm sure it's a pain working through all the issues a new implementation raises. Thanks for all your hard work.
JimmXinu is offline   Reply With Quote