Icon for Project

[billhsln]

When you build single programs you can pick the icon on the build menu.  How is this done for a project.

Thanks,
Bill

[LarryMc]

add an ICON resource and assign it an ID of 1

[billhsln]

Isn't 1 default for VersionInfo?

Bill

[LarryMc]

you can have multiple #1's for VersionInfo and ICON and Manifest I believe.

[Andy]

If I remember correctly I had to also add the line........

SETICON win,hIcon

after opening the first window of my program.

DEF win:window
DEF hIcon:UINT

OPENWINDOW.........
...
....
.....
SETICON win,hIcon

Andy,

[billhsln]

Well it definitely seems that Projects are more complicated then single programs.  This is the first 'Project' I have ever done.  The only reason I needed it to be a Project is because the friend I am writing the program for uses an antivirus program that says it has a virus.  However, now that it is a 'Project' it no longer comes up as virus.  Of course I did have to add the 'VersionInfo' Resource to make it work.  An awful lot of trouble for a Antivirus program that will not update their software to show that our programs are not virus's (Sp?).

Thank you, Larry and Andy for your help.  Will find an Icon to add in and add in the needed code.

I should have asked, this will make it the icon that shows on the desktop, right?  Just making sure.

Thanks again,
Bill

[billhsln]

Found this:

Confused as always!

The Resource Compiler help puts an ICON resource type number at 3, which works for me (24 bit)

In my latest program, I have a 64x64 icon at 3, and a 16x16 icon at 101, which puts a small icon on the titlebar (256 shades)

I know you should have a lot more sizes and bit depths, but 64x64 works at most view sizes, without bloating the program's size

Brian

in:  http://www.ionicwind.com/forums/index.php?topic=5564.0

Tried it and it worked just like I needed.

Bill

[Andy]

Glad you got it sorted!

Ah yes - the wonderful world of false positives by A/V programs....

I did "discover" the following things:

1. Even the simplest of programs can be flagged.
2. Building as a project rather than a single cuts down "for some reason" false positives.
3. Adding copyright / file version in a resource file cuts them down even more.
4. If all else fails... send false positive reports to the A/V companies in question.
5. Remember, if you make even a small change and re-compile it - it could be flagged again.
6. Some A/V companies are "impossible" to contact.
7. Be careful what you call your exe file!

Some time ago I asked my client what did they want the program to be called, eventually they came up with the name "AutoScan".

Unfortunately, the words "Auto" and "Scan" sound like a potential virus and it took a good while to clean them by sending false positives to the A/V companies.

I did note that one image I was using which was rectangle rather than square seemed to cause false positives! - I changed it to a square and loaded it as a scalable image so it would be rectangle on screen, and the false positives went away???

Anyway glad it's sorted,
Andy.