Selective Erase for highlight
It would be nice to be able to erase a specific type of highlighting by applying that type of highlighting a second time...using "Erase" on an area where I have multiple types of highlighting wipes out everything, when I usually just want to get rid of one type of highlighting.
As also voted elsewhere, I would also like to be able to undo the last highlight...every once in a while, Logos applies a highlight to a huge block of text (I think it has something to do with the way I quickly select text with the mouse or pen ... coupled with the unpredictable select delay of Logos 4--by the time I realize Logos overselected, it is too late and I've already pressed a key or button to apply highlight). My idea on the undo is that it would return things to the immediately prior state--including any instances of that highlight on text in that range. For example, "Test ____ Test" if accidently applied with underlining for that whole section, would with CTRL-Z return to "Test ____ Test" and not "Test Test". Regarding the Selective Erase itself, I should be able to highlight the underline part I want to turn off and just apply underline style again--I don't want to use Erase because I tend to have many overlapping highlighting styles and don't want to rebuild all of that just to Erase one.
Ward Walker commented
The "Remove Annotations" Feature (renamed from Remove Highlighting in a later version) adequately scratches this itch. I suggest Logos mark this as completed and free up the votes.
Right-click a small portion of the text that has the incorrect highlight (this can be as small as one character), choose "Selection" on the right, then "Remove highlighting" from the context menu. This will remove the entire span of highlighting for all highlights on the text you right-clicked on.
I'm perhaps not explaining it very well, but I think it should do what you want, espeically for cases where huge blocks of text have been highlighting incorrectly.
Ward Walker commented
Upping my votes...can't believe this is only #305--evidently others haven't accidentally written over a resource with an inadvertent highlight, forcing the complete manual re-build of all highlighting in that resource.