Sign Up
VIPM › Posts › Directly select the right module

suggestion

Directly select the right module

Suggestion shared 3 years, 3 months ago by Olivier Jourdan
   

Details

I'd love to see the tool to select the module I right-click on when the DQMH scripting tool is displayed.
That would save a lot of time for DQMH users.

Comments

Jean-Claude Mengisen The tool shows a menu when you press "right-click" in the project explorer on a module. Are you not able to see this menu? See: https://s3.amazonaws.com/vipm-io-media-files-production/media/package-images/b92d5403-d5e9-4448-b05f-559851854eda.jpg
 •  Reply • 3 years
Olivier Jourdan Hello, the tool works as expected. My request is about the next step. Let's say I right-click on XYZ module, and I pick Create New DQMH Event item. I'd like to see the DQMH create event tool UI with the module XYZ already selected. I'm not sure this is feasible without a modification of the DQMH but, anyway it would be great to have that. Hope the idea is clearer.
 •  Reply • 3 years
Jean-Claude Mengisen When you select the XYZ module, the module will be selected as you described. I know that not all functions support this behavior. But this requires some activity on the DQMH side. => The Create New event supports this functionality
 •  Reply • 3 years
Olivier Jourdan I'm afraid it's not working on my installation. I'm on LV2019 and installed your package over DQMH 4.2. What would be your recommendation for troubleshooting that issue?
 •  Reply • 3 years
Jean-Claude Mengisen I have now tested it with LabVIEW 2019 SP1 (32bit/english) and DQMH 4.2 and it works as expected. Are you using a LabVIEW variant in another language? As an experienced developer, you can also set a breakpoint in the following VI. C:\Program Files (x86)\National Instruments\LabVIEW 2019\resource\Framework\Providers\ZE_DQMH\CreateEvent_Item_OnCommand.vi Attention: Save breakpoint and restart LabVIEW! Project Providers are already loaded at the start of LabVIEW!
 •  Reply • 3 years
Olivier Jourdan Hi Jean-Claude, I had to increase the timeout to get the feature to work. I think 3500 ms is too short. I used your tool on a "small" project with 12 modules, but I have a project with 40+ modules where the time to populate the ring is much longer. The more modules you have, the longer the ring populating will be. So I can't say what would be the best value for the timeout. Anyway, there is a feature request for improving that behavior your tool could benefit --> https://forums.ni.com/t5/DQMH-Feature-Requests/Decrease-scripting-tools-initialisation-time/idi-p/4102517 I hope this can help.
 •  Reply • 3 years
Jean-Claude Mengisen The used time to populate is unfortunately not dependent on my software. The number of modules and the performance of the PC are also crucial. What timeout time do you currently work with? I can increase the time without any problems. The maximum time has to be waited only if there is a problem.
 •  Reply • 3 years
Olivier Jourdan I set it to 60s. I think it should work even with my largest DQMH project.
 •  Reply • 3 years
Jean-Claude Mengisen Thank you for your input!
 •  Reply • 3 years

Please sign in to leave a comment.