Shapes with a higher DisplayLevel value are displayed on top of shapes with a lower value. Visio uses this to place containers behind the shapes they contain, regardless of what order they are added to the page. This cell defines “bands” of Z-order and is used to determine the default global Z-order position for a shape when it is added to the page. In any case, the user can change the setting by toggling the Auto Size button on the Design tab. If the page is at a default size, Visio enables Auto Size so users can benefit from it if customized, Visio assumes that a specific page size was chosen for a reason and disables Auto Size. It makes a best guess by looking at the page size relative to common paper sizes and deciding whether the page size appears to have been customized, or left at a default size.
This value allows Visio to determine whether Auto Size is enabled for the user. Zero is “undefined,” which is the default state for a document created in Visio 2007 or prior, since this cell doesn’t exist in those versions. Values 1 and 2 correspond to Auto Size on and off, respectively. This cell corresponds to the Page Auto Size feature, which is found on the Design tab. This corresponds to the Space Shapes > Avoid Page Breaks setting under the Position button on the Home tab. This cell takes a TRUE or FALSE value and determines whether the Auto Align and Space features attempt to avoid placing shapes on page breaks. Recall that you can view the PageSheet for a page or the ShapeSheet for a shape using the Developer tab. New ShapeSheet cells in Visio 2010: Section
New PageSheet cells in Visio 2010: Section New CellsĪ number of new cells were added to both the PageSheet and the ShapeSheet to support new features in Visio 2010 and to expand the possibilities for shape development. In this post, we will continue with ShapeSheet development and dig deeper to examine the new ShapeSheet cells and functions available in Visio 2010. Our previous post introduced the improvements we made to the ShapeSheet window for shape developers.
0 kommentar(er)
