Hi world, here is the support page about everything Auto open deck at launch add-on https://ankiweb.net/shared/info/425258424
1 Like
V1.2 updated!
This version has been adapted to safer initiation steps, making the plugin more compatible with other extensions. Added automatic advancing between decks (toggleable), and removed the queue limit.
- Known issue: Deck queue auto-advancing only works when you enter the deck using this extension. The button on the completed page is currently a placeholder.
I probably won’t have time to update this extension for the next few weeks unless there are critical errors. Meanwhile, please feel free to leave comments and suggestions in this thread!
How does this add-on work with empty filtered decks in the queue?
If it directly continues to the next deck, can it be instead changed such that an pop-up is shown asking whether to continue to the next deck in queue or to rebuild the deck?
When opening Anki, there is a considerable time delay in comparison to the regular one. Is there a way to minimize this delay?
When I updated the add-on, it erased the currently set decks, and uses a queue of your decks (presumably). I think it’d be better if you can have the decks part be saved and not modified when updating an add-on (if it is the case that the entire config.json file cannot be retained).
When a larger number of decks are there in the queue, the deck queue part should become a scrollable part, rather than increasing the size of the window. I think 10 or 15 is a good limit for the number of decks in queue after which scrolling should activate. Once a new slot is added, some space is added to accommodate the new slot and if you subsequently remove a slot, the space still remains. If slots are removed and there is less than the scroll-limit, it’d be better to decrease the height of the window.
If the user has a large number of decks, it gets slightly inconvenient to search for a particular deck. Maybe you could include deck selector search similar to the Change Deck one?
Hi, Nice catch! This is my first plugin and I was unfamiliar with config saving. This feels like a critical error for me, so I updated again. Also, the filtered deck is very cool, I don’t even know it existed. Hopefully this update fix your issues as I really can’t spend more time on this for now lol.
V1.3: Better handling for filtered deck. Better UI. Button and timer fixed. New save system that hopefully won’t overwrite users’ settings each update. Slightly faster open time.
1 Like
No worries, you can implement things at your own pace. You don’t need to take out time to push updates unless you want to.
Thanks a lot for implementing a quick fix. I had a bit of fun learning Python and how the add-ons work (thanks a lot for your comments, they did help a bunch).
I think the open time is actually an issue from my side, apologies on that. I seem to have misattributed it to this add-on, something else is causing it.
One small issue is that since add-ons apply to each profile, they will act on other profiles also.
I somehow managed to create a menu in the Tools menu to instead start the deck queue on command and a toggle to not run on profile open, as I do change profiles a bit to test stuff out and it’s rather inconvenient for me. Should I include that code here or will you add it yourself in the next update? (No rush, take your time. If anything is that needed for me, I’ll try asking other people out who have a bit of experience with this stuff)
The config file doesn’t seem to be being saved, some error perhaps? If I select the decks inside Anki and then restart Anki, it seems to be working, but if I manually go to the config.json file, it seems to not be updated.
I see what you are trying to do. Custom saving to profiles is a cool feature. I almost went this route, but got lazy again. Lucky, the AI one-shot it, so I updated this feature in V1.4. The button for starting a deck queue is a great idea and solved a big issue that it could only be reinitiated by restarting Anki.
This extension is all AI-coded, so please take its code with a grain of salt. The config problem you have is probably because the settings were saved to meta.json, while the config.json was used to hold default values. Now the configs are saved in Anki2[profile name]\config\425258424.json
I’m getting into coding, so this extension is a cool practice project. Thanks again for your support with debugging and bringing out all the use cases I didn’t consider. My anki use was extremely simple with one profile and one huge deck, but I’m glad that with your feedbacks this add-on could now support power users as well.
1 Like