I did get some work done, mostly cleaning up and working on the xml config code. It's pretty solid right now, allowing a lot of flexibility (mostly for future reuse in other projects). For example, the code will handle things like:
<Tag1 name="test">...</Tag1>
or
<Tag1><Name>test</Name></Tag1>
when looking for a name atrtribute in a particular node.
I know it's pretty esoteric, but I really want this xml config code to integrate nicely with the property tre control, for any number of other projects, so fairly complex config/option structures can be supported with minimal coding involved. I find this is one of the main reasons people don't add config options, is not only do you have to code the change, but you have to code all of this other crap on top of it to put it into a config window, such as placement on a dialog container, labelling the option, tooltips, etc. So with this method, it can all be done in an xml file fairly simply. With a two or three line function added to support looking up the new function.
I still think I have a good chance of getting an alpha version of this out the door this month (with the min focus being on DDE drag and drop type functionality).
I'll have to check Total Commander to see if it handles overloading the d&d like Directory Opus does.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Back from Geneva, had a good time.
I did get some work done, mostly cleaning up and working on the xml config code. It's pretty solid right now, allowing a lot of flexibility (mostly for future reuse in other projects). For example, the code will handle things like:
<Tag1 name="test">...</Tag1>
or
<Tag1><Name>test</Name></Tag1>
when looking for a name atrtribute in a particular node.
I know it's pretty esoteric, but I really want this xml config code to integrate nicely with the property tre control, for any number of other projects, so fairly complex config/option structures can be supported with minimal coding involved. I find this is one of the main reasons people don't add config options, is not only do you have to code the change, but you have to code all of this other crap on top of it to put it into a config window, such as placement on a dialog container, labelling the option, tooltips, etc. So with this method, it can all be done in an xml file fairly simply. With a two or three line function added to support looking up the new function.
I still think I have a good chance of getting an alpha version of this out the door this month (with the min focus being on DDE drag and drop type functionality).
I'll have to check Total Commander to see if it handles overloading the d&d like Directory Opus does.