Actually, I had to think for more than 1 minute to figure out whether
your suggested tooltips really matched how it is implemented in all
possible corner cases, and I did not arrive to a conclusion :-)
So, that seems like a pretty good argument to me for getting rid of
that option :-)
Since beta 1 came out (last September?) nobody ever complained about
the default *behaviour* of that option. There only was a very valid
remark last week that the *description* of that option not matches the
reality very well, but as far as I recall, the default behaviour was
OK for that person.
Thanks for the feedback!
Peter
Quoting Gnome <[email protected]>:
P.S. I think it would be nice to add a message explaining the expected
behavior when the button is set to disabled also.
"You have disabled to relearn sister cards on the same day.
Sister cards will not be shown until you have learned all the cards in
the 'Not memorized' que"
"You have enabled '(Re)learn sister cards on the same day'
Sister cards will be added to your schedule, when you are done with
your daily schedule."
P.S PS:
I'm not sure what behavior I'm actually getting when it comes to
sister cards as a user. Most of the times I think I'm getting the
sister cards (both sides) during learning, or not? :P
On 11 Mai, 22:30, Gnome <[email protected]> wrote:
I'm voting for to leave the button as it is, but add a message box
when you activate it to explain expected behavior.
I think many people may get a bit baffled when their the sister card
is not shown until the end when all cards has been memorized, and may
leave lots questions on it on the forums.
On 10 Mai, 21:26, Peter Bienstman <[email protected]> wrote:
> Mnemosyne currently has a configuration option '(Re)learn sister cards on
> the same day'. However, it's very misleading in the sense that as soon as
> you are running out of new cards to study, Mnemosyne will bring these
> sister cards into the queue to prevent it from running empty. In RC1, I've
> added a warning message to explain that this is happening, but
it's proving
> difficult to prevent it from triggering spuriously.
> So now I'm currently leaning towards removing that configuration option
> altogether and taking the behaviour when this box was unchecked.
This means
> that when learning new cards, Mnemosyne will avoid showing you sister
> cards, unless you are running out of new cards. I'm not sure that
> preventing you from trying to learn the production card when you have
> memorised the recognition card is all that important, and people could get
> confused if they see the 'not memorised' counter non-zero, but
still get no
> new cards to study. Sure, you could give a warning message in
that case, or
> make the behaviour configurable, but I feel that then we're just replacing
> one combination of a confusing, difficult to understand setting
and warning
> message with a different combination of confusing, difficult to understand
> setting and warning message..
> Thoughts?
> Peter
--
You received this message because you are subscribed to the Google
Groups "mnemosyne-proj-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/mnemosyne-proj-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
"mnemosyne-proj-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/mnemosyne-proj-users?hl=en.
