(2017-09-11 17:28)Razze Wrote:(2017-09-11 13:19)ksooo Wrote:(2017-09-11 13:12)Razze Wrote: I think we can fix this via the same thing I we now do for reseting resume points. We need to do the call to update the gui probably best done near the database change request.
No, this is completely different. It's not at all about notifying changes. We have no clue how to identify the right folders as obviously not all folders should get the context menu items in question. That's the actual problem.
Okay, but not so sure about that. That would mean that the availability of resume points is also not correct and should not be handled by estuary like that?
I somehow still think, it might be two bugs crossing each others path. But that's just a feeling, can't say anything concrete and you seem to have looked at it, so you're probably right
No, these are two completely unrelated stories. The problem discussed here is solely about the visibility condition for mark watched / unwatched.
And I do absolutely not get what Estuary should have to do with that. Core context menu items are 100% coded in c++, no skin xml involved.