Reply to thread

Message

<blockquote data-quote="aspik" data-source="post: 1246250" data-attributes="member: 72523">I was away...Since we have user management now, a watched state outside user data doesn't make any sens anymore <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />Knowing this settings is not a problem, trakt is running within the client and I'm already reading the user settings. So this would be a matter of reading the watched played percentage setting and comparing with the value from MI. I was more afraid because such a setting exists. The user could have for same time the default value, and later decide to change it. I thought that after changing the value and syncing the library again, an already watched movie could be read as unwatched. OK, good. Then to know if a MI is watched I'll read the play percentage attribute, but for marking it as watched/unwatched I still use the watched actions as this way it will&nbsp; be saved to the DB.</blockquote>

[QUOTE="aspik, post: 1246250, member: 72523"] I was away... Since we have user management now, a watched state outside user data doesn't make any sens anymore ;) Knowing this settings is not a problem, trakt is running within the client and I'm already reading the user settings. So this would be a matter of reading the watched played percentage setting and comparing with the value from MI. I was more afraid because such a setting exists. The user could have for same time the default value, and later decide to change it. I thought that after changing the value and syncing the library again, an already watched movie could be read as unwatched. OK, good. Then to know if a MI is watched I'll read the play percentage attribute, but for marking it as watched/unwatched I still use the watched actions as this way it will be saved to the DB. [/QUOTE]

Verification