The idea is to have a count on the amount of times an indicator is selected- so it is known if an indicator is unpopular and should be removed from the search area.
Previously when i suggested this, it was rejected with the reasoning of 'just let it search'.
I think this shows a poor comprehension of just how big the area the sqx searches to find its matches.
Please watch this quick and entertaining video on how many different ways a deck of cards can be shuffled: https://youtu.be/ObiqJzfyACM?t=860
Depending on how sqx's search is set up, the search area could be many many factorials even bigger than the 52!* example in the video, leading to absolutely mind-blowing search area sizes.
So if indicators that are rarely found useful can be identified and removed from the search area it can be kept as low as possible and lead to a more effective search.
I have not worried about discussing a how, because first i want to discuss the why. if the logic is agreed then discuss how best to implement a count
However is the easiest way to implement it into sqx would be fine. The coders would know their work better than me and where it could be slotted in. The purpose of this task was to outline its usefulness, not to demand it be implemented in a certain way.