You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that the current behavior of calling listen with Matches will assign one (unused) mask and one (unused) filter for each Match provided, regardless if masks can be shared across multiple filters. This means the user can only utilize up to two filters out of the MCP2515's six. An improved behavior might roughly look like this:
It appears that the current behavior of calling
listen
withMatch
es will assign one (unused) mask and one (unused) filter for eachMatch
provided, regardless if masks can be shared across multiple filters. This means the user can only utilize up to two filters out of the MCP2515's six. An improved behavior might roughly look like this:If this looks good, I can help updating the current implementation.
The text was updated successfully, but these errors were encountered: