Quoting hydr0x:

Quote:

Quote:

There are a few events to which you can register your plugin to, but that's never been my area of expertise.

Thanks for the API. I did in fact register for the plug-in forum, so far the account hasn't been activated. I wasn't even thinking about listening to events for filling these fields, but rather of a manual action that needs to be called by the user. E.g. "Update Invelos titles". Would be good enough for me I guess, especially if that was possible for flagged titles.

At first glance, it looks like it should be possible for your search to use one of these functions and only search within the returned IDs or maybe extend the existing filter set:

ICollectionFilter GetCollectionFilter();
object GetFilteredProfileIDs(ICollectionFilter CollectionFilter);
object GetDisplayedProfileIDs(int SortOrder);

Quote:

Yes you can. You need my plugin-API-key and the names of the fields, both are publicly available.

Great, then I will check if that's an option

But wouldn't he already be using those? And you still don't know how many you will get from the search - which is what he said he couldn't control. Again, if you are willing to suffer an occasional caching of XML for the collection, or subset, then you can use Xpath to get fast search results at any level of detail you desire. Or manually build your own filter (XML) file then use the API to load the filter set. That is also very fast.

Quoting mediadogg:

Quote:

But wouldn't he already be using those?

Nah, I'm just implementing the interface method

Quote:

public interface IDVDProfilerDataAwarePlugin
{
        // Called for each potential match when filtering. Return true to match
        // For use with SetCustomFieldFilterableA
        // ComparisonTypeIndex: the selected index into ComparisonTypes
        // ComparisonValue: the selected index into MatchItemList, or the user-entered value if no list
        // TestDVD: Shell profile record (Profile ID and access to custom fields only)
        // If more data is required from the profile, need to use DVDByProfileID or similar
        bool FilterFieldMatch(string FieldFilterToken, int ComparisonTypeIndex, object ComparisonValue, IDVDInfo TestDVD);
}

Ok, I see. Pretty silly that the API does call this for every title and not only the ones already filtered

Anyways, I'll wait for my access to the subforum, maybe there's some way to solve this. At worst, I'll try the "copy existing title fields into plug-in and filter on that" approach.

Quoting hydr0x:

Quote:
Ok, I see. Pretty silly that the API does call this for every title and not only the ones already filtered

Anyways, I'll wait for my access to the subforum, maybe there's some way to solve this. At worst, I'll try the "copy existing title fields into plug-in and filter on that" approach.

Think about where it is in the chain. If it did what you said, then filters would not work the way you expect. They would become cumulative in their effect (essentially performing an "AND" between each filter operation). Eventually your collection panel could go blank. To see what I mean, go to the Filters panel and do some queries. Each query assumes that the entire collection is available to be searched.

One solution, as you proposed is to write your own GUI, so that the search string is not entered character by character, but as a completed string. As I have suggested a couple of times now, you can simulate that by dynamically creating your own filter file (XML format), and then using the API to run the filter. Then you will have the entire string already formatted. But I don't remember whether custom fields work in filter files. It would be very simple and easy to test, and a simple coding task to implement it. I would be happy to send you a sample code snippet, if you want or need it.

Quoting mediadogg:

Quote:

Another thing that came to mind while testing is that you could possibly use copy / paste (or Ctrl-C / Ctrl-V) to blast past the GUI updates from typing into the search box. I think it works. So, instead of typing character by character, somehow copy your search string into the clipboard, then paste it into the search box. What happens for you? I perceived it to be faster.

Yes, that should be a workaround to avoid the multiplied effect of the delay during typing. Unfortunately, even a single search takes about 30 seconds on my machine due to the total amount of profiles, so I will still look into workarounds ... if I ever get access to the forum