04-25-2023 02:14 AM
I've tried using the editor, i've tried using a free .ico from web... it doesn't matter. In the end, the .exe will look as below, in the attached capture.
04-25-2023 08:13 AM
This is an example of an Icon I built with IconEdit2 -- it is for a test routine we called "Cinnamon" (I just pasted the .ico file on my blue desktop). This happens to be a 256 x 256 pixel icon (to make the image pretty).
Bob Schor
04-25-2023 09:29 AM
Which version of LabVIEW are you using?
Please post your .ico file.
04-25-2023 09:40 AM
It looks cool. Did you have any issues seeing the icon in the finished executable?
04-25-2023 09:55 AM - edited 04-25-2023 10:31 AM
I'm using LabVIEW 2020.
"Icon" is the one downloaded from the web which worked so far up to the moment i've written to this topic.
"TeMaCoN_Icon" is the one developed in labview icon editor.
Is there anything else i should check in any other submenu ?
None of them are working right now.
04-25-2023 10:17 AM
I find LabVIEW frustrating inconsistent with icons. Sometimes I have found that the first icon you try is the only one that works, for evermore. Sometimes the icon doesn't appear at all. I don't have any insight into what's causing this. Some people don't appear to have any issues, which in itself might be a clue. Perhaps the root cause is something else.
04-25-2023 11:30 AM
It seems LabVIEW remembers the old icon.
Even "Clean" the build doesn't work.
I have to create a new build script to update the icon.
04-25-2023 05:15 PM
George,
Your post reminded me of a problem I haven't thought about in years! Particularly when creating icons, sometimes things go awry, and updates for the Icons don't seem to work. Turns out that Windows has an "Icon Cache", so if you edit an Icon, you might have a lovely Icon, but it won't be "attached" to your executable because Windows says "Oh, I already have an Icon for that, I'll just use the one in the Cache".
Do a Web search for "Windows Icon Cache", and you'll find where "IconCache.db" is hidden in your Profile. Follow the instructions to delete it and see if that fixes the problem. [It does entail a trivial delay when you reboot and Windows rebuilds the cache, but you will probably not notice it ...].
Bob Schor
04-25-2023 06:05 PM
iconcache_48.db and iconcache_32.db haven't modified for ~3 years.
So iconcache is likely not the problem.
04-27-2023 12:10 PM
@zou wrote:
iconcache_48.db and iconcache_32.db haven't modified for ~3 years.
So iconcache is likely not the problem.
I would not make that assumption with MS OS.