SUGGESTION: Fix read wear marks

I'd normally call this a bug but I suspect it was intentional. The scroll wear-marks apply to a specific resource not a panel nor system wide as other types of history do. Therefore, scroll wear-marks should be cleared at the resource level (panel menu should be close enough) rather than at the system level.

Find more posts tagged with

Comments

Eli Evans (Logos)

It was intentional. Our thinking was that you either love 'em or you hate 'em. (I don't care for them and turn them off. Love the search tick marks, though.) Is there a specific situation you had in mind for why you'd rather control this at a resource level instead of a global setting, that is, a personal preference?

MJ. Smith

https://community.logos.com/discussion/comment/736583#Comment_736583

They can be useful within a resource if you know that they are collected as of when you started project X which may not be the same time as you started project Y affecting resource Y'. Or put another way, the less meaning they have the less apt people are to use them. Making them global ensures minimum meaning.

Eli Evans (Logos)

https://community.logos.com/discussion/comment/736586#Comment_736586

Okay, thanks!