0 Members and 1 Guest are viewing this topic.
Filter->GetValueAsObject(AIMPML_FILTER_SEARCHSTRING, IID_IAIMPString, ...);
You plugins required debug versions of VS Runtime libraries - MSVCP140D.dll and VCRUNTIME140D.dll. I cannot run the plugin because I have VS2012 on my PC
const int AIMPML_FILTER_LIMIT = 11;const int AIMPML_FILTER_OFFSET = 12;const int AIMPML_FILTER_SORTBY = 13;const int AIMPML_FILTER_SORTDIRECTION = 14; // Refer to the AIMPML_SORTDIRECTION_XXXconst int AIMPML_FILTER_SEARCHSTRING = 20; // optionalconst int AIMPML_FILTER_ALPHABETICINDEX = 21; // optional
in 1st case, looks like I have found a bugs in C++ version of SDK, following constants must be:
in 2nd case, AIMP tries to filter content by NodeID field from grouping tree, but content for table returns items with different NodeId values. So, player have find no matches. I think, will be better to introduce the ParentID field (internal), that will bind grouping tree items with table items.
Do I have to build a full path to the grouping tree node?
Or try to set the AIMPML_GROUPINGTREENODE_FLAG_STANDALONE flag for grouping tree items (refer to the IAIMPMLGroupingTreeDataProviderSelection article)
Hmm, this will work, but I need full path for each grouping tree item ("root\child1\child12"). So I can only have the root nodes as standalone. Otherwise the selection will only contain the selected item id.So how would I use full path as "NodeId"? "root\child1" or "root/child1" does not work.
Filtering like FilePath is available FileName field types only. I suggest you to introduce parentID field instead
If I set all tree items as standalone, the filtering system works but the selection only contains the clicked tree item.
So it seems you can either have all tree items as standalone and filtering system, or if some items are not standalone you need to write your own filtering.Am I understanding this correctly?
This is because you are filtering by NodeID, not ParentID, so it displays only current node.
If you want to use data from grouping tree as file name - you should use filename field type, because only in this case engine combines node path like file name path - root\child1\ and etc, for all other field types it build filter like: (nodeId = 'root') AND (nodeId = 'child1'), as you can see this filter make no sense.
DataColumn1|DataColumn2|..
|NodeID|ParentNodeID|DataColumn1|DataColumn2|..| 0 | -1 | Text 1| 1 | -1 | Text 2| 2 | 1 | Text 3
<Root> + <NodeID=0> + <NodeID=1> + <NodeID=2>