The Stackz Concept > Stackz - Solved Issues
The Back button in the Learn dialogue
James:
Yes, I share the same concern -
The problem occurs when using the undo button in a learn dialogue that has not been completely initialized.?
In such a case the undo button undoes the last classification and brings that entry back to the local stack.
When this happens, if the local stack has not reached its max size (ie not completely initialized), the entry is ADDED to the local stack rather than replacing the entry that followed it. The result is that the local stack increases in size by one, and the user has no opportunity to correctly classifty the second-last entry as "known".
This is a really challenging problem to explain. >:(
Basically if you put 5 or so cards in the local stack (assuming your max setting is 10 ) and try playing around with the undo button, you'll soon see what we mean.
Cheers.
Chris:
Ah NOW I see what you mean!? :o Sorry for the misinterpretation.
The undo action takes the focus away from the entry that was inserted during the erroneous declaration action.
This lost focus turns it to a "not allowed to declare as known" state!
Detail description:
On PocketStackz, after an erroneous declaration, the undo action adds the previously declared entry ("A") back to the local stack, without removing the entry that replaced it during the erroneous declaration ("B"). After the undo action, "A" is selected in the list and its attributes are displayed. When the new entry "B" then is selected, the "declare as known" button is disabled for this entry because it is selected for the second time now, and "declare as known" is only permitted at the first selection to avoid positive declarations out of an iterative learning session.
We will try to find a solution to this problem.
In the meantime, the entries that are added before an undo action can't be declared as known in a learning session indeed. They are best put back on the same stack instead, which does not alter their statistics. Note that another session can be started directly afterwards to catch up on classifying the missed entries, a test session would be more appropriate than a learn session in this case.
Chris:
--- Quote from: bkzk7188 on September 12, 2006, 04:50:51 PM ---1) Entry B is declared as unknown, and stays at #13.
--- End quote ---
To "declare as unknown" means "re-classify the entry by moving it to a different stack on the left".
If an entry is declared as unknown, it leaves the learn dialog.
An entry can't be declared as unknown and stay in the dialog in the same time. According to my previous post, you probably mean "Entry B stays at #13 and is not allowed to be declared as known anymore".
Konstantin:
--- Quote from: bkzk7188 on September 12, 2006, 04:50:51 PM ---I'll try to explain it once again.
--- End quote ---
It was really hard to understand the problem.
I hope now we have a solution.
I've made a bug-fix release and put it to the server.
You can find it here:
http://www.stackz.com/Stackz/ppc/ppc.htm#Download
Could you please check whether it really fixes the problem you meant?
Thanks,
Konstantin
James:
Sorry my ppc has died >:( and I am unable to test.
Anyway the issue I was describing occurs in the learn dialogue in the desktop version.
It sounded like the same problem as the person who started this thread but perhaps it isn't :-\
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version