I’m not the only one who would benefit from an undo button, nor am I someone who wouldn’t benefit from the button being moved. Or maybe I didn’t read that correctly.
Anyway, I would be totally grateful if the button is moved; it was even one of my suggestions (others also suggested it), and I think it would make this whole problem pretty much go away. It’s a great idea!
Thanks again for taking the time to consider everyone’s feedback on this issue.
This behaviour is one of the reasons I’ve cancelled my premium membership.
This plus the response to this simple request is why I won’t be resubscribing with a new account, like I had planned.
I have far too many known words that I don’t know, making my LingQ near unusable for learning. I tried resetting one language, but it deleted all the words, rather than setting them all to blue.
So I decided to create a new account, where I could start afresh without paging marking everything as known, and use LingQ the way that I want to, as we are encouraged to do.
Now I find that one misclick, or forgetting a button’s unobvious behaviour, will make a mess of my account again. And that this will never be fixed. Not even with a check box, like paging has been.
LingQ has great features, but it’s also really frustrating to use. I could live with that when I had hope the frustrations would improve. I’m not sure I can now.
This is still broken.
It’s a bug if users don’t want it.
It’s a bug if it is unintented behaviour, which isn’t the case. It is however an annoyance to ignore a simple and reasonable fix - moving the lesson finished button to a different spot as opposed to the next page button.
If you want to intentionally close a lesson without the remaining words beeing marked as known, you can use the cross in the upper left corner (on Desktop, in the app the position may differ).
It doesn’t reflect customer wishes. It doesn’t work as it should. a main problem is the unintentional action during normal clicking action.
It has just added 100 words to my tally because of the stupid end of lesson buttons. On a tablet, the next lesson and end screen are in the same place.
Place stop this awful function of adding words at the end of a lesson, assuming they are known.
Please remove the additional words.
@bbbblinq Sorry but it’s not possible to undo this. You can go through a lesson, select white words you don’t know and save them as LingQs instead.
I’ve used the app for about a week now, but this is turning out to be a deal breaker for me and I don’t plan to extend my subscription until a checkbox is added to turn this off.
I’m trying to learn Tagalog, and I want to open up long and complicated literature (e.g. Jose Rizal’s “Noli Me Tangere”) and explore for any words I partially recognize (e.g. conjugations and contractions of words I already know) then I can go back to more intermediate lessons (e.g. news articles) and have a better sense of the words and sentences I should reasonably be expected to understand.
And you can’t just can’t not finish the lesson when inspecting those lessons? I don’t see how that could possibly be a dealbreaker.
Have you unchecked “paging moves to known” in the settings ?
On the web app, if you accidentally click on the completion checkmark, you’ll get a warning telling you that all blue words will be moved to known.
On ios or Android, you have a “finish lesson” button. Just don’t click on it.
Every new word either becomes known or becomes a LingQ. This is 100% the essence of LingQ and what makes it unique. Words are not meant to be left hanging.
Tell me more about this extension, please.
read for a bit and then checked my total logged reading on LingQ, recorded as 322 words read. I then put this exact text on a Word document (set to my target language), which indicated that the text included 1,114 words.
LingQ counts unique words, not repeated words. That’s why.
Use a unique word count website instead.
Thanks for mentioning that, I think that can work for me. I had a lesson marked as “complete” yesterday and the warning didn’t show up, so I assumed that was the design.
I don’t have Rooster installed, but nevertheless I get the warning, which SeoulMate mentioned.
I get the warning most of the time, but had at least 2 occourences were the warning was not displayed despite some blue words left. I wanted to end the lesson, so no harm was done, but it would be good if it would work reliable and for everyone, of course.
Having to compensate for bad softare is a sign of a bug, not a feature.