andre@carya

I typically try to avoid a UI design that could get in that state. When modal dialog pops-up it should typically be the interface the use needs to handle before be able to do other stuff in the application. Most application I write nowadays use subpanel constructs for the main UI and only pop-up dialogs "modal" in case it's something that needs to close before doing anything else or float mostly in case of an additional information windows (mostly debug/trace type). User workflow should be a simple for the user as possible, logical flows.

Thanks James, Keep up the good work, it's some getting used to working with JSON in LV.

Is it possible to directly access a particular object somewhere deeply nested inside the JSON text with a JSONpath that doesn't require knowledge of the complete structure? The structure can be altered outside the application, the field however are specified in official documents and should be used. E.g. I want to get the Packet object that has NID_MESSAGE 0. { "ALE (TLE)": { "length": 48, "message_type": 3, "FIE-PR": { "type": 198, "length": 37, "TCEPID": 1987771643, "UNISIG-037 SaPDU": { "ETY": 0, "type": 5, "DF": 0, "UNISIG-026 Message": { "NID_MESSAGE": 136, "L_MESSAGE": 24, "T_TRAIN": 13969, "NID_ENGINE": 103, "Packets": [{ "NID_PACKET": 0, "L_PACKET": 114, "Q_SCALE": 0, "NID_LRBG": 6980601, "D_LRBG": 11133, "Q_DIRLRBG": 0, "Q_DLRBG": 0, "L_DOUBTOVER": 0, "L_DOUBTUNDER": 0, "Q_LENGTH": 0, "V_TRAIN": 0, "Q_DIRTRAIN": 0, "M_MODE": 0, "M_LEVEL": 3 }] }, "MAC": "368268A6E6112334" } } } }

In case it's possible, haven't tried it myself. You could maybe put that SV in a subVI then search and replace each instance with the built-in search and replace function. Manual would be to tedious. Add a dialog that displays the call chain on abort.

Just an addition in case people use the .Net XMLDocument class. XMLDocumentToStringPrettyPrint.vi