Skip to content
New issue

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

Multiple instances of modules cause bleedover of config displayed #364

Closed
pollockm opened this issue Oct 13, 2017 · 6 comments
Closed

Multiple instances of modules cause bleedover of config displayed #364

pollockm opened this issue Oct 13, 2017 · 6 comments

Comments

@pollockm
Copy link
Contributor

pollockm commented Oct 13, 2017

image

(the current released set shows this - we are about to get bugs reported from customers)

Ex:
dds.zip

@pollockm
Copy link
Contributor Author

To reproduce:
View the names of the modbus channels on each target.
change the name of the modbus channel under one target.
Click on the modbus module on the other target. Note that the name given previously has now bled over here.

We're not correctly clearing the display when switching in the subpanel. This caused massive confusion in the customer course I'm teaching this week.

@pollockm
Copy link
Contributor Author

This issue was reproduced with the modbus and DDS modules (same behavior). Not reproduced in EIP Tags or EIP.

I assume this may be template-related.

@becega
Copy link
Contributor

becega commented Oct 16, 2017

Can reproduce it with the new versions it wasn't there at least until tag editor core 2.4.0.6. WHen updating core it also update 2 other modules, the updates in my machine were:
Tag Editor Core 2.4.0.6 --> 2.4.0.33
Module Interface 2.3.0.11 --> 2.3.0.17
Execution Interface 2.3.0.11 --> 2.3.0.7
Most Likely its in tag editor core

@becega
Copy link
Contributor

becega commented Oct 16, 2017

The issue was introduced on the build 0.32 that i think is related to this pull request:
#356

@becega
Copy link
Contributor

becega commented Oct 17, 2017

The bug was introduced in this VI \Tag Editor Core\Table API\Listbox\Init.vi

Value signaling causes the error and just switching value solves the issue and keeps the previous bug solved.

@dbendele
Copy link
Contributor

@becega , thanks for investigating! Are you going to make the change?

As a side note, I don't yet understand why the value signaling would lead to this issue.

@dbendele dbendele self-assigned this Oct 18, 2017
dbendele added a commit that referenced this issue Oct 18, 2017
fix issue #364
use value property instead of value signaling property
cosmetic changes to diagram
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants