Wie zu Lesen, Shape-Eigenschaften in Visio

Ich gehe davon aus, dass durch die Eigenschaften, die Sie beziehen sich auf Shape-Daten, die verwendet werden, um " Benutzerdefinierte Eigenschaften in der Benutzeroberfläche und wird noch wissen, dass Namen in der API.

Wenn Sie nicht vertraut sind mit dem ShapeSheet sollten Sie haben Blick auf eine Form mit benutzerdefinierten Eigenschaften in der ShapeSheet-zuerst, um zu sehen, wie die Eigenschaften definiert sind. Siehe"Was geschah mit dem ShapeSheet?", um zu lernen, wie zu öffnen das Shapesheet von Visio 2010.

Folgende Beispiel-Programm sollte Ihnen den Einstieg. In diesem Beispiel wird davon ausgegangen, dass Sie die Visio Primäre Interop-Assembly installiert auf dem PC und dass Sie einen Schiedsrichter, der für Microsoft.Office.Interop.Visio in Ihrem Projekt.

namespace VisioEventsExample
{
    using System;
    using Microsoft.Office.Interop.Visio;

    class Program
    {
        public static void Main(string[] args)
        {
            //Open up one of Visio's sample drawings.
            Application app = new Application();
            Document doc = app.Documents.Open(
                @"C:\Program Files\Microsoft Office\Office14\visio content\1033\ASTMGT_U.VST");

            //Get the first page in the sample drawing.
            Page page = doc.Pages[1];

            //Start with the collection of shapes on the page and 
            //print the properties we find,
            printProperties(page.Shapes);
        }

        /* This function will travel recursively through a collection of 
         * shapes and print the custom properties in each shape. 
         * 
         * The reason I don't simply look at the shapes in Page.Shapes is 
         * that when you use the Group command the shapes you group become 
         * child shapes of the group shape and are no longer one of the 
         * items in Page.Shapes.
         * 
         * This function will not recursive into shapes which have a Master. 
         * This means that shapes which were created by dropping from stencils 
         * will have their properties printed but properties of child shapes 
         * inside them will be ignored. I do this because such properties are 
         * not typically shown to the user and are often used to implement 
         * features of the shapes such as data graphics.
         * 
         * An alternative halting condition for the recursion which may be 
         * sensible for many drawing types would be to stop when you 
         * find a shape with custom properties.
         */
        public static void printProperties(Shapes shapes)
        {
            //Look at each shape in the collection.
            foreach (Shape shape in shapes)
            {               
                //Use this index to look at each row in the properties 
                //section.
                short iRow = (short) VisRowIndices.visRowFirst;

                //While there are stil rows to look at.
                while (shape.get_CellsSRCExists(
                    (short) VisSectionIndices.visSectionProp, 
                    iRow, 
                    (short) VisCellIndices.visCustPropsValue,
                    (short) 0) != 0)
                {
                    //Get the label and value of the current property.
                    string label = shape.get_CellsSRC(
                            (short) VisSectionIndices.visSectionProp, 
                            iRow,
                            (short) VisCellIndices.visCustPropsLabel
                        ).get_ResultStr(VisUnitCodes.visNoCast);

                    string value = shape.get_CellsSRC(
                            (short) VisSectionIndices.visSectionProp, 
                            iRow,
                            (short) VisCellIndices.visCustPropsValue
                        ).get_ResultStr(VisUnitCodes.visNoCast);

                    //Print the results.
                    Console.WriteLine(string.Format(
                        "Shape={0} Label={1} Value={2}",
                        shape.Name, label, value));

                    //Move to the next row in the properties section.
                    iRow++;
                }

                //Now look at child shapes in the collection.
                if (shape.Master == null && shape.Shapes.Count > 0)
                    printProperties(shape.Shapes);
            }
        }
    }
}

InformationsquelleAutor Pat Leahy

Alle diejenigen, die benötigen Codes helfen, später auf diese Frage:

...
using Visio = Microsoft.Office.Interop.Visio;

namespace RibbonCustomization
{
   [ComVisible(true)]
   public class Ribbon1 : Office.IRibbonExtensibility
   {

      public void ReadShapes(Microsoft.Office.Core.IRibbonControl control)
      {
         ExportElement exportElement;
         ArrayList exportElements = new ArrayList();

         Visio.Document currentDocument = Globals.ThisAddIn.Application.ActiveDocument;
         Visio.Pages Pages = currentDocument.Pages;
         Visio.Shapes Shapes;

         foreach(Visio.Page Page in Pages)
         {
            Shapes = Page.Shapes;
            foreach (Visio.Shape Shape in Shapes)
            {
               exportElement = new ExportElement();
               exportElement.Name = Shape.Master.NameU;
               exportElement.ID = Shape.ID;               
               exportElement.Text = Shape.Text;
               ...
               //and any other properties you'd like

               exportElements.Add(exportElement);
            }
         }
....

InformationsquelleAutor Daniil Belonin