Today when an event is removed, no special actions are done in the testers and a 'manual search' has to be done in the module's main VI.
Here is what is suggested in DQMH help :
- In the case of a Request:
- In the Tester VI:
- Open the block diagram and find the event frame configured to test calling this request.
- ...
- In the DQMH Module Main.vi:
- Open the block diagram and find the event frame configured for this request (It might no longer be listed and instead say something like “Unknown Event (0x0)”).
- ...
- In the case of a Broadcast:
- In the Tester VI:
- Open the block diagram and find the event frame configured for this broadcast. (It might no longer be listed and instead say something like “Unknown Event (0x0)”.)
- ...
- In the Module Main VI:
- Open the block diagram and find the places where the broadcast VI is called and remove it.
- ...
It would be nice to attract dev eyes on the places where modifications need to be done post event-removing.
Maybe adding a comment like this would be enough ?
It is not much, but the comment color and hashtag would ease the 'finding' process.
The DQMH target is not known so far.