I'm using some iPacks in addition to using IconPackager. This has caused some issues as when I make a change in IconPackager it will completely revert 100% of the changes I've made using an iPack package (in case you don't know, iPacks are self installing icon packs that use an executable to change a bunch of the icons using dlls).
I realize that this may garner a response of "Well that's the iPack's problem not ours" but the issue here is NOT that the IconPackager application is simply overriding or conflicting with the iPack installation. When I go to look at files using the IconPackager I can still see all the iPack icos contained in the image.dll etc. It merely appends to the system files, it doesn't actually delete them. So it seems to me that there should be no reason why IconPackager shouldn't be able to just keep it's hands to itself and not interfere with the other program. I know development is not easy but I work as a developer and this seems to be poor containment of the code that IconPackager is executing.
Also this is my second post today, but I decided to make multiple posts so as to keep the specific issues I'm having in separate threads. Keep things tidy etc.