TestStandify! Unable to execute successfully in the 32-bit Chinese version

[Pablo J Bames]

Thank you very much to the author for improving based on the feedback from last time.
In the new version (Version 1.2.1.33), it is found that there are still some problems that cannot work properly.
I did the test process:
one:
1. Create a project with the 64-bit English version of labview
2. Use the DQMH Testandifier tool in the 64-bit English version of labview to work normally.
two:
1. Create a project with the 64-bit English version of labview
2. Use the DQMH Testandifier tool in the 32-bit Chinese version to work normally.
three:
1. Create a project with the 32-bit Chinese version of labview
2. The DQMH Testandifier tool in the 32-bit Chinese version cannot work properly.
Four：
1. Create a project with the 32-bit Chinese version of labview
2. Use the DQMH Testandifier tool in the 64-bit English version of labview cannot work properly.
3.Stuck at this step（Building source distribution...）

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
错误-4500发生于 DQMH_TestStandifier.lvlib:Main.vi -> DQMH_TestStandifier.lvlib:TestStandify State Machine.vi -> DQMH_TestStandifier.lvlib:Create Source Dist.vi -> NI_AB_API_SDIST.lvclass:Set Destination Path.vi -> NI_AB_API_Build.lvclass:Set Destination Path.vi -> AB_API Set Destination Path.vi

该错误代码未定义。出现未定义错误可能有多种原因。例如，代码说明不存在，或者连线输入的数值并非对应于错误输入的错误代码。

此外，出现未定义错误代码的原因还可能是该错误与操作系统或ActiveX之类的第三方对象相关。对于这类第三方错误，可通过对错误代码(-4500)或其十六进制表示(0xFFFFEE6C)进行Web搜索得到错误说明。

Error Dialog w Copy to Clipboard.lvlib:Simple Error Handler.viDQMH_TestStandifier.lvlib:Main.vi
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
09:44:48.059 : Building source distribution...
09:44:48.059 : Test My Cloneable Module API.vi has been found
09:44:46.666 : Looking for Tester VI...
09:44:46.666 : Selected Module is valid
09:44:46.603 : Validating : Wait for Module to Stop for Cloneables (59/59)
09:44:45.718 : Validating : VIs with Auto Error Handling (58/59)
09:44:45.584 : Validating : Unwired Bundles in Main EHL (57/59)
09:44:45.540 : Validating : U32 Module ID Input (56/59)
09:44:45.429 : Validating : Tester Stop Module Case Structure (55/59)
09:44:45.333 : Validating : Teardown with Incoming Error (54/59)
09:44:45.306 : Validating : Stop Module Error Propagation (53/59)
09:44:45.266 : Validating : Stop Module - Event Firing (52/59)
09:44:45.238 : Validating : Stop Module - DQMH 2.1 (51/59)
09:44:45.191 : Validating : Stop Module - Cloneable Running as Singleton Polling (50/59)
09:44:45.050 : Validating : Start Module - Run VI Method (49/59)
09:44:44.944 : Validating : Start Async Call Reference Output Wired (48/59)
09:44:44.808 : Validating : Show Main Diagram on Init (47/59)
09:44:44.707 : Validating : Sending Nonexistent Messages (46/59)
09:44:44.680 : Validating : Semaphores for Singleton (45/59)
09:44:44.569 : Validating : Required Nodes - Tester (44/59)
09:44:44.512 : Validating : Required Nodes - Obtain Request Events (43/59)
09:44:44.458 : Validating : Required Nodes - Obtain Broadcast Events (42/59)
09:44:44.378 : Validating : Required Nodes - Main (41/59)
09:44:44.325 : Validating : Required Nodes - Destroy Request Events (40/59)
09:44:44.272 : Validating : Required Nodes - Destroy Broadcast Events (39/59)
09:44:44.245 : Validating : Required Event VIs (38/59)
09:44:44.220 : Validating : Requests Folder (37/59)
09:44:44.000 : Validating : Request Tagging (36/59)
09:44:43.976 : Validating : Request Folder (35/59)
09:44:43.511 : Validating : Request and Wait for Reply Tagging (34/59)
09:44:43.273 : Validating : Reentrant Cloneable Start Module (33/59)
09:44:43.012 : Validating : Obsolete MHL Frames (32/59)
09:44:38.802 : Validating : Non-Reentrant VIs in Cloneable Module Library (31/59)
09:44:38.775 : Validating : Non-Reentrant Reset Override (30/59)
09:44:38.747 : Validating : Non-Reentrant Queue Class Overrides (29/59)
09:44:34.163 : Validating : Non-Reentrant Event VIs (28/59)
09:44:33.908 : Validating : No Release Queue in Top-Level Error Case (27/59)
09:44:33.558 : Validating : New Module Error Codes (26/59)
09:44:33.523 : Validating : Missing DQMH VIs (25/59)
09:44:33.214 : Validating : Improved Error Reported Frame in Tester (24/59)
09:44:32.970 : Validating : Handle Exit Error Handling (23/59)
09:44:32.918 : Validating : Find Tester (22/59)
09:44:32.895 : Validating : Find Request and Wait for Reply Timeout Error VI (21/59)
09:44:32.545 : Validating : Find Request and Wait for Reply Events with No Timeout Error (20/59)
09:44:32.192 : Validating : Find Request and Wait for Reply Events with No Conditional Wait (19/59)
09:44:32.139 : Validating : Find Multiple Testers (18/59)
09:44:32.091 : Validating : Find Multiple RT Testers (17/59)
09:44:32.039 : Validating : Find Multiple Main VIs (16/59)
09:44:32.015 : Validating : Find Main (15/59)
09:44:31.749 : Validating : Event Registration Error Output Not Wired (14/59)
09:44:30.361 : Validating : Event Cluster Naming (13/59)
09:44:30.322 : Validating : Error Reported Handling DQMH Tags (12/59)
09:44:30.294 : Validating : Error Cluster in Reply Payload (11/59)
09:44:30.270 : Validating : DQMH 1.0 (10/59)
09:44:30.104 : Validating : Close Module Update Execution Status (9/59)
09:44:29.938 : Validating : Close Module Error Handling (8/59)
09:44:29.752 : Validating : Close Module - Cloneable Race Condition (7/59)
09:44:29.459 : Validating : Broken Tester (6/59)
09:44:29.244 : Validating : Broken Main (5/59)
09:44:29.223 : Validating : Broadcasts Folder (4/59)
09:44:28.852 : Validating : Broadcast VI Event Icon (3/59)
09:44:28.595 : Validating : Broadcast Tagging (2/59)
09:44:28.574 : Validating : Broadcast Folder (1/59)
09:44:28.574 : Validating : My Cloneable Module.lvlib (1/1)
09:44:28.335 : Validating Module this may take several minutes
09:44:28.335 : Initialization succeeded.

未命名项目1.7z Untitled Project 1.7z

Edited November 24, 2023 by JasonBro

[Cyril Gambini]

Hi,

Thanks for the feedback !

I cannot really help here ! We noticed few erratic bugs with LV when working with unicode related langages (we have a Korean employee and it is often a problem when his PC is set in Hangul).

For the moment, due to very low request to support Chinese characters and diffculties to investigate on such issues, I will simply note this behavior as a bug.
And there is a great chance that we will not investigate further.

Sorry to be very direct here, but I prefer not to give false hopes !