Anki 2.1.57 Beta

Hi all,

A new beta is available: Changes in 2.1.57 - Anki Betas

12 Likes

anki
Anki starting…
Initial setup…
Traceback (most recent call last):
File “”, line 1, in
File “aqt”, line 40, in
File “anki.lang”, line 12, in
File “anki._backend”, line 14, in
ImportError: libssl.so.1.1: cannot open shared object file: No such file or directory
~/anki-2.1.57-linux-qt6 >

Dang. Not a permission issue; I’ve pushed a new build that should fix it.

1 Like

Thanks for the release! Lots of cool new features.

Windows10 qt6

  • Light mode only: when I use background-image in the CSS, there is always a ~ 55 px bar at the bottom of the card which seems not to be affected by the styling (showing instead the card’s background color).


  • Card styling: I cannot seem to apply my own CSS to buttons of the type <button></button> unless I use !important (e.g. button {border-radius: 5px !important;})

  • Is the new color scheme of the template editor an intentional design choice? My first impression is that the 2.1.56 look worked better, as it was simpler and less dashing. But again, it’s probably mostly a matter of habit.

  • When opening the Add window, there is always an interval of 1-2 seconds (the add window opens a bit slowly on my computer) in which the focus seems to be on the “choose note type” button. I find it more curious than anything.

  • Lastly: maybe the reviewer’s bottom bar could use a couple more pixels of padding?

4 Likes

:rocket: really nice work everyone, and particular thanks to @kleinerpirat for all the toolbar & preferences tweaking

I think I would tend to agree. Seeing both next to each other, it seems like the 2.1.56 widget styling created slightly better contrast between editable areas and surrounding UI. But it’s also not a drastic difference IMHO.

4 Likes

I will push a PR that will ensure the reviewer CSS is unaffected by the button styles.

Nope. That was a side-effect of styling QGroupBox for the preferences screen. Since it’s also used in the template editor, I’ll have to either make the styling specific to the preferences or use a different layout in the template editor.

  • When opening the Add window, there is always an interval of 1-2 seconds (the add window opens a bit slowly on my computer) in which the focus seems to be on the “choose note type” button. I find it more curious than anything.

The first field only gets focus once the webview is done loading, hence the delay. This has always been like that, but this update brings a few Qt stylesheet additions to show button states. I might have overdone the focus indication a bit.

If you check on a version below 2.1.55, it should also show that behaviour, although with less prominent focus styling.

Yeah, that’s something that’s been bugging me too. The other design changes were higher priority, so I pushed the issue back a bit.

3 Likes

A post was split to a new topic: Wrong info when hovering over future due graph?

Thanks for the new beta. I really like the new UI changes.

Two issues I’ve encountered during a quick look around. Firstly, spacing around the section headers on the note-type editor seems off:

Secondly, there seems to be a string in the german translation which includes a duplicate html tag:

1 Like

I like that the toolbar background changes along with the card background now!

One minor remark: the Style option in the Preferences should maybe be hidden if it’s not applicable for the OS? On my Windows pc, it just shows up as a label without an option.

2 Likes

@dae I removed the bold tags from the original translation, because it’s not needed for the QGroupBox title. Will this show up as a new task for the translators or is changing an existing string a no-go and I should have named it differently?

I wonder how it is possible that I haven’t (almost) yet come across plugins that were broken by the move?

When you change the wording of a string without changing its name, the translators don’t get notified. I didn’t realise you’d moved the string outside of a HTML-supporting QLabel - probably best to create a new key in this case.

We can thank @glutanimate for that :slight_smile:

He made sure existing add-ons are compatible with the reworked toolbar and also made it easier for add-on authors to add their own buttons.

PR: Fix toolbar add-on breakages and introduce toolbar tray layout & API by glutanimate · Pull Request #2301 · ankitects/anki · GitHub

5 Likes
  • The top toolbar area can now take on the color/background of the main window.

Is there a setting for color/background that I missed, or does this mean with an addon like Custom Background Image and Gear Addon?

Is something missing here in style?

1 Like
1 Like

I forgot about that label, a PR is already pending :slight_smile:

2 Likes

The toolbar checks the main webview’s body and copies its background (e.g. templates that set a background-image on .card). If I remember correctly, that add-on sets the background on the Qt widgets themselves, so that won’t work.

I’ve been working on a PR to support background images natively though.

2 Likes

I would prefer the bar not to linger so long down. You have to return to your place after a second / a second and a half

I once reduced it to 1s and it felt a bit hectic to me. Currently it is at 2s. We can increase it to 1.5s for the next beta to let the community judge what’s best.