CriticMarkup and Word Count
It would be nice (and I think make more sense) if the word count at the bottom of the Marked window reflected the word count for the current view when using CriticMarkup. Right now, it just counts words for the entire document, markup included. I think, for example, if you click the "edited" tab for a CriticMarkup doc, the word count should instead reflect the number of words after CriticMarkup has been processed.
Expected behavior:
- word count reflects the count of the current view when looking at a CriticMarkup-enabled document, not counting comments for any view
Actual behavior:
- word count reflects the total word count of the entire document, CriticMarkup included
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Brett on 24 Nov, 2013 04:52 AM
It _would_ be nice, but it's problematic. It's about 10x faster to do
the word count on the raw text in Obj-C than it is to do it in
JavaScript in the preview. It's painfully slow to do a full word count
in the Preview. When CriticMarkup is rendered, all the elements are
there, and Marked just hides various elements based on the selected
mode.
I can definitely see the value in having comparison word counts. I might
be able to have a special circumstance for CriticMarkup mode where the
text of visible elements was shuffled to the main class for parsing and
have the count updated when switching modes. I'll put it on the roadmap,
but no promises on ETA.
2 Posted by Jonathan on 24 Nov, 2013 09:07 AM
Yeah, I thought that might be the case...
I didn't realize it at the time of posting, but if I just select the text, a little popup appears that has all the information I need. So at least there's still a way to do it.
Support Staff 3 Posted by Brett on 30 Nov, 2013 07:19 PM
I figured it out, by the way. The latest update has this issue solved.
Brett closed this discussion on 30 Nov, 2013 07:19 PM.