I have an app that needs to be called from a shortcut which passes
along command line arguments via the shortcut's command line, as well
as filename(s) via drag and drop.
Unfortunately, it seems if you drag and drop files to a Windows
shortcut, it decides to completely ignore the arguments specified
within the shortcut command line, and treats the first file as the
first argument. (At least that's what it does on 98).
Any windows experts out there have any ideas on getting around this?
Another possible workaround to the above I coudl use some help with:
If I had a way of determing the path of the shortcut .lnk file that
called my main application, I could probably work around the problem
by skipping using command line arguments in the shortcut at all. I
could instead write the arguments in the "comments' field of the
.lnk file when I create it. I could then check for the arguments
using the shortcut.dll extension from within the application the
shortcut is calling--if I knew of a way to determine which shortcut
called the application in the first place!
So....anyone know of a way to determine from an application which
shortcut (.lnk file) called it?
If anyone could offer help with either of the above two questions I
would be extremely greatful!
Thanks,
Daniel Barrett