Bug/Tip: Molassas highlighting can be corrected with a re-start

DMB

I noticed this yesterday, that under 'certain' events, the iOS app new highlighting can be really slow between the time of the temporary highlight (where the font sits under the highlight) and the confirmatio re-draw (where the text sits over the highlight) ... I'm using the traditional 'highlight' similar to Kindle.

I also noticed that re-starting the app clears it up. 

Today I noticed that the problem seems to occur in the code between the blue highlighting (older Logos app code), and the new overlay coloring. If the stylus (in my case) is not touching absolutely, the code gets mixed up and then sits for a while before it finally confirms the highlight.  But after that, it's molassas time until I re-start.

Another clue on the stylus-touch timing, is that the app will move the initial blue highlighting to the top-left of the app page (suggesting to me, it's completely lost its x/y coordinates).

Or if I highlight, starting with one word, then drag to a phrase, and then back to the start word, this seems to mix the code logic up as to exactly 'what' I'm doing ... and what to do next (display the lookup menu or just finish the highlight). In any event, a re-start gets it back on track.  In this 2nd example, the code eventually decides on a highlight; not a menu display.  But it's molassas time after that.