DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

"Rename DQMH Event" tool does not rename MHL cases

Solved!
Go to solution

I just realized that the "Rename DQMH Event" tool does not rename MHL cases. Is that intentional?

Michał Bieńkowski
CLA, CTA, CPI

  1. Did someone devote their time to help solve your problem? Appreciate it and give kudos.
  2. Problem solved? Accept as a solution so that others can find it faster in the future.
  3. Contribute to the development of TestStand by voting on the TestStand Idea Exchange.
0 Kudos
Message 1 of 6
(162 Views)
Solution
Accepted by topic author bienieck

It is intentional. You may have other code in your Main VI that is executing that particular MHL case.

0 Kudos
Message 2 of 6
(121 Views)

Ok, that makes sense. However, I think "Destroy Request Events.vi" is not updating the unbundle by name, but it should, right?

Michał Bieńkowski
CLA, CTA, CPI

  1. Did someone devote their time to help solve your problem? Appreciate it and give kudos.
  2. Problem solved? Accept as a solution so that others can find it faster in the future.
  3. Contribute to the development of TestStand by voting on the TestStand Idea Exchange.
0 Kudos
Message 3 of 6
(112 Views)

One more comment: I think a note about that the cases are not renamed might be added to the rename tool window.

Michał Bieńkowski
CLA, CTA, CPI

  1. Did someone devote their time to help solve your problem? Appreciate it and give kudos.
  2. Problem solved? Accept as a solution so that others can find it faster in the future.
  3. Contribute to the development of TestStand by voting on the TestStand Idea Exchange.
0 Kudos
Message 4 of 6
(105 Views)

Actually, I noticed more instances where renaming didn't happen. To summarize:

  1. MHL cases (intentional),
  2. Destroy Request Events.vi,
  3. Request argument cluster constants already placed on the diagram,
  4. EHL labels.


This is what I've spotted so far.

Michał Bieńkowski
CLA, CTA, CPI

  1. Did someone devote their time to help solve your problem? Appreciate it and give kudos.
  2. Problem solved? Accept as a solution so that others can find it faster in the future.
  3. Contribute to the development of TestStand by voting on the TestStand Idea Exchange.
0 Kudos
Message 5 of 6
(84 Views)

Thanks Michał, I have filed Issue #967 to the DQMH Consortium to look into these issues. I'd say most of them are cosmetic, but the Destroy Request Events issue is definitely a bug that I was able to easily reproduce.

0 Kudos
Message 6 of 6
(55 Views)