From: SourceForge.net <no...@so...> - 2003-01-09 21:28:24
|
Feature Requests item #665325, was opened at 2003-01-09 14:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373088&aid=665325&group_id=22049 Category: None Group: None Status: Open Priority: 5 Submitted By: Eric Weddington (arcanum) Assigned to: Nobody/Anonymous (nobody) Summary: CreateShortCut sucks Initial Comment: CreateShortCut in 2.0b0 sucks. The docs say that $OUTDIR is used for the working directory. This breaks the semantics of $OUTDIR. When I call CreateShortCut, the installer creates it in the directory where the installer resides. I then have to copy or move the shortcut to the directory I want to put it in, typically in $DESKTOP and $SMPROGRAMS\whatever. The working directory for the shortcut should be (another) parameter to CreateShortCut. I would like to be able to do: SetOutPath "$DESKTOP" CreateShortCut ... SetOutPath "$SMPROGRAMS\whatever" CreateShortCut ... Thanks. Keep up the good work! FYI, I use NSIS as the installer for the WinAVR Project: http://sourceforge.net/projects/winavr Eric ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373088&aid=665325&group_id=22049 |
From: SourceForge.net <no...@so...> - 2003-01-09 21:38:54
|
Feature Requests item #665325, was opened at 2003-01-09 23:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373088&aid=665325&group_id=22049 Category: None Group: None >Status: Closed Priority: 5 Submitted By: Eric Weddington (arcanum) >Assigned to: Amir Szekely (kichik) Summary: CreateShortCut sucks Initial Comment: CreateShortCut in 2.0b0 sucks. The docs say that $OUTDIR is used for the working directory. This breaks the semantics of $OUTDIR. When I call CreateShortCut, the installer creates it in the directory where the installer resides. I then have to copy or move the shortcut to the directory I want to put it in, typically in $DESKTOP and $SMPROGRAMS\whatever. The working directory for the shortcut should be (another) parameter to CreateShortCut. I would like to be able to do: SetOutPath "$DESKTOP" CreateShortCut ... SetOutPath "$SMPROGRAMS\whatever" CreateShortCut ... Thanks. Keep up the good work! FYI, I use NSIS as the installer for the WinAVR Project: http://sourceforge.net/projects/winavr Eric ---------------------------------------------------------------------- >Comment By: Amir Szekely (kichik) Date: 2003-01-09 23:40 Message: Logged In: YES user_id=584402 Use CreateShortCut with a full path... For example: CreateShortCut "$SMPROGRAMS\bla\wwhatever.lnk" "$INST DIR\myprog.exe" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373088&aid=665325&group_id=22049 |
From: SourceForge.net <no...@so...> - 2012-05-18 00:34:49
|
Feature Requests item #665325, was opened at 2003-01-09 13:30 Message generated for change (Comment added) made by jmichae3 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373088&aid=665325&group_id=22049 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Priority: 5 Private: No Submitted By: Eric Weddington (arcanum) Assigned to: Amir Szekely (kichik) Summary: CreateShortCut sucks Initial Comment: CreateShortCut in 2.0b0 sucks. The docs say that $OUTDIR is used for the working directory. This breaks the semantics of $OUTDIR. When I call CreateShortCut, the installer creates it in the directory where the installer resides. I then have to copy or move the shortcut to the directory I want to put it in, typically in $DESKTOP and $SMPROGRAMS\whatever. The working directory for the shortcut should be (another) parameter to CreateShortCut. I would like to be able to do: SetOutPath "$DESKTOP" CreateShortCut ... SetOutPath "$SMPROGRAMS\whatever" CreateShortCut ... Thanks. Keep up the good work! FYI, I use NSIS as the installer for the WinAVR Project: http://sourceforge.net/projects/winavr Eric ---------------------------------------------------------------------- Comment By: Jim Michaels (jmichae3) Date: 2012-05-17 17:34 Message: doesn't work like that. he said "working directory". that means "default directory windows cd's into before running the app". and yes, I don't like it either. you *do* have to set $OUTDIR in order to set the working directory for the shortcut. I don't exactly know why this is, but it is, and I don't think it should be this way. there *must* be a better way of some kind. to see how this works, create on your desktop a shortcut to c::\windows\system32\cmd.exe and set the "start in" directory to your favorite directory. then after you have clicked ok, double click on it and watch what happens. this is the same effect. most people who want to set the working directory in a shortcut want to do this with only about 2-3 parameters in CreateShortCut. as things are now, we have to do this: Push $OUTDIR SetOutPath "${workingDir}" CreateShortCut "'$SMPROGRAMS\$StartMenuFolder\${PRODUCT_TITLE}.lnk" "${targetAbsFilepathOrUrl}" Pop $OUTDIR ---------------------------------------------------------------------- Comment By: Amir Szekely (kichik) Date: 2003-01-09 13:40 Message: Logged In: YES user_id=584402 Use CreateShortCut with a full path... For example: CreateShortCut "$SMPROGRAMS\bla\wwhatever.lnk" "$INST DIR\myprog.exe" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373088&aid=665325&group_id=22049 |