[Doctor Eggs]

Excellent! What skin is the view for?

Aeon Nox Silvo. I contacted Mike to see if he wanted to put it into the skin. If he doesn't, I'll post the files that need to be updated in a separate thread.
 

I will code a new property for launchers called NumROMs. Once it is coded the infolabel will be $INFO[ListItem.Property(NumROMs)].

That will be awesome. Thanks!

Is there also a property that differentiates between Platforms and ROMs? I would like to have different text based on whether it's a platform vs. rom.
 

Can you post a debug log when the problem happens? Make sure you follow the instructions on the first post. In any case I will have a look ASAP.

In the mean time, export you launcher to an XML file, edit the XML to add a plot, and then import the edited XML. That should work right now. 

I'll go with the NFO import. Just saw all of the platform nfo files you have up in Git and that is awesome. I'll also post an error log when I get the opportunity.

1) Although I said I would focus on AEL starting from this week, I'm still working on AML and will release a new version soon. AEL views are 100% compatible with AML views, you can try your view with AML and I can code the property feature tomorrow. It will take some time (weeks) to code it in AEL.

I'll check out AML.

2) In AEL the number of object in a launcher depends if the display mode is Flat or Parent/Clone. In Flat mode you have number of ROMs, in Parent/Clone mode you have number of Parents. Should I add 2 different properties (NumROMs and NumParents), only one will be active at an given time OR Should I code a counter property NumObjects and then another property LauncherViewMode equal to Flat or PCloneHuh What is easier to code in the skin? In AML this situation is the same.

Two different properties makes more sense to me.