okay thanks! I'm quite happy editing nfo files so I'll do this. cheers! feature request to include a button/menu option for this in MC ;)
I mostly prefer using tvdb for scraper but I have a couple of shows where some of the specials are missing on tvdb and listed on tmdb. I can't seem to change scraper to tmdb though without changing it for my entire library, am I missing something? I can see it's possible to have different scrapers for different root folders but I don't really want to move some of my library to a different folder just for them to be scraped the way I want. I've tried running rescraper wizard > tmdb id, but this doesn't...
aha - looks like this might be an issue then. thanks, looks like I will have to manually Refresh() as needed
actually thinking about it I can probably just follow the treelistview IsExpanding events to follow nodes as they expand, and then subscribe to each objects PropertyUpdated event as they do. shouldn't take more than a few lines of code
yes, it will work, and it's a whole lot of extra code if I can simply use INotifyPropertyUpdated to do it. the objects themselves already handle everything with regards to reflecting the disk/directory structure, each object has a FileSystemWatcher that watches for changes in its own directory, and it reloads its child objects as necessary. all of this already works, the object.Children property (which the ChildGetter delegate returns) already holds the correct information if changes are made on...
yes, it will work, and it's a whole lot of extra code if I can simply use INotifyPropertyUpdated to do it. the objects themselves already handle everything with regards to reflecting the disk/directory structure, each object has a FileSystemWatcher that watches for changes in its own directory, and it reloads its child objects as necessary. all of this already works the whole point of objectlistview is to get away from the model of presenting a dictionary of key/value pairs which reflect a separate...
unfortunately I'm not easily able to notice a change in the model objects, because my code does not know about most of the model objects - the only model objects my code knows about are the roots (the top level) of the treelistview (in this case, a list of drive letters). all of the child objects are created by and owned by their parent objects, they are returned using the ChildGetter delegate (which itself returns a property Children which is a List<> of objects), none of the objects know about...
unfortunately I'm not able to notice a change in the model objects, because my code does not know about most of the model objects - the only model objects my code knows about are the roots (the top level) of the treelistview (in this case, a list of drive letters). all of the child objects are created by and owned by their parent objects, they are returned using the ChildGetter delegate (which itself returns a property Children which is a List<> of objects), none of the objects know about each other...