Skip to content
Discussion options

You must be logged in to vote

The dbc_classes.cpp one is already fixed on master. PR #450 changed the multiplex storage to multiplexLowAndHighValues and left that line behind, then de5b5cc (Oct 20) switched it to sig->isValueMatchingMultiplex(val), which checks every range the signal has. Your .at(0) version only looks at the first range, so it would miss signals with extended multiplexing (several value ranges), and you don't need to make the member public either.

Fix commit: de5b5cc

So I'd pull the latest master and rebuild before patching further. The foreach and CONFIG += exceptions questions are really for the maintainer, but it's worth re-checking them against a clean master build first.

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
0 replies
Answer selected by klkl140
Comment options

You must be logged in to vote
2 replies
@charles-benedito
Comment options

@klkl140
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants