Exactly. When playing stuff with longer duration, the 50% mark is just not logical. It leaves to much to coincidences. For music and short clip video, sure. Here it might be a problem if the Number Plays increases just when it's reached the 90% mark. Some people change tracks often, or often before it's quite finished.
I just stumbled upon this problem too and decided to try to do something about it today. Watched(1) is pretty much useless (and the Watched checkmarks trigger too easily).
It should really be decoupled from the [Number of Plays] and triggered where:
Watched(1) = 0:[Number of Plays] = 0 and the bookmark is at 0%.
Watched(1) = 2:[Number of Plays] > 0 and bookmarks is at:
>50% for any file with [Duration] < 10 minutes or so (this specific number is open to debate)
>~90% for any file with [Duration] > whatever number you picked above
Watched(1) = 1:Everything else.
With the checkmark being equivalent to:
[=Compare(Watched(1),<,2)]=1However, if this is too "complex" for the simple function, then I'd much, much rather it always trigger at 90% (or so) than the current "1/2-way watched" behavior. The problem is that, especially with kids, now I end up watching 1/2 of a show and then stopping, intending to come back later. This makes building views that depend on the Watched status impossible, and makes the checkmarks have dubious value, for the vast majority of my use-cases.
It works as-is for Music Videos and other short stuff, but that's a tiny fraction of my files, and I can't think of a good use-case where you'd care about the "partial vs. non-partial" watched status of a music video. You just want to count plays, for those.
The logic of the current system doesn't work well at all for watching TV shows or Movies if you ever come back and finish an episode/film later.