Randem Systems Support Board

InnoScript => InnoScript - General Questions, Report Bugs, Problems etc... => Topic started by: jans on June 23, 2009, 02:08:39 AM

Title: Quick Launch Icon
Post by: jans on June 23, 2009, 02:08:39 AM
Hi,
 
I tried to create a QuickLaunchIcon by selecting it in the Parameters list. InnoScript produced a code refering to:
{commonappdata}MicrosoftInternet ExplorerQuick Launch
When trying to install no QuickLaunchIcon is shown, although the shortcut is installed in the right directory.
When using:
{userappdata}MicrosoftInternet ExplorerQuick Launch
After install there is a shortcut in the quicklaunch bar which works.
 
Is the problem some setting in the receiving PC?
Is there a way in InnoScrript to get the quicklaunch working?
Title: Quick Launch Icon
Post by: Randem on June 23, 2009, 12:15:28 PM
I will check on that. Are you installing on Vista or XP?
Title: Quick Launch Icon
Post by: Randem on June 23, 2009, 12:54:24 PM
I check and you are correct the folder should be {userappdata} not {commonappdata}. This has been changed for the next version. In the meantime place the line with {userappdata} in a template file and it will automatically replace the current line on the next conversion in InnoScript.
 
Thank you for reporting this issue.
Title: Quick Launch Icon
Post by: jans on June 23, 2009, 07:49:53 PM
Your welcom,
 
I was installing on XP
 
Adding the whole line works.
 
Is it possible in a template to just order a replace of {commonappdata} with {userappdata}?  
Adding the whole line makes it inflexible for changes.
 
Thanks
Title: Quick Launch Icon
Post by: Randem on June 23, 2009, 08:07:46 PM
No, you cannot add just one item in the line. It was designed to add/replace whole lines. What were you thinking about replacing in the line that you would need replacements on that level?
 
I need to understand what the procedure would be...
Title: Quick Launch Icon
Post by: jans on June 23, 2009, 08:39:18 PM
In this case a simple search and replace of {commonappdata} with {userappdata} could solve the problem for the moment, also when changes were made to the name of the exe file, when putting it into a standard template added to each project.  
(of cause only when no other use is made of{commonappdata} )
 
I don't know if it would be of some general use.
 
;)