forum.vdsworld.com

LiquidCode

Is there a way with API to get all the info from a shortcut? I know @file() can get the path from a shortcut, but I would like to get everything. Like any parameters, start in folder etc.

Thanks

DaveR · Posted: Tue Jun 26, 2007 4:34 am Post subject:

I've found that the easiest way is to read the file with @iniread() as *.lnk files are just ini files (as are *.url internet shortcuts).

You can't open them with say notepad to have a look as notepad opens the file that the link points to. But you can load the file into VDS list and use @text() to have a look at it.

EDIT All of my statement above is wrong.

jules · Posted: Tue Jun 26, 2007 8:52 am Post subject:

I never knew that! It's incredible, when you look at the complicated COM code Microsoft says you have to use to get information from .lnk files ...

vdsalchemist · Posted: Tue Jun 26, 2007 1:07 pm Post subject:

vdsalchemist · Posted: Tue Jun 26, 2007 1:11 pm Post subject:

LiquidCode,
It is just 2 functions maybe I will add them to my GadgetX.dll so you don't have to lug around multiple DLL's?

DaveR · Posted: Tue Jun 26, 2007 2:36 pm Post subject:

Sorry for the partial misinformation Embarassed

. After I posted that I had to leave to go to work... & then I remembered that while *.url files use the ini format, *.lnk files are binary.

On a similar topic *scf files use ini format. And the *.msc Common Console Documents use xml format, as do manifest files.

LiquidCode · Posted: Tue Jun 26, 2007 6:20 pm Post subject:

Thanks for all the info. dragonsphere, I want to keep this program to one exe and as small as I can. If the dll for the shortcuts is small, I would rather have that then along in the GadgetX. I will only be using the shortcut functions.

Thanks!

vdsalchemist · Posted: Tue Jun 26, 2007 6:37 pm Post subject:

LiquidCode,
I have already added this ability to GadgetX. GadgetX is only 122kb? I can still make you a VDS DLL just for this if you like?

LiquidCode · Posted: Tue Jun 26, 2007 7:14 pm Post subject:

I wouldn't mind if it's not too much trouble. If it is a pain, I'll just use GadgetX.

vdsalchemist · Posted: Tue Jun 26, 2007 7:58 pm Post subject:

Chris,
I have already got a seperate VDS dll working for you. It will probably be around 20kb in size when finished. I am building some demos and will start working on the documentation.

LiquidCode · Posted: Tue Jun 26, 2007 8:43 pm Post subject:

Great! thanks a bunch!

LiquidCode · Posted: Tue Jun 26, 2007 9:32 pm Post subject:

On more thing. Embarassed

Is there a way to change information in a .lnk w/o recreating it? Like file location and parameters?

vdsalchemist · Posted: Wed Jun 27, 2007 2:09 pm Post subject:

I already thought of that Wink

With my DLL you will be able to update individual parts of the Link without the need to completly recreate the link. You will also be able to clear out individual parts of the Link without affecting other parts. For example if your link has Arguments and you want to remove those arguments you will be able to without the need to recreate the link.
Sorry it is taking a little longer than expected but I wanted you to be able to set Hotkeys using the same syntax as the HOTKEY command in VDS instead of trying to figure out the hotkey from it's numeric value. I have hotkeys completed now. Also you will be able to change the show command using words instead of numeric values.

The only thing you will not be able to do at this time is set links to Non-File objects. The reason is because you would need to get the Non-File objects PIDL list which is not possible with VDS unless you use GadgetX.

LiquidCode · Posted: Wed Jun 27, 2007 3:13 pm Post subject:

Cool Thanks! I'm not sure what you mean by non-file object?

vdsalchemist · Posted: Wed Jun 27, 2007 3:41 pm Post subject:

Hmmm how can I explain Non-FileSystem Objects? I guess the easiest to understand would be objects that resolve back to a registry entry. Like the reason why there is a difference when you tell the Desktop to show the Internet Explorer Icon and when you copy a shortcut to Internet Explorer. You can see the difference by right clicking your desktop and choose properties from the context menu. When the properties dialog opens choose the Desktop tab. If you are on Windows XP click the Customize Desktop button. A desktop Items dialog should show up. In the Desktop Icons group box check the Internet Explorer check box. You should now see and Icon for Internet Explorer on your desktop. If you right click that icon and choose properties from the context menu you will see your Internet Properties and not the shortcut properties. If you just create a shortcut to Internet Explorer you will see the shortcut properties. This is also true for the My Documents, My Computer, My Network Places, and Recycle Bin icons. Eventually they all resolve back to the file system but the icons do not go directly to the file system.