bVisual

bVisual Blog by David Parker

Published on by

Toggling Layers On and Off

UPDATE March 2017 : I have now expanded this functionality into an add-in for Visio (see Layer Manager add-in for Visio released ).

Visio layering system is more complex than any CAD system I’ve worked with, and often catches users out.  A Visio shape can belong to no layer, one layer or multiple layers simultaneously, and a layer can be visible or invisible; printable or non-printable.  In fact, you can have a shape on a layer that is invisible but printable – a good way to put a watermark across a document.

Firstly, Visio layers are per page in a document, and secondly, Visio layers are stored as an index number with an associated name.  Therefore, layer 1 on page 1 could be named Outline, but layer 1 on page 2 could be called something completely different!

View > Layer Properties will show you the layer settings on the active Visio page, but the # column, which gives you a count of shapes on each layer, can be misleading because the same shape can be on multiple layers, and even sub-shapes (those inside a grouped shape) are counted.

image
[Read more…] about Toggling Layers On and Off

Published on by

EventXFMod can cause Visio to stop working

I was recently re-working with some old code of mine that enhanced the Cross Functional Flowchart template, and found that it can cause Visio to stop working when the VBA project is enabled. Let me explain the problem, and the solution that I have adopted.
Firstly, I should say that this is VBA because it is for occasional use only, otherwise I would go to the trouble of making an add-in.
I modified the Flowchart shapes master by entering a formula in the EventXFMode cell:
=CALLTHIS(“GetFunction”,””)
This caused the GetFunction sub to be called whenever the shape was moved (in this case to detect the Functional band that it lay within).
This was working fine until the number of pages and shapes increased, and what I found was that, although it continued to work whilst the document was open, it caused Visio to stop working when the document was opened and the VBA project enabled. This always occurred whilst Visio was busy processing all of the shapes. It seems that my GetFunction sub was conflicting with whatever the Microsoft Cross Functional add-on and the Visio routing engine was up to.
I decided that the simplest solution would be find a way of filtering the firing of my GetFunction sub, and the easiest way to do this was to add a User-defined cell in the document, called MonitorShapes, and to only call my sub if the value in that cell is not zero, by using the modified formula in the EventXFMod cell:
=IF(TheDoc!User.MonitorShapes,CALLTHIS(“GetFunction”,””),0)
Of course, I then need sub to set this value to 0 or 1.
Public Sub StartMonitorShapes()

    If ThisDocument.DocumentSheet.CellExists("User.MonitorShapes", Visio.visExistsAnywhere) Then

        ThisDocument.DocumentSheet.Cells("User.MonitorShapes").Formula = "1"

    End If

End Sub

Public Sub StopMonitorShapes()

    If ThisDocument.DocumentSheet.CellExists("User.MonitorShapes", Visio.visExistsAnywhere) Then

        ThisDocument.DocumentSheet.Cells("User.MonitorShapes").Formula = "0"

    End If

End Sub
The result is that Visio no longer stops working when I open the document, as long as I remember to run StopMonitorShapes before I save and close it.