Shifting your add-on development discussion from Browser: Add a column for flags.
[If you want to make your own thread for this, I can move your discussion there instead.]
3 Likes
This makes it easy to see a card’s suspension or buried status without relying on other columns when flagged.
But this doesn’t solve the problem of viewing the current row. It’s always blue on Windows 10, for sure.
And it would be good to make the column always visible, regardless of scrolling…or better yet, two columns, if you want to finish the add-on.
This is actually a great idea. I’ll work on this.
1 Like
Can you elaborate on the “two columns” idea?
The flag is already there, just for visual color. But what if we use a different icon, just to show whether the map is “suspended” or “buried.” Unfortunately, there’s still one more color: maps tagged “marked.”
This addon attempts to solve all these problems: Advanced Browser - mod kaiu 2026
Ah, I see. Yes, because selection is a transient interaction state, and suspension is a semantic status, they shouldn’t visually override each other… I think two columns could become visually busy and hard to parse at a glance, but I’ll try it as well as some other ideas I have soon…
1 Like
Thank you. Perhaps management will like something and want to do the same without add-ons. I hope so, but so far I see that nothing is changing that quickly.
But users will have a choice, which is very good.
Thanks again for your time.
You can try it this way. I don’t know if people like it. I at least like that the color is visible.
I like the two-column idea… the problem is many things can change color. The one’s I’ve thought of so far are:
- suspension status
- marked status
- buried status
So, we would potentially have to make 3 new columns (4 columns total) to encapsulate all these possibilities…
Any thoughts?
suspension OR buried
You can’t have both, so there can be 2 columns.
You’re the author, so you can see for yourself. You could even set up a vote later. But I don’t see many people even giving it a like. So it should be primarily up to you or your group, if you have one.
Interesting and beautiful. If there’s an option to make the column always visible, I think it would be very nice.
I updated the Anki addon to support these new features. They are disabled by default, though, so as to not upset users who may update.
You can go to Tools > Flag Column Settings… to enable the states, though.
Let me know what you think!
2 Likes
When scrolling, this shift occurs. Initially, the border thickness for your columns is the same as here, but after scrolling down the screen, the thickness changes. This results in a height error that constantly accumulates.
The selection border is a bit thick. And if you select a cell and move across a row to another column, visibility disappears.
Perhaps this isn’t the case for you; I understand you’re on MacOSX.
If at least everything works fine for you, well, I could write about it.
I don’t know about other systems either; I’m only on Windows 10. And it doesn’t work well with the “Advanced Browser - mod kaiu 2026” add-on, but that’s okay. At least make it work properly on its own, and we’ll figure out compatibility later.
It seems simple, but I see code already running at 1,500 lines or more. Yes, such seemingly simple things take a lot of time and effort, and often it’s testing, not coding. With this AI, we’ve all become testers, not programmers, because it can throw out a lot of code, but its quality needs to be checked and modified repeatedly.
1 Like
Oh no… funny enough, this code originally wasn’t very long, but getting the borders and sticky columns to work required a lot of Codex… and it eventually ended up working on my Mac. I wasn’t aware it wouldn’t work in Windows… I might have to try to approach this entirely differently.
My idea at the moment is to simplify the addon and remove the border selection style. It will only be “classic” but the state icons should do the job (i.e., you can still see the ! for suspended even if you select the row). Unless you think “border” selection style is essential…?
I also want to completely rewrite the sticky column logic, but I’m not sure how at the moment… I’ll try some ideas later.
1 Like
It’s all up to you. If anyone really needs it, let them finish it if they can 
I’m not the client, making demands. You do what you like and what you see as right.
That’s why group development is so difficult, because it requires lengthy discussions and it’s very difficult to find a solution that satisfies everyone. Alone, you could recreate or rework the entire Anki I’m kidding, not everyone has the time for a year, and then maintain it. At the very least, I need to find the time and energy to maintain the add-on, and I’m not that young or that healthy anymore. Maybe one day, AI will be cheaper (than a programmer) and will be able to create a fully finished product in a month. Then, you could task the AI ​​with analyzing the source code, and it could even improve the entire Anki
Hahaha that’s actually very encouraging, thank you. It’s definitely a fun thing to do on the side, but I’m still in medical school so it does get a little busy!
I just did a refactor with GPT 5.4 and it’s actually… really good. I gave it some Anki source code for the Browser and it seemed to find a better way to implement it than I did. I updated the addon on AnkiWeb. The border is still thick, but I couldn’t find any bugs on macOS (except on the settings preview window, which is fine for now).
It seems to be working better. I’ve noticed fewer lags. But 666 seems to have some effect. I can’t figure out what it is, other than the influence of the mystical 666. It doesn’t make the frame lower. Everything works fine in other decks.
Then there’s group selection. It’s fine for notes. Not for cards anymore.
That version worked more or less with group selection. I still have the code, so I can compare.
So, I’m saying the AI ​​generates code, but is it optimal? I haven’t trusted it to change the code for a long time. Only minimal ideas, and the rest must be done manually.