Tried to understand the posts within this thread in order to be able to create custom filters.
The path "MQNext" is my actual main folder of mq.
I do not unterstand release/config as path, as I did not download the ressources, but started with the attempt to create parcel_sources.lua and get it to work, using the example provided.
My guess is: "release/config" is the path used, when you use the source-files and compile the stuff by yourself.
As a user, my intension is not to download the whole sources and compile it myself, but just add filter-functionallity by adding the filter-definition-file.
At first I created the file within the same folder of the other files: "MQNext/lua/parcel". That did not work.
Next attempt I created a subfolder "config" and put the file there:
View attachment 57031
did not work either,
Next attempt I went one folder up and put the file into MQNext/lua/config. Did not work.
Next attempt I went one folder up and put the file into MQNext/config. That did work
View attachment 57032
Question: what is the intended location of the filter definition file : parcel_sources.lua?
As it is of type lua, my feeling is, it may be located under MQNext/lua/config ... or even better to stay together with the other files of that project "MQNext/lua/parcel" or "MQNext/lua/parcel/config".
To proceed, for now it is not important to get the answer immediatley.
As far as I have seen, the lua-projects attempt to contain all necessary files of the project within their subfolder within "lua/".
Are you going to change the location of the filter-definition to stay within the same folder of the other project-files?
For me step 1 is done: understand how to implement personalized filters
Step 2 now will be: try which modification exactly I need to do, to add the ability to create and recognize the "nosend" list of itens, to be excluded for parcel.
Will come back and present the result, if I get it to work.
PS: I like the idea to keep the core of the project as clean and small as possible, and give users the possibility to personalize it at their will.
Should keep the maintainance of the project as easy as possible while offering all extensions requested without the need to end with spaghetticode within the core of the project itself.