1
Stackz - New Feature Requests / Change to mark right/wrong
« on: July 06, 2006, 07:25:17 PM »
Firstoff, I know that this is a huge and probably useless one but I thought I could as well give an idea what can still be improved.
Okay, I am aware of the fact that it might not be the smartest idea to have like 7000 cards in one stack...but I still like it like that. Random reviewing without seperation is just the best for me.
But stacks is getting slower and slower in testing mode...to mark a card as known or unknown takes like 5 seconds on my machine. Maybe I'm an idiot but I think that this needn't be. After all it does not need to rewrite every sub-stack just because I answered one card. Sure this might be useful for people who want the graphic of the stacks to be updated after every card...but an option to update the stacks after more entries and doing it in the background might make it better. I mean it should be possible to instead of rewriting the two stacks that are influenced by answer, which I assume is what is wasting most performance atm, to just make a small memory area where it stores what is to go to which stack eventually and then when it has spare performance do it or do it more infrequently on larger stacks, or maybe some other way.
Okay, I am aware of the fact that it might not be the smartest idea to have like 7000 cards in one stack...but I still like it like that. Random reviewing without seperation is just the best for me.
But stacks is getting slower and slower in testing mode...to mark a card as known or unknown takes like 5 seconds on my machine. Maybe I'm an idiot but I think that this needn't be. After all it does not need to rewrite every sub-stack just because I answered one card. Sure this might be useful for people who want the graphic of the stacks to be updated after every card...but an option to update the stacks after more entries and doing it in the background might make it better. I mean it should be possible to instead of rewriting the two stacks that are influenced by answer, which I assume is what is wasting most performance atm, to just make a small memory area where it stores what is to go to which stack eventually and then when it has spare performance do it or do it more infrequently on larger stacks, or maybe some other way.