If we like to do it like this the right function to create a link actually would be
IPersistFile::Save since this is the place where the information gets flushed
to disk. How do you like to handle things like working directory and
parameters?
With the place you choose your program might be happy but others will
create toons of links:
---
IShellLink::GetShowCmd
Retrieves the show command for a shell link object.
---
Second point: how do I switch it off? I use KDE and many others do.
I may once implement writing native *.lnk files. We would need a point to
switch between this 3 choices.
Third Point: since we likely going to have more code like this for window-
manager integration we night want to create special directorys for
kde and gnome.
juergen
Date forwarded: Fri, 21 Jul 2000 09:57:06 -0600
Date sent: Fri, 21 Jul 2000 17:49:01 -0500
From: Brian <[EMAIL PROTECTED]>
Send reply to: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: linux linking
Forwarded by: [EMAIL PROTECTED]
> This patch gives IShellLink::SetPath the ability to create a kde and
> gnome link to the program based on its windows directory. This works
> definitely in RH 6.2, not sure under other systems. It provides an icon
> interface under a subdirectory named winefiles in the application
> section of the kde/gnome start menus. There are two seperate files
> attached, one is the program file itself, which belongs in the
> wine/dlls/shell32/. directory and the xpm which I put into
> wine/linuxIshell/. directory (and needs to be there for a proper
> reference to be made to it from the linking function.
> -Brian
>
> files: kdelinkmaker.c directory: wine/dlls/shell32/.
> wine.xpm wine/linuxIshell/.
>
---
[EMAIL PROTECTED]
... from sunny Berlin
