Extensible Config Page doesn't work
No one really cares about this but me, but this will document this issue so I can keep track of it.
I put in the ability for a plug-in to extend the config page. This works great in that the option shows up and the custom config page works as well. The problem is in the fact that that config page has no way to reference anything inside the plug-in. It only has a pointer back to the application.
There needs to be some way for the config page to bind to information that is a part of the plug-in or this page is pretty useless…
I care!!! That’s why I left the vanilla options in the MB release!
Okay, well, I'm working on it. Hopefully, I can figure something out…
This has got me pulling my hair out. I actually have a solution designed and implemented and it WORKS – as long as I'm running a debug build. Doesn’t work with a release.
Ugh…
I've got this licked. I'll get the templates updated to include how to do it and get them uploaded later today.
Okay, this is all done and checked in. Whew.
Throg – if you want to update V2, re-import the plug-in template from the new one in the trunk. Then, create a new project based off of it and you will see what needs to be done to make the config page work.
Basically, you need a ‘MyConfig’ (or whatever) class that inherits from ModelItem and you need to pass that to the AddConfigPanel method. Then, your configPanel takes that object as a parameter (just copy the template-generated config panel to start) and you can bind to its properties as normal.
