Respect monitored item trigger (DataChangeFilter) #579
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As already mentioned in #332 according to https://forum.unified-automation.com/post282.html the
DataChangeFilterallows clients to get subscription updates even if the value does not change. I need this kind of functionality because of legacy components, so I can't switch to e.g. Events.To achieve this I removed the filter for identical values and only avoid calling the callbacks of a value if the timestamps are exactly the same. The actual filtering based on the
DataChangeFilteris done similar to thedeadbandfilter. I added a new subscription method which enables clients, tools and tests to subscribe with aDataChangeFilterofStatusValueTimestamp.Please let me know if you have any doubts.