Let’s get one thing straight.

Menu is probably the most complex part of skinning. We know well after doing around 1000 skins in the last 3 years. Salaro team is large and developers come and go. Each menu takes time and the complex ones take a long time to do and sometimes the developer may have spent weeks working it out in his head. Even commercial Menu products like Telerik are as complex or in my opinion can be even more complex than solpart. Questions put to Telerik may never get answered because this is just the nature of the beast. Basically even they dont know all the possible combinations of what can be done and what cannot. Bugs exist all the time and things get better with time and this is just the way this business works.

If one is pushing the boundaries of what a menu can do too far then it takes time and may be money to get it right. Otherwise just use what you can deal with and your problem will be solved. IMHO cutting edge documentations exists only in developers head and sometimes because of language barriers they are unable to articulate it or simply pressure of life in other directions does not give them the bandwidth to give time to this.

Salar

On the subject of using commercial DNN Menus in skins for resale I just wanted to add that the developrs edition of the Snapsis CSS NavMenu 3.0 has recently been released with a very liberal license for skin developers to reuse it in their own skins.

The new template driven system is also becoming very popular as it allows you to build virtually any type of menu for DNN and include the template in your skin.