[cfe-dev] Clang-format / clang-tidy VS plugin

Richard via cfe-dev cfe-dev at lists.llvm.org
Wed Aug 17 11:02:48 PDT 2016


[Please reply *only* to the list and do not include my email directly
in the To: or Cc: of your reply; otherwise I will not see your reply.
Thanks.]

In article <CAAErz9h+_1_VzvzwewfR+_kOb=iLARs2QHxSN6GuVmZ0pQX7UQ at mail.gmail.com>,
    Zachary Turner via cfe-dev <cfe-dev at lists.llvm.org> writes:

> That is one idea that I considered, but from what I understand of how to
> implement options UI in Visual Studio (I have never actually done this, but
> looked at it for an hour or so once upon a time) the options and values
> need to be statically defined in order to create the UI property sheet.  ie
> you can't build one of these sheets dynamically, because the UI is
> generated when Visual Studio loads your extension by reading some XML.
> It's possible my understanding is wrong though.

If you ship the executable with your plugin, then the options are
known at the time the plugin is packaged and you can generate the XML
at packaging time.
-- 
"The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline>
     The Computer Graphics Museum <http://ComputerGraphicsMuseum.org>
         The Terminals Wiki <http://terminals.classiccmp.org>
  Legalize Adulthood! (my blog) <http://LegalizeAdulthood.wordpress.com>



More information about the cfe-dev mailing list