Ok I think I see what your asking. There is a problem with that. Under that logic it would not work. I mean it’s too generic and would trigger event on unwanted things.
You need events to be specific and with meaning. Also setting is a specific item we refer too, think Program Setting, so that’s not a good word to use.
Think about your request and try to be more specific.
I am going to use your term Setting for this but in practicality I really think you mean Configuration Change. I mean really think about it. How in the world could it watch for Setting Changed without knowing what setting. If its watching for all settings then does that sound practical?
Think about the current Rule structure does it sound like that would fit in this structure?
I am going to explain something that I hope others can understand as well. I hope I explain this well and please dont take it as me saying your ideas are bad, they are not bad.
It would be better if you presented your specific problem your trying to solve and lets find solution for that. We expand and explore features through this method the best. General Ideas are great but I will be honest most of the best expansions of SambaPOS happened when fixing very specific problems. When we see a specific prolblem and we brainstorm how to fix that problem we typically can come up with new features or ideas.
If we start with an idea but really dont know exactly what it will fix but kind of have idea… that doesnt really solve much nor does it really expand on features, its just an idea. I mean Emre would rather develop ideas that are meant for specific problems. When I say problems I dont really mean broken things It could be a configuration your trying to do but current features dont allow it.
I will give a great example and I am sorry some of you not in the Beta team may not understand this fully until next release. The latest Beta build you saw the insane new additions that will be coming soon hopefully, those came from me responding to several reoccuring problems of people trying to do the Delivery setup from V3 into v4 or even v5 because there never was an updated tutorial using newer tools since version 3. I took it upon myself to try and build it and update a tutorial for v5. Emre decided instead he will rebuild it from scratch to take advantage of newer features in v5. While he was working on that problem he saw several specific requests for things that were asked to solve specific problems and he was able to incorporate those into some TOTALLY amazing new features that hopefully everyone will see soon in next update.
So sorry for long post but last point then ill let it rest. As you will see with next release we have a TON of new features coming out and they were the result of Specific Problems that were explained in detail and through feedback Emre came up with some amazing new features that not just solve those problems but expanded capabilities because of them. Emre loves new features and he would add them every day for you but they must solve real problems not hypothetical problems.
You have a real problem or you wouldnt be asking for this. Its best if you explain the problem and work with us to find solutions to solve the problem Emre will design features and new ideas will flow through that. Dont expect every problem to be solved quickly, obviously he prioritizes things and typically he watches for similar needs and once he sees its starting to become a big need he solves it. Often while solving the problems new features happen that allow even better problems later! Yes in this case Problems are a GOOD thing