I noticed the new introduced search keyword doesn’t appear in the changelog. Might be relevant for some users, so I just thought I’d mention it here.
Import CSV file is not importing the cards in the right deck.
- Create an empty deck, “test_deck”
- File > Import > any CSV
- Choose “test_deck” as destination > import
- The cards will be imported in a new “default” deck. “test_deck” is empty.
Everything is working as expected in 2.1.44
I have had many people complaining that the review heatmap add-on “doesn’t work” on newer versions because it counts way too much. It appears that it is also counting cards that are rescheduled with the “set due date” function.
On that note, it may be helpful to make it so that the “rated” function could do “rated:1:0” so that these can be included or excluded. On the same note, some may consider it helpful to add to the new “introduced” feature (which is awesome by the way!)
@dae I would also still recommend adding “leech” and “marked” to the top of the sidebar rather than buried in the tags based on what users have told me
2 Likes
Review Heatmap is not built upon rated:, it has built its own query to search for reviews. rated: already excludes rescheduled cards. You can search for rescheduled cards with resched:.
Review Heatmap could be updated to use rated: and prop:rated= instead. In fact, when I changed the implementation of rated and introduced resched:, I was thinking of use cases like Review Heatmap.
@hengiesel I forgot about resched! @dae I would recommend adding little things like this to the sidebar. It is far more user friendly and then users (even advanced users like myself) don’t have to go searching through the manual. I think this works well enough because you can add in resched cards or remove them using the resched
Are there any other search terms that should be added to the top sidebar besides leech, marked, resched? Perhaps a “card properties” section with prop:ivl,reps,lapses, and ease?
@glutanimate This change was introduced in a stable release almost 6 months ago, and fixing it should be as simple as ignoring revlog entries with ease < 1. Could you look into it when you have a chance, please?
And to clarify, rated:/resched: are not useful for fixing the issue - if the add-on were using Anki’s search code to determine the counts for each day, it would be very slow. They are useful if a user clicks on a given day to search for it though.
“Rescheduled” fits nicely in the existing “Today” category, so that’ll be in the next build. I’m not so sure about the others - marked and leech may not be used by some people, and they can now easily be dragged onto the saved searches area if a user finds themselves accessing them frequently. Prop searches are fairly advanced, and typically the user will want to vary the operator and the number of days, so I’m not sure whether they should really be on the sidebar by default.
1 Like
@dae I would recommend it simply so that users do not have to go to the manual to search for them every time (which is what I do because I use them quite infrequently). Perhaps a top menu item that allows users to “toggle on advanced” functions or just listing them closer to the bottom would be helpful? I do think you’re right that the average user won’t access them that frequently
For marked and leech, I think users do use those quite a bit more often. Would it work to have them as a saved search by default and that way users could delete them if wanted? Personally it’s quite easy for me to access from the tags, but like I said I have had many people already email me about them (likely because the customize sidebar add-on put them at the top and that’s what they were used to?)
@dae just found an error in the special fields add-on. Any chance this can be easily fixed?
Caught exception:
Traceback (most recent call last):
File “/Users/Nick/Library/Application Support/Anki2/addons21/1102281552/dialog.py”, line 361, in onFields
FieldDialog(mw, fields, parent=self)
File “/Users/Nick/Library/Application Support/Anki2/addons21/1102281552/dialog.py”, line 67, in init
self.form.sticky.setParent(None)
AttributeError: ‘Ui_Dialog’ object has no attribute ‘sticky’
@dae, a couple of suggestions, just in case you want to consider for 2.1.45:
- Add “Info card” to the Options menu, which I think is a logical and useful place to be.
- Group related options from that menu.
The add-on is referencing this removed setting:
So it has to be updated, but the fix should be as trivial as deleting the line self.form.sticky.setParent(None).
@Rumo the current line is already
self.form.sticky.setParent(None). It’s for a new dialog (not the one you referenced) but it does remove that button in the new dialog. Haven’t had any issues till this version
The add-on is repurposing the native Anki dialogue from cqg’s screenshot. The error is thrown because it’s trying to remove a button that doesn’t exist anymore.
Not sure what you mean by “the current line is already self.form.sticky.setParent(None).” It has to be removed.
When I remove it I get this funky formatting now:
I don’t understand why it was there in the first place… but if I remove that line and go to 2.1.44, then I do get a “remember last input when adding” button. When I then view it on 2.1.45, I get the image above. Simple fix perhaps. If that button isn’t going to exist anymore, then do I just need to have someone update the special fields add-on? (seems like it may just be a cosmetic thing)
Yes, it’s only cosmetics. The problem is that the add-on relies on an existing form in Anki and when this form changes, the dialogue’s layout breaks.
The author probably had their reason to do it this way, but if the add-on was shipped with its own form, it wouldn’t break as easily.
1 Like
I will make a case here for marked at the top of the sidebar. That’s something that I always wanted to say. Let’s think through the eyes of the new user:
-
he makes his first basic notes: Oh, I can tag cards (at this point, he still doesn’t know the difference between notes and cards).
-
he starts studying: Oh, I can also flag and star each card too. So, I can mark each card in 3 different ways. Nice.
-
he makes his first visit to the browser: I see my flagged cards. I see my tagged cards. But, where is that pretty little star?
(true story)
So, my suggestion is that there should be a separate category, in the top of the sidebar, for marked cards, with a Star by the side of it. When people put a Star in the card, they expect to find a Star in the browser.
Flags are way less used (I think), but they are there, at the top, with actual little colorful flags.
BR,
2 Likes
+1 on that!
I can only repeat what I have proposed a while ago:
It always felt wrong to see marked and leech somewhere within the normal tags.
2 Likes
And it gets worse when the person is using Anki in a language in which “Mark Note” (as seen when marking the card) translates to something that doesn’t ressamble the word “marked”. So the italian user:
-when studying: Contrassegna nota (Mark note)
-wants to find his “Contrassegna nota” (or something similar) in the browser; finds the tag “marked”: Ma chi è Mark (But, who is Mark)?
Italian fellows, please confirm.
The same happens in other languages.
Making ‘marked’ a default saved search will mean it’s the first thing seen by a user, and I don’t really think it is used enough to justify such prominent placement. When flags were introduced, they were originally intended to replace marking completely, and while marking has remained, most users should find flags cover their use cases.
Making it into a saved search also means it won’t be able to change when the interface language is adjusted.
Placing it and leech at the top of Tags means everyone is forced to see them even if they don’t use them, and some people have already complained about the presence of Untagged. Maybe one alternative would be to change “Untagged” to “Builtin”, and nest Untagged along with Leech and Marked there, as children. Would that work for people?
Perhaps just add a “card properties” beneath tags for less used things? I have always thought mixing leech and marked in with tags was strange as it feels like a flag or something controlled by anki and the tags feel more like user-added. I will also add that most users I talk with are still using marked and leech. I frequently get questions about those functions (at least 4-5x/wk)
The biggest complaint I hear from new users is that they can’t find things or that anki isn’t user friendly (I’m talking 100s of complaints). That is why I continue to suggest making things more organized and available from within anki and not just the manual. I do recognize it means more maintenance for you so I’m not specific about where or how they are located, as long as it’s reasonably accessible.
1 Like
Sounds better than “Builtin” (easier to understand for non-native-speakers like me).
I’d put it right above “Tags” though, not beneath, because most of the time the hierarchy will be expanded.
1 Like