BoxSetInfo version 1.6

The main reason why I wrote this update was that you would get a nasty error if your collection contained "ghost profiles" (see below). After fixing this I also added the option to show which boxset parents that have ghost children.

In addition to this I updated the runtime check, now showing both the calculated runtime for all child profiles, and the runtime entered in the parent, in parenthesis, for example "Runtime: 456 (432)".

I also corrected a minor anomaly. If HTTPJolie was active, double clicking a row in the main tab would use it, but in the two other tabs sendkeys would be used. Not a big problem, but HTTPJolie is faster and more reliable.

So, what are these "ghost profiles"? In DVD Profiler, a boxset parent can have child profiles that don't exist in your collection. You can't see them in Profiler itself, only in the XML export. Do they cause a problem? Not in normal Profiler operations (as far as I can tell). But they can cause external tools to malfunction. If they don't cause a crash, then might cause incorrect statistics.

Should you remove these ghosts (who you gonna call?) Well, it's not really necessary unless it's important to you that the XML export accurately reflects your collection in every detail. And if you want to remove them, then how, since they don't show in Profiler. Well, I found that one way to do it is to remove the child profiles from the parent profile, and then add them back again.