There seems to be quite the fuzz about how SCMDraft extensions work, and I just peeked a little bit on the surface - but I can answer some of the questions.
The current FAQ is not distributed with a compiled .sdp file (ScmDraft Plugin).
You are going to have to fire up MSVS and build the file. If you don't have MSVS, you can still look at the code, but I don't know if Dev-C for example can build libraries, I'd guess it can however.
1) What is a plugin, really?
A: The plugin is just a library of code that is linked to SCMDraft through being called by the host application.
2) How do I do xyz?
A: If you don't know how to go about a problem, you need to learn C++ first - it's a very complicated language and can NOT be taught on this forum. It has all sorts of memory aspects and such to consider. It might be possible to write these plugins in C too, I'm not quite sure at the moment.
3) My SCMDraft fails to load the plugin, it says so!
A: Download the latest SCMDraft - auto update may not work as intended either (bugs for me) - it should load fine. Read above if you just extracted all files into the plugins/.
4) The sample plugin has weird indention and such
A: I agree.
5) What does the author mean with "This is the whole trigger editor?"
A: It's a bad wording, he means that the part of code that does that is all the code written for that menu click.
QUOTE(Min @ Aug 7 2006, 06:55 AM)
If I had a decent C++ resource editor I'd be writing my own trigger editor for Scmdraft 2. Although a C# GUI and a C++ dll have been doing the job good so far.
[right][snapback]541266[/snapback][/right]
Oh.. What do you mean resource editor? Like, icons & strings, or just extracting resources from compiled files?
As in making a GUI.
Strings, Icons, Text Boxes, etc.. I have no decent resource editor.