Add a "None" Option for "Consuming Event Loop"

[LFBaute]

Add an always available "None" option in the drop list, 

Selecting this option will avoid creating a case for the event in the Message Handling Loop (MHL) nor any other place

Here...

so by default this droplist will include, 
- Event Handling Loop
- None (this will avoid generating a consuming case anywhere)

or it could be 

a checkbox next to the consuming event loop droplist

to allow developer to select avoid generating it

[Darren]

Um, if there's no event loop in the DQMH Main VI registered for the request, where does it "go"?

[LFBaute]

Sorry I meant the Message Handling Loop,

Just trigger the event in the EHL, and no consuming loop.

[joerg.hampel]

After consideration and discussion, we decided to decline this feature request.

The Consortium and the Trusted Advisors agree that the benefit of the feature is largely outweighed by making the UI more complex. Scripting Hooks could be an alternative for this.

We really appreciate your input, declining the idea does not mean it didn't help us fine-tune the scope of DQMH and reconsider our strategy. Please keep those ideas coming 😉