struct SAddinFuncs
{
    HMODULE hmod;

    // Supported functions
    bool (*fixup_tooltip)     (String* tooltip, String** newTooltip);
    bool (*fixup_cliptext)    (String* cliptext, String** newCliptext);
    void (*monitor_keystroke) (int vkey, unsigned int flags);
    // Other functions go here
};

SAddinFuncs* load_third_party_addin(char* pathname)
{
    HMODULE hmod = LoadLibrary(pathname);
    if (!hmod)
        return NULL;

    SAddinFuncs* addin = new SAddinFuncs;
    addin->hmod = hmod;
    addin->fixup_tooltip     = GetProcAddress(hmod, "fixup_toolip");
    addin->fixup_cliptext    = GetProcAddress(hmod, "fixup_cliptext");
    addin->monitor_keystroke = GetProcAddress(hmod, "monitor_keystroke");
    // Repeat for other functions
    return addin;
}

void monitor_keystrokes(int vkey, unsigned int flags)
{
    for (int lnI = 0; lnI < addins.size(); ++lnI)
    {
        SAddinFuncs* addin = addins.get(lnI);
        if (addin->monitor_keystroke)
            addin->monitor_keystroke(vkey, flags);
    }
}

String* fixup_cliptexts(String* cliptext)
{
    String* newCliptext;

    for (int lnI = 0; lnI < addins.size(); ++lnI)
    {
        SAddinFuncs* addin = addins.get(lnI);
        if (addin->fixup_cliptext)
        {
            newCliptext = NULL;
            if (addin->fixup_cliptext(cliptext, &newCliptext) && newCliptext)
            {
                delete cliptext;
                cliptext = newCliptext;
            }
        }
    }

    // Return the updated cliptext content
    return cliptext;
}

quote:

---

Originally posted by feline

Having seen some of the strange and bizarre things that people do with C++, good luck, you are likely to need it

---

quote:

---

Originally posted by feline

I have put in a feature request for this, but I am still not convinced that this is going to be an efficient use of resources at the moment. Still, worth seeing what the developers make of it.

---

quote:

---

Originally posted by feline

The main focus for feature requests and bug reports for VA are specific features that are either logical extensions of existing features, or handling edge cases. The IDE is already extendable, but re-working VA to provide a stable API would require an ongoing commitment to keeping everything working correctly. A significant overhead.

---

quote:

---

Originally posted by feline
Having said that, what problems are you actually trying to solve here? You can already extend the IDE its self, and there are plenty of tools for programming / controlling Windows as well.

---

quote:

---

Originally posted by feline
Remember that a lot of what VA does is based on parsing your code as you are writing it, which is hard. We cannot assume your code compiles, or is valid, but still try to provide useful and helpful feedback and interaction.

---

quote:

---

Originally posted by feline
As a slight answer to making Visual Assist extendable, Microsoft removed the built in macro tools in Visual Studio several versions ago, since their data showed that only a tiny percentage of developers used them, so they were not really a priority feature. Personally I did use the macros, but I know that in general people were not interested in using them to fix problems or work around issues, sadly supporting Microsoft's experience.

---

quote:

---

Originally posted by feline

Have you considered one of the extensions to add IDE macros back to the IDE?

---

quote:

---

Originally posted by feline

Are you aware of both the VA clipboard history and Windows 10 built in clipboard history features?

---

quote:

---

I know the feeling of needing to pull together several pieces of text / information from different places, but generally when I am doing this I need to do some limited editing as well as I stitch the parts together, so simply having them placed into a single block without control would not help much. Of course it's possible your usage is different.

---