05-19-2006 09:54 AM
05-19-2006 10:07 AM
Do
Call SudDlgShow("Dlg1","C:\test.sud")
Select Case DlgState
Case "IDOk" : MsgBox "OK"
Case "IDCancel" : MsgBox "Cancel"
End Select
Loop While DlgState<>"IDOk"
You also can use the click event for the buttons to show up the dialogs.Matthias Alleweldt Project Engineer / Projektingenieur | Twigeater? |
05-22-2006 02:13 AM
Hello Matthias,
thanks for your answer.
Who does make up that stuff and it is not even written down in the help?!
Thomas
05-22-2006 09:14 AM
Actually, it is in the help:
Brad Turpin
DIAdem Product Support Engineer
National Instruments
05-22-2006 09:17 AM
OK,
So the pretty pictures only show up on my computer. If you look in the help for "SudDlgShow()", you will find a description of the "Return Parameter" called "DlgState". If you click on that link, it lists the allowed values of "DlgState", which Matthias used in his answer.
Brad Turpin
DIAdem Product Support Engineer
National Instruments
05-22-2006 09:30 AM
05-23-2006 03:11 AM - edited 05-23-2006 03:11 AM
Message Edité par tom_the_dude le 05-23-2006 03:12 AM
Message Edité par tom_the_dude le 05-23-2006 03:12 AM
05-23-2006 03:21 AM
Matthias Alleweldt Project Engineer / Projektingenieur | Twigeater? |
05-23-2006 04:09 AM
Hello Matthias,
oh yes, it's true. I can do stuff from my dialog but just this command does not work. So I have to have something wrong in the whole process.
Have to check it.
Thank you!
Thomas
05-23-2006 09:03 AM
Hi Tom,
In answer to your question about why NI implemented the SUDialog interface the way they did-- in a word... licensing. NI does not own the rights to Visual Basic, which does indeed have a lovely form editor. We could have used VB or VBA as the automation language and custom GUI engine for DIAdem, but then we would have had to pay a licensing fee for each copy of DIAdem, and then your version of DIAdem would have been noticeably more expensive.
Brad Turpin
DIAdem Product Support Engineer
National Instruments