filetags | Management of simple tags within file names

The main issue with the code is the file loop. GUI applications are event based so the button must be used to move to the next file. For the controls, build them once then update the values when a new file is loaded.

Try this code. It loads the tag data into the form for each file.

To filter records having tag count zero you need to use having clause as follows -

i made a few changes into something that would work in my database with a similar structure... This did return me some 0 count rows, however this is postgres i am running it on, and you are clearly using something different

I think you want LEFT JOIN:

I have verified this issue and be warned! Updating the index in parallel is not possible! My index corrupted itself partially (both the index and daemon didn't crash). You will not see this issue at a first glance. I have verified this by inserting and checking the inserted value (by directly selecting it after insertion) and the returned value didn't always match the inserted value as outlined below.

As an example for clarification. I inserted test but I got back t^463t from the select (directly after the insertion was performed).

For this test I have inserted 1.000.000 documents spread over a two-threaded application whereof 43.372 documents had this issue outlined above. This of course is dependent of the exact rate of parallel inserted documents, but Sphinx doesn't seem to be thread safe. (assumed is that even more documents will get corrupted when using more threads to insert documents in parallel)

Sometimes I also noticed that words from multiple documents where concatenated (those documents where inserted at the exact same moment).

I suggest you do things in phases, partly to make sure it's working correctly (testing), partly because it's easy to maintain/extend.

Try this to get only the pdf links. I used selector to make the parser focus on those links which have this .pdf in the end.

Do I understand correctly that you want to "merge" the contents of the txt files tagged "mypackage" into the archive, i.e. everything listed in all the files is supposed to end up there? If so, then you simply need a "top-level" rule that does the aggregation. Your existing rules would tag their outputs as e.g. "mypackage.part" and then a multiplex rule would take these as inputs and create a "mypackage" artifact. Note that there is the archiver module (https://doc.qt.io/qbs/archiver-module.html) that can do the final step of creating the package for you from the aggregated txt file.

You did not tell qbs that you want documentation to be built. Add a relevant tag to the product type, such as "qch". See https://doc.qt.io/qbs/qt-modules.html#core-file-tags for the qdoc-related file tags. See https://doc.qt.io/qbs/rule-item.html#rules-and-product-types on the general role of the product type.