I am looking to get some input from the user and the best dialog function I have come across is "create_custom_dialog()". Unfortunately this seems a bit limited because I don't seem to be able to:
display default values
control the size of the edit boxes
include a listbox in the custom dialog
Am I missing something or will I have to write something up on my own?
BTW, if you are going to tell me that I should use a flatfile or INI file instead because it makes batching the tests overnight easier... please don't bother - that's not what I'm asking about.
All I would like to know is whether or not there is more that can be gotten out of the create_custom_dialog() function or if there is another such function that would do the trick better for me.
Yeah, I was looking at the create_* dialog functions too and wondering why they even bothered developing them since they are so limited. We're ALL missing something with these functions... Best I've come up with is having multiple dialogs prompting one after the other, like create_list_dialog followed by another create_list_dialog, followed by create_custom_dialog, to get all the user input I needed.
I wish they'd get something together like what Robot used to have (or still has) where you could build dialogs with radios, check boxes, drop downs, edit boxes, all sizes defined by the coder and as many as you want/need.
Sorry I'm no help. Just sharing in your pain.
Dialogs in WinRunner are weak at best.
WinBatch from "Wilson WindowWare" http://www.windowware.com
Cost of WinBatch is about $100
Cost of Compiler is about $500
The Compiler is well worth the money!
The Compiler can produce stand alone .EXE files that can be distributed to as many machines as you wish.
You can have as many as 100 controls in a WinBatch dialog. You can "invoke_application from WinRunner" the .EXE which makes a call to the dialog .WBC file.
In the .EXE script file, you can save the info returned from the Dialog into a file.
Then read the file in WinRunner.
I have done this and it works great!