add ChannelOwnerModule class #26
Open
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.
I use a local copy of this class already in several modules. The idea behind this class is, to centralize the handling of channels in one common place.
Another possibilities for this implementation would be to merge it directly to OpenKNX::Module. The behavior would be fully downwards compatible. Only if the constructor with the number of channels will be used, the new functions will be used.
I would also add the same channel handling for the console functions, but for this, the console functions processCommand and showHelp must be moved from OpenKNX::Module to OpenKNC::Base.