ICO is to ICL as EXE is to DLL (except for the dynamic linking). Are you
saying you want to make an icon library that will execute? Execute what?
--
dadiOH
____________________________
dadiOH's dandies v3.06...
...a help file of info about MP3s, recording from
LP/cassette and tips & tricks on this and that.
Get it at http://mysite.verizon.net/xico
> Is there a freeware to do this? I googled but didn't find anything.
> thx :)
If you already have *.icl files, you only need to rename them to
*.dll. The *.icl libraries are actually *.dll files, containing
just icon resources.
To create or edit *.icl files, you may have a look at IconShop
from LionTech:
http://users.pandora.be/liontech/Downloads.htm
But since you asked about *.icl files as conversation source, you
may already have a tool for this task at hands...
BeAr
--
===========================================================================
= What do you mean with: "Perfection is always an illusion"? =
===============================================================--(Oops!)===
This is really a programming task involving building a "resource only"
DLL - see for instance
http://www.dolphinmap.net/wiki/Building_Resource_Libraries
http://www.vb-helper.com/howto_icon_dll.html
If you're not a programmer though, it might be possible to use the
free Resource Hacker http://www.angusj.com/resourcehacker/ something
like this:
o Find a little DLL and make a copy of it (rename as desired)
o Open in ResHacker
o Follow the instructions in the help file under "Adding icons or
bitmaps".
I don't think it can add ICL files as a resource, so you may have to
first extract all icons of interest in the ICL to a folder, using
something like ABC Amber ICL Converter - http://www.processtext.com/abcicl.html
HTH
Brian
Excellent! I never knew IconShop could do this. Much better than my
"manual labour" method! :)
Brian
>On Wed, 30 Jul 2008 15:37:19 -0700 (PDT), MitchellWMA wrote:
>
>> Is there a freeware to do this? I googled but didn't find anything.
>> thx :)
>
>If you already have *.icl files, you only need to rename them to
>*.dll. The *.icl libraries are actually *.dll files, containing
>just icon resources.
>
>To create or edit *.icl files, you may have a look at IconShop
>from LionTech:
>
> http://users.pandora.be/liontech/Downloads.htm
That's what I used to create the original ICL file with, thanks. <g>
>But since you asked about *.icl files as conversation source, you
>may already have a tool for this task at hands...
Well, so far, the results haven't worked, but I'm wondering if that
isn't because of another issue. So I'm researching the other before
discounting the fact that the resulting dll "didn't work".
I have AutoIt syntax to use for cycling through icons in a dll such as
shell32.dll. Shell32.dll works and the icons are displayed randomly.
When I switched the shell32.dll reference to my own coverted ICL->DLL
one, only the same old AutoIt icon is seen in the systray. No go.
So first am seeing if AutoIt isn't at fault, or if there is syntax
that will work instead of the one I'm using.
I'm also going to see how else to test the ICL->DLL file to see if it
a "true DLL", or whatever. Don't know how I'll do that, but will go
google. ::g::
Well, d'uh ...!!! The instant I went to my desktop, realized perfect
test would be to create a shortcut then change the icon, pointing to
the new dll and choosing one of the embedded icons in it.
Well, the renaming ICL to DLL sure DOES work there! So it may just
be that the syntax I have is geared primarily for something in
Shell32.dll. I'll go back to the AutoIt as possible source of
"malfunction" ::g::.
Will report back. And if I ever get syntax to work, will provide AI
syntax, too.
> Well, the renaming ICL to DLL sure DOES work there! So it may just
> be that the syntax I have is geared primarily for something in
> Shell32.dll. I'll go back to the AutoIt as possible source of
> "malfunction" ::g::.
Please note that *.icl files are often 16 bit *.dll files!
>On Sun, 03 Aug 2008 08:22:11 -0400, MitchellWmA wrote:
>
>> Well, the renaming ICL to DLL sure DOES work there! So it may just
>> be that the syntax I have is geared primarily for something in
>> Shell32.dll. I'll go back to the AutoIt as possible source of
>> "malfunction" ::g::.
>
>Please note that *.icl files are often 16 bit *.dll files!
>
>BeAr
Didn't know that, thanks.