The Visio Event Monitor that's part of the SDK is a great tool for understanding how Visio works and the events that are firing away while you work. So in this post I thought I'd demonstrate a quick technique for making the output a little easier to read.
Following on from my previous post, I thought I'd move on and look at some interesting aspects of the Congress shapes from a Visio construction perspective.
In Visio, a page's drawing units are defined by the value found in the DrawingScale cell. Like all cells you can interrogate this in code via the Cell.Units property, but in the ShapeSheet, there's no direct method to find out the same information. So I thought I'd write down one way you could approach this.
As of version 5.25, LINQPad has a new object diff’ing method that’s great for comparing objects and tracking down problems in code and this, of course, also applies to Visio.
In this post, I’m going to look at one method to provide a lookup in a 2D array, which could be used, for example, to map cells in the ShapeSheet to a table collection.
Today I’m releasing a new training course on Channel 9. The course is aimed at developers who are new to Visio, but need a quick overview of how Visio works under the covers.
[Note, that even if you have no desire to write code, you might still find the first part useful if you’re interested in creating your own shapes and masters.]