DQMH Consortium Toolkits Feature Requests

cancel
Showing results for 
Search instead for 
Did you mean: 
Olivier-JOURDAN

Move Stop Module.vi next to Start Module.vi in the library hierarchy

Status: New

IMHO, it would make more sense to have the Stop Module request at the same level than Start and Sync functions.

 

OlivierJOURDAN_0-1664382201793.png

 


Olivier Jourdan

Wovalab founder | DQMH Consortium board member | LinkedIn |

Stop writing your LabVIEW code documentation, use Antidoc!
2 Comments
Jens_S
Member

Well I have to say that I disagree with this. The Start Module VI is not a DQMH request at all so it's separated from the other build in request like Stop Module. At first I also found this a bit confusing but it makes sense if you think about it from a DQHM point of view.

Olivier-JOURDAN
Active Participant

@Jens_S, the stop module is a request, yes, but the code doesn't look like all the other requests.

Moreover, I'm not sure the hierarchy needs to follow the nature of the code. For me, that's more a kind of palette organization. In this way, it makes sense for me to have the start and the stop at the same level.


Olivier Jourdan

Wovalab founder | DQMH Consortium board member | LinkedIn |

Stop writing your LabVIEW code documentation, use Antidoc!