Easily see shortcut icon

[NewsArchive]

Is there any way to easily see the icon that is set up in the shortcut,
without having to go through the whole process of reselecting the file and
the icon.

I have instances where the order of the icons have changed from compile to
compile ..and instead of my nice startup icon, i get a green ball, or some
other icon that occupies the old icon resource space...

See image

Ben

[NewsArchive]

Ben,

As you can see, there is no "local" information available that points to the
file on your development machine. %_SB_INSTALLDIR%\FIN6.EXE is a location on
the target machine. Because a shortcut is created on the target machine, it
does not have any reference to the development machine.

Friedrich

[NewsArchive]

Hi Friedrich,

>As you can see, there is no "local" information available that points to the
>file on your development machine. %_SB_INSTALLDIR%\FIN6.EXE is a location on
>the target machine. Because a shortcut is created on the target machine, it
>does not have any reference to the development machine.

If the shortcut relates to a .exe that is in the install, can't it
track back to it on the dev machine as it certainly needs that to be
able to create a shortcut to it?

I.e. you have:

C:\products\myproduct\whateverfolder\myexe.exe

You install it into %_SB_INSTALLDIR%\Whatever\myexe.exe

You create a shortcut to this file. Shouldn't that be relatable (if
that's a word<g>) back to the local file?

Best regards

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

Unfortunately, this is not possible. It may work in your specific case (if
you have a fixed, fully qualified path name). In this case, it should be
possible to "scan" through the whole script to find the source code location
for %_SB_INSTALLDIR%\Whatever\myexe.exe. But it does not work if you have a
compiler variable in your source folder (and most developers use compiler
variables as source path to make the project portable and machine
independent).

For example:

[SB6_POOL]\sbuilder.exe is installed into %_SB_INSTALLDIR%\sbuilder.exe

The compiler variable is only available at compile time and cannot be
resolve at script development time.

-or-

C:\products\myproduct\whateverfolder\myexe.exe

You install it into %MY_VAR%\Whatever\myexe.exe

%MY_VAR% is set to %_SB_INSTALLDIR% in the script.

There is absolutely no way to resolve %MY_VAR% at development time.

The IDE would not be able to find the source location and so it's (IMO) not
worth the extra 8-12 hours of development time to implement this "partial
working" feature <g>. We have exactly 453 items on the wish list now (101
items are already code complete), so I have to set priorities (especially if
it will take at least a full day to implement it). But of course, if there
really is an interest in that feature, I'll add it to the list ;-)

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.6
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi

what other options do you have available

Is this then a required step each time you build an installation for a app
file ????

Ben

[NewsArchive]

Hi Ben,

> what other options do you have available
>
> Is this then a required step each time you build an installation for a app
> file ????

I think I don't understand the question :-( Do you mean "options" for other
(resource viewer) tools to get the index of an icon or do you mean options
in SetupBuilder?

Friedrich

[NewsArchive]

Hi

Option in Setupbuilder....

Our products are sold on the basis that the client can request development,
so our products don't always have the same resources associated with the
same resource ID.

At this point I can not 'auto build' releases, I have to go through each one
manually and check that the resource id used in the links is still the
correct one as originally specified.

This is very time consuming and painfull boring...

Kind Regards

Ben

[NewsArchive]

Hi Ben,

> Option in Setupbuilder....
>
> Our products are sold on the basis that the client can request
> development, so our products don't always have the same resources
> associated with the same resource ID.
>
> At this point I can not 'auto build' releases, I have to go through each
> one manually and check that the resource id used in the links is still the
> correct one as originally specified.
>
> This is very time consuming and painfull boring...

There is no option because it's not possible from the technical point of
view. The Shortcut is created on the target machine and there is no
reference to the application at development time (runtime variables are only
available at installer run-time). Files and Shortcuts are completely
differen objects.

Use the built-in Icon Viewer in SetupBuilder or an external resource editor
to retrieve the index of the icon.

Friedrich

[NewsArchive]

Thanks... now the other painfully slow item is creating the Create
Subscription Key standalone or comamnd line callable utility

Ben

[NewsArchive]

> Thanks... now the other painfully slow item is creating the Create
> Subscription Key standalone or comamnd line callable utility

Yes, you are right. Unfortunately, making new features available is a
priority-driven processes.

We'll open registration for the SetupBuilder "Subscription Key Bulk
Generation" tool soon. This tool will not be part of the standard
SetupBuilder installation and has to be requested separately.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.6
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner