Beta testers for calibre 9 needed

[JSWolf]

Originally Posted by kovidgoyal

What doesnt work? Scrolling by dragging the scrollbar or using a mouse wheel/touchpad scrolls by pixels not shelves. It's up to you to end your scrolling in whatever position you want.

But if automatic was able to fix the shelves so when I stopped scrolling and made what's on screen show the full X number of shelves fully, that would work.

[DiapDealer]

Originally Posted by JSWolf

Try running calibre on a 4th gen i5-4300U (1.9 GHz) and you'll see slower without the GPU. Also, it only has 8GB RAM.

Remember: the WebEngine GPU setting being spoken of has absolutely no bearing on anything except the Viewer and the Editor Preview. So "running calibre" is not an accurate performance test.

[un_pogaz]

Originally Posted by kovidgoyal

The remaining questions are:
1) Should the default for the cover animation be shift or above?

2) Should the default cover thumbnail on spine be cropped or full

3) Should the minimum spine width be increased when there are two lines on
the spine? This has the downside of reducing width variation between books
and not indicating that a book is very thin. Increasing both minimum and
maximum is another option, however this has the downside of invalidating the
thumbnail cache since it depends on maximum spine width and the two lines
setting is per library not global.

Thanks to everyone for all the testing/bug reports. Phew

1) I'm for "Above". If the "Shift" is pretty, I find it a bit strange at first impresion and a less excepted behavior compare to a "Above" hovering for new user.

2) Cropped seem better. "Full" resize the cover without taking the ratio account, which is a bit strange, especialy compared to elsewhere in Calibre where the "keep ratio" is the default.

3) Always show the two line. Make it not optional if defined seem better, because the optional is to not write it.
And for resolve the the cache issue: since we know if a second line is here or not, rather change the min and max width in LayoutConstraints, maybe better to just append the second line height to 'min_spine_width' in the "get_spine_width().linear()". The max dimension is preserved, the cache is happy, and we still keep the variation for all the range.
I will look if can do a PR on that.

Else, thanks you for your work and responsiveness on this, a great pleasur.
And phew myself too, I will be able to return to a normal sleep cycle.

---
Else, about the commit 6012e77:
Nice, thanks. I didn't expect you to solve my such weird case.
...and them someone report a weird automatic size because he has vertical sreen in second monitor the ride never end (just my funny first throug when a see it )
Although, maybe a fix is possible, oh, I will look at it, else realy not critical.

[kovidgoyal]

Originally Posted by JSWolf

But if automatic was able to fix the shelves so when I stopped scrolling and made what's on screen show the full X number of shelves fully, that would work.

Automatic simply means the shelf height is calculated automatically, it has absolutely no bearing on scrolling behavior.

[kovidgoyal]

Originally Posted by JSWolf

It's slower to render graphics. It's more choppy to scroll the vewer if I do it fast enough.

This is scrolling in paged mode or flow mode?

[thiago.eec]

Originally Posted by kovidgoyal

@thiago.eec: Is your plugin using Qt WebEngine within the calibre process? If so it should not do so as this is not supported. It needs to launch a worker process, similar to how the ToC edit tool works in calibre.

I guess so. I think it runs in the gui thread:

self.browser = QWebEngineView()
self.browser.page().setHtml(month_html)
self.group_box2_layout.addWidget(self.browser)
self.browser.page().navigationRequested.connect(self.daily_pages_columns)

Also, I just noticed this is the same problem that another user ran into. I guess something changed in how 'self.browser.page().navigationRequested' works.

[kovidgoyal]

@thiago: You should really move it to process. But you can also try connecting navigationRequested via a queued connection

[kovidgoyal]

@JSWolf: Here's a tweak you can use to control GPU usage by webengine. I doubt it will make a difference, but...
https://github.com/kovidgoyal/calibr...ed8e4ae35467c7

[JSWolf]

Originally Posted by kovidgoyal

@JSWolf: Here's a tweak you can use to control GPU usage by webengine. I doubt it will make a difference, but...
https://github.com/kovidgoyal/calibr...ed8e4ae35467c7

Thank you. I'll try it when the next build is made.

[thiago.eec]

Originally Posted by kovidgoyal

@thiago: You should really move it to process. But you can also try connecting navigationRequested via a queued connection

I've PMed you.

[un_pogaz]

@Kovid, arh, I try to add my idea to append the second line height inside "get_spine_width().linear()", but is such a intricated things, I want to clarifed my idea so that you try on your side (and if I succeed before, sweet).

    def linear(f: float):
        return lc.min_spine_width + int(max(0, min(f, 1)) * (lc.max_spine_width - lc.min_spine_width - second_line_height))

[JSWolf]

I found what I hope will be an easy enough fix. I'd an option to make the settings in Bookshelf View to be global for the libraries I want. So for example, If I have library A, B, C, D, E. I want to be able to make changes in B and have them apply to C & D but not A or E.

[JSWolf]

Now for another fix. When I want to show the title and author. the auther is in the wrong place. The author should be under the title.

[BetterRed]

Windows 10 Pro 2022H2, calibre Portable 8.99.2

Look and Feel->Show layout buttons checked.

If I right-click on the Bookshelf icon in the status bar the Look and feel->Main interface dialogue pops, to be consistent it should pop the Look and feel->Bookshelf dialogue.

BR

[BetterRed]

The Group by item that's injected at the top of The context menu for the books in the calibre library in Bookshelf view should be optional, or be movable/deletable.

Even better, dispense with it in the booklist context menu, and have a Group by button in the Search bar, after the Sort by button. That would make it's visible to everyone.

BR