We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm observing this issue on Linux with a self-built executable from commit 67dfaf1 (lastest master).
Signals with SIG_VALTYPE_ 1 show up with the correct values in text fields, but have incorrect values when graphed.
For example:
BO_ 1026 port_traction3: 8 Vector__XXX SG_ inverter_temp_port_traction : 0|32@1- (1,0) [0|0] "" Vector__XXX SG_ motor_temp_port_traction : 32|32@1- (1,0) [0|0] "" Vector__XXX SIG_VALTYPE_ 1026 inverter_temp_port_traction : 1; SIG_VALTYPE_ 1026 motor_temp_port_traction : 1;
The text was updated successfully, but these errors were encountered:
That sure looks like a bug. Obviously the main window and graphing windows should be displaying the same data. So, something is wrong here.
Sorry, something went wrong.
No branches or pull requests
I'm observing this issue on Linux with a self-built executable from commit 67dfaf1 (lastest master).
Signals with SIG_VALTYPE_ 1 show up with the correct values in text fields, but have incorrect values when graphed.
For example:
The text was updated successfully, but these errors were encountered: