Reply to thread

Message

<blockquote data-quote="henso" data-source="post: 1227339" data-attributes="member: 119106">This is probably related to the fact the imported watch status is stored into the MediaAspect and not the user watch status. The filters in the client only use the user watch status, so they will not work with imported watches. When browsing though the media the watch status will be determined both from the MediaAspect and from the user watch status, so here they will appear to be watched. This was done to not lose the watch status of media at the beginning of the MIA rework. Later though when the filter were created it was only possible to do for the user watch status. So we should probably remove that media appears watched based solely on the MediaAspect. I also don't think parents are updated during import so series will still be be un-watched etc. The question is how should this be handled? Should all users have the watch status imported when importing a watch flag? This would update the parents also but I have no idea what that will do the import speed. Another possibility is to not import the watch status and everything has to be updated through the client after an import.That's probably because the watch status is only saved for client on which is was watched. So this is, as already mentioned, because of the not fully implemented user support.</blockquote>

[QUOTE="henso, post: 1227339, member: 119106"] This is probably related to the fact the imported watch status is stored into the MediaAspect and not the user watch status. The filters in the client only use the user watch status, so they will not work with imported watches. When browsing though the media the watch status will be determined both from the MediaAspect and from the user watch status, so here they will appear to be watched. This was done to not lose the watch status of media at the beginning of the MIA rework. Later though when the filter were created it was only possible to do for the user watch status. So we should probably remove that media appears watched based solely on the MediaAspect. I also don't think parents are updated during import so series will still be be un-watched etc. The question is how should this be handled? Should all users have the watch status imported when importing a watch flag? This would update the parents also but I have no idea what that will do the import speed. Another possibility is to not import the watch status and everything has to be updated through the client after an import. That's probably because the watch status is only saved for client on which is was watched. So this is, as already mentioned, because of the not fully implemented user support. [/QUOTE]

Verification