A minor issue with the Browse screen. Not sure if it’s a bug or a feature, anyway here it goes:
Another minor, cosmetical issue when removing a preset from the deck options:
Also something that maybe you want to consider: if you press OK in that dialog to confirm that you want to delete it, the preset is supposedly removed, and a new deck option preset is automatically assigned to your deck:
That’s because the search line has focus and captures these key strokes. You can press Ctrl+Shift+L to move focus to the table.
Yes, you’re right, but don’t you think that no card should be shown as selected by default then?
The newer sidebar has tags with ^ in front listed near the top now vs down at the bottom like previously. Is there any reason for that change? It was kind of nice to have certain characters push tags to the bottom while other characters pushed them to the top. Any chance that could be reverted to the previous method?
-Sincerely someone using thousands of tags in a shared deck with 50k cards 
(for reference @dae since I believe you asked a while back, there are over 100,000 downloads of the deck for medical students so far)
I suddenly received this dialog today while reviewing, for the first time. After clicking OK, everything worked as usual.
Debug info:
Anki 2.1.45 (6ffa7440) Python 3.8.6 Qt 5.14.2 PyQt 5.14.2 Platform: Windows 10 Flags: frz=True ao=True sv=2 Add-ons, last update check: 2021-07-05 21:53:15 ===Add-ons (active)=== (add-on provided name [Add-on folder, installed at, version, is config changed]) Anki Persistence ['1051511270', 2020-09-01T21:32, 'None', ''] Asset Manager ['656021484', 2021-04-05T22:24, 'None', ''] Closet For Anki ['272311064', 2021-04-12T16:09, 'None', ''] ===IDs of active AnkiWeb add-ons=== 1051511270 272311064 656021484 ===Add-ons (inactive)=== (add-on provided name [Add-on folder, installed at, version, is config changed])
I guess that depends on your personal workflow. Since it has always been like this, I wouldn’t change it lightly.
Beta 6: I have a collection with the v1 scheduler (it still shows the “Anki 2.1 comes with a new scheduler…” infobox). When I try to import an apkg (also v1) it gives me this error:
Import fehlgeschlagen. Die Fehlermeldung lautet:
Traceback (most recent call last):
File “aqt\importing.py”, line 394, in on_done
File “concurrent\futures_base.py”, line 432, in result
File “concurrent\futures_base.py”, line 388, in __get_result
File “concurrent\futures\thread.py”, line 57, in run
File “anki\importing\apkg.py”, line 46, in run
File “anki\importing\anki2.py”, line 41, in run
File “anki\importing\anki2.py”, line 61, in _prepareFiles
Exception: must upgrade to new scheduler to import this file
Is this what’s supposed to happen? I’m pretty sure this would confuse many users who try to import old decks.
“Queue test1 up for removal on save?” might more closely convey what actually happens, but I wonder whether the extra wordiness is a net gain or not.
The ‘selected and focused’ colour and ‘selected but not focused’ colours are quite similar, and there is perhaps scope to make them a bit easier to distinguish, but I vaguely recall years ago that having a grey ‘not focused’ state looked bad or interfered with the colours of things like suspended cards.
.35 seems to sort in the same way - maybe you were using an add-on that sorted differently? Changing the behaviour of ^ is not practical, sorry, as we’re relying on unicode sort order.
I suspect you managed to send through two answers for the same card - maybe when you pressed one of the answer keys, your keyboard registered two taps? I can’t seem to reproduce it by hammering the keyboard, but can if I programmatically trigger two answers for the same card.
While the message could be improved, you should only be seeing it if you try to import a v2 scheduler deck exported with scheduling into a v1 collection. If you’re sure you did not export it with v2 active, maybe you have an add-on that is interfering with things, as Anki will assume it’s v1 if the caller is monkey-patched.
Yes, that could be confusing. I personally would expect Anki to actually remove the deck option after asking for removing confirmation, no matter if changes are saved afterwards or not.
No changes are made until you click on Save - I would have thought that more logical than some changes requiring a save and some not. The behaviour is consistent with the card layout screen and means any changes you made can be undone in one go. It’s not how the old deck options screen behaved however, and perhaps that’s why you’re expecting it to behave differently?
Must be an OS thing, because I don’t see any different colours. The focused cell has a dotted outline, that seems to be the only clue that focus is on the table widget.
While the message could be improved, you should only be seeing it if you try to import a v2 scheduler deck exported with scheduling into a v1 collection. If you’re sure you did not export it with v2 active, maybe you have an add-on that is interfering with things, as Anki will assume it’s v1 if the caller is monkey-patched.
I disabled all addons and tried again, same error. I even tried importing a deck that I just exported from the same v1 collection and got the error, so this seems to be a bug.
As for a less scary message I would suggest something like this:
The deck you are trying to import uses the v2 scheduler while your Anki collection still uses the v1 scheduler. In order to import the deck you must first upgrade your collection to the v2 scheduler as well. You can do so by clicking “Update” in the grey info box displayed in the main menu.
I’ve just submitted a fix.
I expect a program to delete a option if I click on “delete”, the program asks for confirmation and I click “yes”. I find the contrary kind of weird. But in this case, as stated previously, things are a little bit more complex, that’s right.
In any case, it’s not really a problem at all, it was just a simple comment / suggestion that can be safely ignored 
Thanks for persisting, this should be fixed in the next beta.
Appreciate the feedback, just think in this case what we have currently might be the least-bad option - if confirmation were delayed to the end, users could end up making other changes that get reverted if they decide to abort the full sync.
Aftersome time using 2.1.45, I have to say that I’m still finding some aspects of the new deck options window a little bit confusing, particulary, when using a complex estructure of decks and subdecks , each with different deck settings.
I tried to explain it here:
Probaby I’m still missing something here, but trying to figure out which settings apply only to the parent / actual deck and which ones applies to the parent deck AND its subdecks requires a lot of experimentation through trial and error and it’s, in my opinion, one of the most confusing aspects of the GUI.
For example, let’s say we are studyng this whole set (Deck A):
Deck A (Deck optionsA)
-SubdeckA1 (Deck OptionsB)
-SubdeckA2 (Deck OptionsC)
…
In that case, will New card gather priority / New card sort order values from DeckoptionsA override the New card gather priority / New card sort order values from DeckoptionsB and C?
A couple more suggestions:
While technically correct, I honestly think that 90% of Anki users don’t really know what “Position (lowest first)” really means in Anki terms. I find “Oldest first” or “Position (Older first)” -even if not 100% accurate- much more user friendly and intuitive terms.
Add a “Random” option to the previous settings. That would make a very common user request (pick new cards from ALL the subdecks randomly) much easier, without the need of setting limits separately for each subdeck.
Put a “Help” button (like on 2.1.44) on the deck option windows and add examples to the help page. I understand that the corresponding help page is still under construction and doesn’t reflect the new changes, but since the deck options window is really the core of the program -at least, from the user perspective-, I think that its help page deserves a complete overhaul, maybe with the addtion of examples ilustrating the use of each settings in different scenarios (simple deck, deck > subdeck, etc…). I will be happy to help if help is necessary.
https://docs.ankiweb.net/deck-options.html
Not omplaining, the new features are terrific, and scheduler v3 is definitely a great imrpovement over v2.1, It’s just I think there is still some room for improvement in the GUI area.
Anyway, thanks as always for considering! 
I have to disagree. If I choose “oldest first”, and then am not shown the oldest cards first (because “lowest” isn’t equivalent to “oldest”), that isn’t user-friendly at all. Also, the concept of Position is explained under Insertion Order.
@dae is this an error that can be fixed? Batch editor is no longer working
Caught exception:
Traceback (most recent call last):
File “/Users/Nick/Library/Application Support/Anki2/addons21/291119185/main.py”, line 107, in
lambda state, x=“replace”: self.onConfirm(x))
File “/Users/Nick/Library/Application Support/Anki2/addons21/291119185/main.py”, line 186, in onConfirm
batchEditNotes(browser, mode, nids, fld, text, isHtml=isHtml)
File “/Users/Nick/Library/Application Support/Anki2/addons21/291119185/main.py”, line 197, in batchEditNotes
browser.model.beginReset()
AttributeError: ‘Browser’ object has no attribute ‘model’
