Open GoogleCodeExporter opened 9 years ago
Issue 373 has been merged into this issue.
Original comment by dpra...@gmail.com
on 25 Nov 2012 at 11:36
Fixed at revision r166
Word count is now updated only after a short period of user inactivity (450 ms)
and this is periodically checked every 2 seconds.
Original comment by dpra...@gmail.com
on 28 Nov 2012 at 10:33
I have just released a new version of KeyNote NF: 1.7.9 Beta 4
Could you verify and confirm if the issues are correctly resolved?
Thanks
Daniel
Original comment by dpra...@gmail.com
on 7 Jan 2013 at 7:43
Tested it in 1.7.9b4
The word count is not working at all now. When the option is turned on, the
word count from the last selection remains visible, but there is no live update
of total word count while you type.
Original comment by krommen...@gmail.com
on 8 Jan 2013 at 4:01
Hello krommenaas, certainly word count is not constantly updated. As I
indicated previously in this issue, word count is updated only after a short
period of user inactivity (450 ms) and this is periodically checked every 2
seconds. That implies that while typing word count will not change, but a
little moment after you stop writing the count will be updated.
I preferred that behaviour instead of updating regularly every 5 seconds, as
you proposed, because that operation could be quite long and very intrusive as
you yourself have proven.
I think it should be sufficient most times, isn't it? Are you constantly
checking that information while typing?
Original comment by dpra...@gmail.com
on 8 Jan 2013 at 8:54
Hi Daniel. I tested again and now notice that the word count is updated after 5
seconds (not 2) of inactivity. This may be confusing, for example when you've
pasted some text and look at the word count you won't know if it's up to date
or not.
Some suggestions:
* the word count could be made grey as soon as the user starts typing. Then,
when it updates after he stops typing, it could be made black until he starts
typing again. That way you'd know that when the word count is grey, it's not up
to date.
* the delay before the next update could be made dependent on the previous
result of the word count. For example if the previous word count was < 1000
words, the delay could be very short, whereas if it was > 10000 words, it could
be long to prevent slowing down the program.
* after deselecting a text selection, the word count should be cleared
immediately. right now, the word count of the selection remains visible and can
be confused for the total word count.
Original comment by krommen...@gmail.com
on 9 Jan 2013 at 11:11
Hello
Ok, I'll considerer one of that suggestions or something similar
Best regards
Original comment by dpra...@gmail.com
on 9 Jan 2013 at 4:11
Original issue reported on code.google.com by
krommen...@gmail.com
on 21 Aug 2011 at 12:49