I've been just simply dragging and dropping my icons to a package builder folder I'm working on. I'm saving them one by one as I go along so that I won't have a bunch of them to do when the package is done. Periodically, when I've applied a new icon, after I save the package, the icons save to the wrong folder. For quite a while they would save in the appropriate folder, but now I'll get my cd folder saving to my scheduled tasks folder. Just today, I had about 5 out of 20 save to the correct folder but the other 15 didn't.

I've tried going back to redrag and drop them, sometimes with success, sometimes without.

Anyone else have this issue? Thanks for any help anyone can give.

Donna

Comments
on Aug 30, 2005
Gotta bump this I'm afraid.

I'd really like some feedback on this, if possible.


Anyone?
Thanks.
on Aug 31, 2005
You keep using the word folder, when I think you mean something else. I'm having trouble understanding ...... When you save, the icons should be saved as a package, in the IconPackager Themes folder...... not to separate folders.

but now I'll get my cd folder saving to my scheduled tasks folder

Do you really mean the CD icon is being saved as the Scheduled Tasks icon?

Perhaps if you reword your description of the problem, and explain 'exactly' what's going on, someone may be able to help.
I apologize if I'm simply being dense.....

on Aug 31, 2005
I think it's me who's being dense here, Koasati.

They all do stay in the correct folder. It's the icon that is not saving as the correct icon.

Sorry about the way I wrote that first post.

Donna
on Aug 31, 2005
Screen shot!
I need a screen shot with arrows and charts and stuff.

Are you saying for example: all the icon for bmp is got a big w on it? the icon for a word doc is an avi icon? like that?
on Aug 31, 2005
Donna,

Suggest foregoing the incremental save, and just save all images to a folder and build when done.

If you really want to do the incremental save, I would suggest applying the package each time.

I have seen a small issue when creating a custom package, in that - it saves as an icon package file, but is not displayed in Icon Packager configuration list until one double-clicks the package to apply - then it is shown in the list.

Note - I have not experimented with this, but noticed it when creating one custom package on my system.

It could be that applying it writes the icons permanently to their assigned positions each time, and that not applying each time you modify is in some way not being interpreted correctly.

Not a coder, so not sure - just thought I would throw that in.