2024-05-21, 08:37
Hi,
i think I solved the issue. When I use:
So what's different/ what changes did I made to Karellens code?
I added:
Also I noticed that - when using the Library Node Editor - that choosing "file" as sorting order generates:
when you change it to (like what Karellen proposed in the example):
Note that is now says file instead of filename.
Now I am just wondering what to chose in the Library Node Editor to generate
instead of:
Or is it a Library Node Editor issue?
i think I solved the issue. When I use:
I get exactly what I want.xml:<node type="filter">
<label>MCU</label>
<content>movies</content>
<rule field="filename" operator="contains">
<value>MCU</value>
</rule>
<rule field="title" operator="contains">
<value />
</rule>
<group>none</group>
<order direction="ascending">file</order>
</node>
So what's different/ what changes did I made to Karellens code?
I added:
xml:<group>none</group>
Also I noticed that - when using the Library Node Editor - that choosing "file" as sorting order generates:
xml:<order direction="ascending">filename</order>
when you change it to (like what Karellen proposed in the example):
the issue is solved.xml:<order direction="ascending">file</order>
Note that is now says file instead of filename.
Now I am just wondering what to chose in the Library Node Editor to generate
xml:<order direction="ascending">file</order>
instead of:
xml:<order direction="ascending">filename</order>
Or is it a Library Node Editor issue?