Explorer-view drag-and-drop shortcut/lnk files

RichMacDonald wrote on 5/22/2004, 5:08 PM
Is it just me or does Vegas not handle lnk files, i.e., shortcuts to files stored elsewhere? When I select the lnk file, I get no information besides the path. When I drag-and-drop an lnk file (a shortcut to an avi file) onto a track, it is disallowed.

This is quite annoying because lnk files are a good poor-man's filing system. Say I have 30 avis that will be made into 10 dvds for 10 different people...organized by whose kids appear in which avi, naturally :-) So I created 10 folders and tossed in shortcuts to the 30 original avis. Within each folder, I now need to do some Vegas work. Too bad I cannot use the "avis" (lnks to avis, I mean) in these folders.

Perhaps someone can tell me if this is also how Vegas 5 operates. If not, I humbly suggest to Sony that they add this feature. Simple to add, useful for some, correct Windows behavior, IMHO. Thanks.


---------- EDIT ------------------

Ahem. Upon further review, it looks at though Vegas handles lnk files just fine when they are good links. When the shortcut links to a file that doesn't exist...then Vegas has a bit of a problem. Good Vegas, Bad User :-)

Sony: Since you already have the lnk feature, how about a bozo button for this forum allowing users to remove their own threads?

Comments

jetdv wrote on 5/22/2004, 9:54 PM
how about a bozo button for this forum allowing users to remove their own threads?

There IS a delete button for your posts. If your post is the only post in the thread, it will also remove the thread.
RichMacDonald wrote on 5/23/2004, 7:29 AM
>If your post is the only post in the thread, it will also remove the thread.

LOL. The only way to tell me about it was to prevent my ability to use it :-)

Incidentally, I continued to have wierd behavior with shortcuts last night. I had one mpg link that Vegas refused to deal with, however, double-clicking it launched Windows media player and played it just fine. But this is now a minor issue, so let's just stick to the user-error story and move on.