The user clicks a button, something like "Scale your model", and the VB program shell executes the DBP one. It also passes along some commandline info, in this case, where your model is stored. The information is contatined within two characters, such as a single quote. I.E.
shell("C:\Program Files\MyApp\ModelScale_DBP.exe '" & Me.ModelPath.text & "'")
which ends up looking like
The reason for the quotes is as follows:
When you drag a file onto an EXE, windows starts the exe, and passes the path of the dragged-on file. This information is contatined within double quotes (
" ). So, it makes sense to allow the user to drag a file onto the exe, or to launch it from within the main program. If you like, I could show you the DBP code that removes the extra characters from around the passed-file's path.
As for what I said about storing information in a common directory:
In the
Hud and MuzzleFlash Positioner, a sub module of
Weapon Creator, you position your Hud.x model. The position data is then written to a common directory, in this case "C:\Program Files\WeaponCreator_AUX". Then, when my program needs that info, it just checks the file in that common directory. There's some
code in the code snippets board that shows how to get the Program Files directory.
Later,
Codemaster
