Visual DialogScript FAQ
After I have created a program, I am not able to edit the dialog with the dialog editor. When selecting this choice by either F2 or by right mouse and selecting from the menu it brings up a new dialog box. What am I doing wrong?
The cursor must be in the "DIALOG CREATE" line if the script when you press F2.
How do I insert TAB's and LINE BREAK characters in text I need to output with the TEXT control?
The @TAB() function will insert TAB characters, while the @CR() function will insert LINE BREAK characters in the text you need to output.
I am trying to hide a program when it is running. I have tried to use WINDOW HIDE but it still shows up on the task bar. How do I hide the task bar button?
The window and the taskbar button are two separate things. If you want to hide the taskbar button you must give it a different name from the window, so the WINDOW HIDE command can identify it uniquely.
I do not live in UNITED KINGDOM. Can I purchase a license for Visual DialogScript locally?
Currently, licenses for Visual DialogScript can only be obtained online from 2CheckOut. If you don't want to put your credit card number on the Internet you can fax your order to Commercial Research. For more information see the Online shop.
I need a version that will run on Windows NT 3.51. What can I do?
The 32-bit version only supports NT from version 4.0. The 16-bit version will run on NT 3.5, but this has various limitations as mentioned above.
I want to use the @MCI function. Why are the MCI commands not documented.
Visual DialogScript simply provides an interface to the Windows MCISendString function, to allow scripts to execute MCI string commands. MCI itself is not part of Visual DialogScript and is not documented or supported by Commercial Research Ltd. It is part of Windows and is documented by Microsoft. You'll find into the help file an updated link to Microsoft MCI resources
I want to write a script program to do something and I don't know how to start. Are there any books or other examples I could look at?
The best place to start looking for further information about using Visual DialogScript is right here in the extensive support section of this site. You will find User Mailing List and Message Boards, and other forms of support that can aid you in your learning or continued efforts of programming with Visual DialogScript.
What do I get when I register? Will I receive the software on disk and a printed manual?
Visual DialogScript is an electronic product. The registration fee pays for the license to use the software and distribute the executable files created with it. The code you receive upon registration converts the evaluation copy to a fully licensed version, so there are no disks to install and no new software to download. The manual is in the form of the online Windows Help. You can print out the Help pages if you need a printed reference manual.
What platforms does Visual DialogScript and the programs generated with it run on?
Visual DialogScript is designed to run under Windows 9x / Me / Nt / 2k / Xp / Vista / 2008.. There is a version for 16-bit Windows but this version has certain limitations (see README.TXT for more details.) The System Requirements page has more information on this.
When I run my compiled script EXE I get a "cannot run script" error. What is wrong?
The error "Cannot run script" means that the VDSRUN60.DLL cannot be located. It has to be in the search path: either the current directory, the Windows directory or a directory in your PATH DOS environment string.
Where can I find more information about the @SENDMSG function?
Upon registering Visual DialogScript, you can download articles that explain the @SENDMSG function in greater detail. The @SENDMSG function uses the Windows Api SendMessage command. More information about SendMessage can be located on Microsoft's website.
Will scripts developed under Windows 95 or later run under Windows NT 4.0?
Many scripts developed for Windows 95 will run under NT 4.0. However, Windows NT is not completely compatible with Windows 95 and therefore some scripts that work under Windows 95 will not work correctly under Windows NT. These scripts may need rewriting in order to work under Windows NT. In some cases it may not be possible to do something under Windows NT that you can do under Windows 95 because NT prevents it. For information about the differences between NT and 95 see the Microsoft web site.