Calibre Viewer problem - Page 6

Tanjamuse · 10-07-2019, 01:22 AM

Quote:

Originally Posted by kovidgoyal

I have told you before, I have added a retry for this operation to work around antivirus/file sync software, you just need to wait for the next release.

How about adding the option/tweak for disabling cover if I don't want it shown?

kovidgoyal · 10-07-2019, 01:27 AM

Quote:

Originally Posted by Tanjamuse

How about adding the option/tweak for disabling cover if I don't want it shown?

Sorry no I dont think the code complexity is worth making you stare at a cover for a second when you open a book.

Tanjamuse · 10-07-2019, 01:40 AM

Quote:

Originally Posted by JimmXinu

Is there a discussion somewhere I could read about why the reader makes up a cover image now? I'd turn that off if there was an option for it. Failing that, I'd expect it to use the Calibre metadata cover when there isn't one in the file.

It's not just me who has asked for it.

kovidgoyal · 10-07-2019, 04:08 AM

Quote:

Originally Posted by Tanjamuse

It's not just me who has asked for it.

The you here is generic.

sjfan · 10-07-2019, 10:24 PM

Quote:

Originally Posted by kovidgoyal

@sjfan: that was a problem in flow mode, will be fixed in the next release. https://github.com/kovidgoyal/calibr...551b50916572c0

Awesome, thanks. There's some problem with my version of g++ trying to build from source, so I'll take a look when the next release comes out. Thanks for your time and effort!

EDIT: And 4.1 is out. I can confirm this fixes the issue, thanks again!

thiago.eec · 10-08-2019, 06:49 AM

First, I must say the new 4.1 viewer is great. The scrollbar is just beautiful.

Now, I'm having trouble to use the Toggle Page/Flow Mode shortcut. CTRL+M was not working, so I tried to delete it and reassign, but now I can't set it: when I click CTRL+M, the assigned keys are CTRL+Enter. Temporarily, I'm using CTRL+P (all other keys seems to work, except M).

Windows 10 1903 x64, calibre 4.1 x64, epub file.

kovidgoyal · 10-08-2019, 08:31 AM

That's because on windows, chrome stupidly maps ctrl+ascii key to an ascii control code and ctrl-m maps to enter. but instead of reporting the actual ascii control code, it reports the key as "Enter" which means the workaround I added for this is not going to work. And there is no way to distinguish between ctrl+m and ctrl+enter on windows Sigh. Guess I will have to inspect the keycode in this case to try to distinguish, le double sigh.

thiago.eec · 10-08-2019, 09:17 AM

Quote:

Originally Posted by kovidgoyal

That's because on windows, chrome stupidly maps ctrl+ascii key to an ascii control code and ctrl-m maps to enter. but instead of reporting the actual ascii control code, it reports the key as "Enter" which means the workaround I added for this is not going to work. And there is no way to distinguish between ctrl+m and ctrl+enter on windows Sigh. Guess I will have to inspect the keycode in this case to try to distinguish, le double sigh.

Just tested the fix. Although it lets me choose CTRL+M, is just an illusion. It shows CTRL+M, but when you close and get back, you will see that it changed to CTRL+Enter.

Also, about the loading screen with Qt now: I don't know if this only happens because I'm running from source, but every time a book loads, the Preferences screen flashes rapidly before showing the content.

kovidgoyal · 10-08-2019, 09:37 AM

Quote:

Originally Posted by thiago.eec

Just tested the fix. Although it lets me choose CTRL+M, is just an illusion. It shows CTRL+M, but when you close and get back, you will see that it changed to CTRL+Enter.

Doesn't matter pressing ctrl-m works.

Quote:

Also, about the loading screen with Qt now: I don't know if this only happens because I'm running from source, but every time a book loads, the Preferences screen flashes rapidly before showing the content.

Its not the preferences screen, its the open book screen and it was always there just a bit harder to spot.

thiago.eec · 10-08-2019, 09:49 AM

Quote:

Originally Posted by kovidgoyal

Doesn't matter pressing ctrl-m works.

You are right, it does work. Thanks.

Quote:

Originally Posted by kovidgoyal

Its not the preferences screen, its the open book screen and it was always there just a bit harder to spot.

Oh, I see. Well, when it's not the first time the book is being opened, the screen just flashes. But, when opening for the first time, then it really shows, sitting there while the book loads.

EDIT: The above is fixed now with the last pushed commit.

jbooker · 10-08-2019, 07:16 PM

I downloaded 4.0 and am having trouble with the ebook reader. when going to open a book the little wheel just spins and spins, I eventually have to go to the right where the cover of the book is displayed and click on it once, then the book finally appears in the reader. I've also had trouble with error messages, and one time I tried to open a book and five ebook readers popped up, all trying to open one book. if I download 4.1 will it clear up this problem?

JimmXinu · 10-09-2019, 09:39 PM

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.

kovidgoyal · 10-09-2019, 09:49 PM

@JimmXinu I suspect all those issues are because you are in flow mode, try switching to paged mode and they should all go away. In the paged layout section of the viewer preferences. the exception being repeating scrolling when holding the mouse down on the scrollbar, which I have not bothered to implement.

chantw0968 · 10-09-2019, 09:51 PM

I just downloaded the 4.1 version is there going to be an update to include pages in the reader view. Please advise.

Thank you.

BetterRed · 10-09-2019, 10:26 PM

Quote:

Originally Posted by chantw0968

I just downloaded the 4.1 version is there going to be an update to include pages in the reader view. Please advise.

Thank you.

You need to put in the header or footer - it's called Position in book/section.

BR

10-09-2019, 09:51 PM	#89
chantw0968 Connoisseur Posts: 51 Karma: 10 Join Date: Apr 2014 Device: sony e-reader	I just downloaded the 4.1 version is there going to be an update to include pages in the reader view. Please advise. Thank you. Last edited by chantw0968; 10-09-2019 at 10:00 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Calibre Japanese Vertical Text Viewer Problem	fobos3	Calibre	10	06-12-2020 12:32 PM
Problem with Viewer	JToner	Calibre	1	08-20-2015 04:47 PM
BUG: Calibre 2.0 E-Book Viewer ePub extra space display problem	trying	Calibre	3	08-28-2014 07:56 AM
360 Problem with viewer	soccera	PocketBook	2	04-09-2011 12:47 PM
The problem with LRF viewer	jfreyd	Calibre	3	03-22-2009 12:13 AM

10-08-2019, 06:49 AM	#81
thiago.eec Wizard Posts: 1,291 Karma: 1428263 Join Date: Dec 2016 Location: Goiânia - Brazil Device: iPad, Kindle Paperwhite, Kindle Oasis	First, I must say the new 4.1 viewer is great. The scrollbar is just beautiful. Now, I'm having trouble to use the Toggle Page/Flow Mode shortcut. CTRL+M was not working, so I tried to delete it and reassign, but now I can't set it: when I click CTRL+M, the assigned keys are CTRL+Enter. Temporarily, I'm using CTRL+P (all other keys seems to work, except M). Windows 10 1903 x64, calibre 4.1 x64, epub file.

10-08-2019, 08:31 AM	#82
kovidgoyal creator of calibre Posts: 45,604 Karma: 28548974 Join Date: Oct 2006 Location: Mumbai, India Device: Various	That's because on windows, chrome stupidly maps ctrl+ascii key to an ascii control code and ctrl-m maps to enter. but instead of reporting the actual ascii control code, it reports the key as "Enter" which means the workaround I added for this is not going to work. And there is no way to distinguish between ctrl+m and ctrl+enter on windows Sigh. Guess I will have to inspect the keycode in this case to try to distinguish, le double sigh.

10-08-2019, 07:16 PM	#86
jbooker Junior Member Posts: 7 Karma: 10 Join Date: Sep 2019 Device: none	I downloaded 4.0 and am having trouble with the ebook reader. when going to open a book the little wheel just spins and spins, I eventually have to go to the right where the cover of the book is displayed and click on it once, then the book finally appears in the reader. I've also had trouble with error messages, and one time I tried to open a book and five ebook readers popped up, all trying to open one book. if I download 4.1 will it clear up this problem?

10-09-2019, 09:39 PM	#87
JimmXinu Plugin Developer Posts: 7,125 Karma: 5005503 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.

10-09-2019, 09:49 PM	#88
kovidgoyal creator of calibre Posts: 45,604 Karma: 28548974 Join Date: Oct 2006 Location: Mumbai, India Device: Various	@JimmXinu I suspect all those issues are because you are in flow mode, try switching to paged mode and they should all go away. In the paged layout section of the viewer preferences. the exception being repeating scrolling when holding the mouse down on the scrollbar, which I have not bothered to implement.