Help
Published on January 3, 2006 By DanielFlaco In IconPackager
Ok I have all my icons made and the pack, but I'm having trouble adding a subpackage. I created a second pack then added it as a subpack
and it worked on the computer I created it, but when I zip it for distribution and installed it on a different computer the subpack didn't work. So I tried to edit it in the subpack button and it shows but is looking for the file path or in other words a second Pack wich is kind of dumn if you need to have both packs for the subpack to work. I created the two packs on my home Computer then I just added it 1 as a subpack and works on there but it didn't work on another computer.
Can anyone tell me what I'm doing wrong. or is there a tutorial on how to created subpackages.

Comments (Page 2)
2 Pages1 2 
on Jan 11, 2006
I received 14 emails over a 15 hour period yesterday confirming they received my ONE email. If I go by that, it'll be 48 hours from the first/last one they sent me (?)..which will either be 7:38 Thursday morning or 4:27 that afternoon.

I'll wait the 48 before I take any further action. This is only the first time I have ever had a problem with any of the software.
on Jan 11, 2006

I also have been successful in creating the ".packages" file, but no ".subpackage" file in the sub-pack folders.

The folders do exist outside of the parent folder with the Apogee pack. So you get the "Apogee" folder, "Apogee (Amber)" folder, "Apogee (Black)", "Apogee (Blue)", etc.

Mormegil uses the "Save package as individual icons" option in IconPackager\Settings category, which results in a folder with all icons available for copying to another folder (for say ObjectDock use).

The parent "Apogee" folder has icons, ".iconpackage" file, and the additional ".packages" file - while the sub-package folders have the icons that are different than the parent, and the ".subpackage" file only.

I have been able to create packages (which I save to the IconPackager\Themes sub-directory), and then assign them as sub-packages (and shows them in the drop-down list inside parent listing) - but this still leaves the packages which were added as sub-packages listed in the normal list as well. I have not found a way around this, nor how to create the ".subpackage" file - which I believe to be the key to the issue.

IMHO - An updated "Help" file is a must in this version.

on Jan 11, 2006
Well! thanks for trying to help. I had already done everything you describe runninig into the same problems. I guess we will just have to wait until Stardock decides to release a step by step tutorial.
on Jan 13, 2006
An updated "Help" file

Your version has a HELP file????

Is it like mine...



I've gotten more help in the forums and tutorial articles.

Patience is a virtue.
on Jan 13, 2006

I've gotten more help in the forums and tutorial articles

Yes, I have the same one.....

I create documentation at work, and I must agree that this one needs serious work - ASAP.

One difficulty with releasing updates/upgrades, or making any changes for that matter, is the need for a dedicated documentation division to complete the process professionally. I have to assume that the current staff size at Stardock does not support this need, which I see in many products by other companies as well.

Microsoft relies greatly on authors who use their product to provide competent documentation outside of the Help files - though none of the them are volunteers, so obviously food can be put on the table while writing.

Hopefully, we will see something here at WC, or at the Stardock site to support the new feature.

on Jan 14, 2006
This is from another thread and explains the subpackage issue. It was posted my mormegil who is putting together the Apogee update.....

Po, All you have to do is make sure you have 3.1 then make your main pack. in package builder create your subpackages. Then create your parent package, in package builder you will see a ?????? button, I dont know why this is, named that way. I will yell at brain abou that. Anyway. Here you add new sub package. You can add as many as you want.

PS. If you want to just do it in the package file. There will be a, .packages file as text file and enter them that way. the format is.

[Apogee (White)]
File=..\Apogee (White)\Apogee (White).subpackage
LoadMain=1

You will not the subpacks are called .subpackage, this is the same as .iconpackage, except it hides them in the main list.

I am sure we need to get some UI tweeks in to make it a bit esyer to make these. But it is quite simple even now, once you know were to look.


I'll be trying it out. Let me know how it works for you.
on Jan 16, 2006
This is exactly what I did before even posting this article for help. I created the main pack then the subapacks in packedge builder. But like I said it worked fine I had no problem adding the subpacks. The problem came When I tired to Zip it for distribution, I wouldn't include the subpacks in the packs.But I'll try it again may be it will work this time around.
on Jan 16, 2006
This is exactly what I did before even posting this article for help. I created the main pack then the subapacks in packedge builder. But like I said it worked fine I had no problem adding the subpacks. The problem came When I tired to Zip it for distribution, I wouldn't include the subpacks in the packs.But I'll try it again may be it will work this time around.
on Jan 16, 2006
I think the bottom line...but DON'T quote me on this...is that the APogee Icon Pack has it's OWN installer?????....and probably the ability to do what we are trying to get IconPackager to do...but I am not sure. I have been posting back and forth with Paul(mormegil) about it and am waiting for a reply to my last post.

What I beleive you/we may have to do until IconPackager is tweaked is to put the parent file folder and subpack folders into one regular zip folder to upload it, with instructions on where to put everything.

The only thing I gleamed from his posts that I hadn't been doing was to change the extension on the subpackages from ".iconpackage" to ".subpackage" on the actual file and in the ".packages" document (which you may need to go into it's properties and set it to open with notepad).

Here's the link to the thread...you can see his comments and that I have tried to zip this stuff in every kind of arrangement possible with no luck. I am 'still' waiting for my response from SD Support and will probably resubmit the email.

Link
on Jan 16, 2006
Thanks a lot that would be very helpfull. And from what I'm hearing sounds like Stardock hasn't figured out this subpack issue. But we'l just have to wait I guess.
2 Pages1 2