Possible Bug: SkinObject(s) - Need CORE Team Advice

Hi All,
I'm currently working on a SkinObject to provide context sensitive help throughout DNN.  There's one problem that I'm having though: DNN won't parse my ControlKey as a skin object.
Here's what I've done:

Create a skinobject in code
Went to DNN > Host > Module Definations
Created a Module named "ContextualHelp"
Created a Defination named "ContextualHelp"
Created a Control with a key of "CONTEXTUALHELP" that points to my ascx file.
Created a container that has "[CONTEXTUALHELP]" in it.
Had DNN parse my container

I do see that there is a skinobject named "[Skin Objects]" that has a list of all the skin objects for the portal.  Am I supposed to be adding my skinobject into there?  Also, my skin object will have settings associated with it.  What is the "proper" way of tieing a settings page to an instance of a SkinObject (like what should I be throwing in NavigateURL and EditURL and such?).

Thanks!

MobileNow wrote:

Possible Bug: SkinObject(s) - Need CORE Team Advice I do see that there is a skinobject named "[Skin Objects]" that has a list of all the skin objects for the portal.  Am I supposed to be adding my skinobject into there?

Yes.

Also, you add settings to a skinobject via the skin or container that holds the skin object.   Use the skin.xml / container.xml.

MobileNow wrote:

Also, my skin object will have settings associated with it.  What is the "proper" way of tieing a settings page to an instance of a SkinObject (like what should I be throwing in NavigateURL and EditURL and such?).

SkinObjects do not support settings pages (regrettably so). It would be a great enhancement if this were possible...

cheers,

erik