<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MicroStation Tips&#187; Level Tips</title>
	<atom:link href="http://microstationtips.com/category/microstationtips/level-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://microstationtips.com</link>
	<description>Time-saving MicroStation Tips and Tricks</description>
	<lastBuildDate>Wed, 26 May 2010 16:17:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Using Level Symbology to plot thinner lines.</title>
		<link>http://microstationtips.com/using-level-symbology-to-plot-thinner-lines/</link>
		<comments>http://microstationtips.com/using-level-symbology-to-plot-thinner-lines/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 18:26:01 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Level Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[Plotting Tips]]></category>
		<category><![CDATA[level symbology]]></category>
		<category><![CDATA[plot]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=191</guid>
		<description><![CDATA[A question we recently received was: &#8220;Is there a way to plot the lines in some reference files thinner, without changing the drawing and keep the other reference files the same?&#8221; The easy way to handle this is to use Level Symbology. (The following directions are for MicroStation/J.) 1) From the &#8220;Reference&#8221; dialog box, select [...]]]></description>
			<content:encoded><![CDATA[<p class="body">A question we recently received was: &#8220;Is there                  a way to plot the lines in some reference files thinner, without                  changing the drawing and keep the other reference files the same?&#8221;<br />
The easy way to handle this is to use Level Symbology. (The following                  directions are for MicroStation/J.)</p>
<p class="body">1) From the &#8220;Reference&#8221; dialog box, select                  the reference file you want to plot.</p>
<p class="body"><img src="http://www.axiomint.com/images/tips/lvlsymb/ref-level-symbology-dialog.jpg" alt="" width="370" height="266" /></p>
<p class="body">2) Go to Settings | Level Symbology. This will open                  the &#8220;Ref Level Symbology&#8221; dialog box for that reference                  file.</p>
<p><img src="http://www.axiomint.com/images/tips/lvlsymb/ref-level-symbology-weight.jpg" alt="" width="370" height="266" /></p>
<p class="body">3) Select the levels you want to make &#8220;thinner&#8221;,                  then click on the Weight check box, under the &#8220;Settings&#8221;                  area.</p>
<p class="body">4) Modify the Weight and click &lt;OK&gt;.</p>
<p class="body">5) In the View Attributes for your active view,                  turn on &#8220;Level Symbology&#8221;.</p>
<p><img src="http://www.axiomint.com/images/tips/lvlsymb/ref-level-symbology-view-at.jpg" alt="" width="276" height="293" /></p>
<p><span class="body">Enable the &#8220;Level Symbology&#8221; view                  attribute to see the level symbology you just set.<br />
That&#8217;s it! This does not affect the actual element symbology,                  only how the element displays in that view. You can turn off the                  level symbology when you are done plotting.</span></p>
<p class="body">If you use this procedure often, it would be good                  practice to set up this up in an unused view. This gives you a                  &#8220;plotting view&#8221; that you can modify however you want,                  without modifying the actual drawing.</p>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/using-level-symbology-to-plot-thinner-lines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Change Level Names in MicroStation V8</title>
		<link>http://microstationtips.com/change-level-names-in-microstation-v8/</link>
		<comments>http://microstationtips.com/change-level-names-in-microstation-v8/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 18:15:43 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Level Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[levels]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=179</guid>
		<description><![CDATA[How do you change the &#8220;level&#8221; names to our standards? (i.e. &#8220;Anchors&#8221; level change to Level &#8220;24&#8243;). To rename one level at a time, just open the Level Manager (under Settings &#62; Level menu). Then, right-click on the level you want to rename, and select &#8220;Rename&#8221; from the options. Viola! Now, if you want to [...]]]></description>
			<content:encoded><![CDATA[<p class="body">
<p class="body">How do                              you change the &#8220;level&#8221; names to our standards?                              (i.e. &#8220;Anchors&#8221; level change to Level &#8220;24&#8243;).</p>
<p><span class="body">To rename one level at                              a time, just open the Level Manager (under Settings                              &gt; Level menu). Then, right-click on the level you                              want to rename, and select &#8220;Rename&#8221; from                              the options. Viola! Now, if you want to rename multiple                              levels across multiple design files, I recommend you                              look into a plug-in, like Axiom&#8217;s <em>Global File Changer </em> (<a class="bodytextlinks" href="http://www.axiomint.com/products/globalfilechanger.htm">www.axiomint.com/products</a>),                              to help you automate that.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/change-level-names-in-microstation-v8/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Introduction to models for the new V8 user</title>
		<link>http://microstationtips.com/introduction-to-models-for-the-new-v8-user/</link>
		<comments>http://microstationtips.com/introduction-to-models-for-the-new-v8-user/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 18:14:11 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Level Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[design model]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=177</guid>
		<description><![CDATA[With V8, Bentley introduced MicroStation users to the concept of models. Whereas a V7 design file used to be one single design space, a V8 design file is a container of models, each of which behaves much like a separate design file. You can create an unlimited number of models in a DGN file. There [...]]]></description>
			<content:encoded><![CDATA[<p><span class="body">With V8, Bentley introduced MicroStation users                  to the concept of models. Whereas a V7 design file used to be                  one single design space, a V8 design file is a container of models,                  each of which behaves much like a separate design file. You can                  create an unlimited number of models in a DGN file.</p>
<p>There are two types of models: design or sheet. Design models                  can be either 2D or 3D. A design model can also be used as a reference                  or placed as a cell. Sheet models, which are flat and used for                  drawing composition, are ordinarily 2D (see description of &#8220;drawing                  composition&#8221; below). Sheet models let you attach references                  to create a set of working drawings for the design. By default,                  the view windows of design models have black backgrounds and those                  of sheet models have white backgrounds.</p>
<p>MicroStation users familiar with AutoCAD will notice that the                  model concept is not new to CAD. A design model is similar to                  the &#8220;DWG model space&#8221; and a sheet model is similar to                  the &#8220;DWG paper space&#8221;.</span><br />
<span class="bodyBold"><br />
<strong>Drawing Composition</strong></span></p>
<p><span class="body">As the name suggests, design models are meant                  to serve as design environments, where designers can draw components                  or sections of an overall design and then use sheet models to                  bring together parts and compose finished, annotated drawings.                  This is a concept known as &#8220;Drawing Composition&#8221;. In                  other words, you can reference in models from the same file into                  another model in the same file (or another design file if you                  want). For example, you can design the drawers for a desk in one                  design model, the table top in another and bring them all together                  as a complete desk in the sheet model.</span></p>
<p><strong class="bodyBold">Models dialog box</strong><br />
<span class="body">MicroStation V8 offers a simple dialog box                  to manage models. The Models dialog box can be accessed through                  File | Models or by clicking on the Models icon.</span></p>
<p class="body">The Models dialog box is explained in the graphic                  below:</p>
<table border="0" cellspacing="5" cellpadding="0" width="100" align="center">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/mst/jan06/tip_models_dialog.jpg" alt="" width="450" height="284" /></td>
</tr>
<tr>
<td class="bodyCaptions">The Models dialog box (File | Models)                      is used to create and manage models in an open DGN file.</td>
</tr>
</tbody>
</table>
<p><strong class="bodyBold">Useful model key-ins</strong></p>
<p><span class="body">If you are like most of us at Axiom (read:                  a geek), then the following key-ins will help you move faster.                  You can either memorize them or assign them to a function key.                  Enjoy!</span></p>
<ul>
<li class="body"> Create a new design model: MODEL CREATE DESIGN</li>
<li class="body">Create a new sheet model: MODEL CREATE SHEET</li>
<li class="body">Import all models from another design file: MODEL                    IMPORT ALL</li>
</ul>
<p><span class="body">These key-in commands will prompt for any                  additional information they need.</span></p>
<p><strong class="bodyBold">Drag and drop models</strong></p>
<p><span class="body">You can also drag and drop DGN or DWG files                  from Windows Explorer into the Models dialog box to import the                  models from the selected files. Similarly you can use drag and                  drop to drag models from the Models dialog in another open session                  of MicroStation to the Models list box and drop them in to import                  the models. Neat!</span></p>
<p><strong><span class="bodyBold">Models! Models! Models!</span><br />
</strong><span class="body"><br />
Models have changed the way MicroStation designers work, by providing                  multiple design environments within one file. This translates                  to fewer numbers of files per project and easier management of                  design information. Yet another clever way Bentley has given us                  to more efficiently communicate design intent.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/introduction-to-models-for-the-new-v8-user/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Introduction to Level Libraries</title>
		<link>http://microstationtips.com/introduction-to-level-libraries/</link>
		<comments>http://microstationtips.com/introduction-to-level-libraries/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 18:12:10 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Level Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[level libraries]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=175</guid>
		<description><![CDATA[Level libraries are a MicroStation V8 enhancement that allow you to ensure consistency by offering an easy way to standardize level settings in your design files. Level libraries are very similar to the LVL files found in previous versions of MicroStation [Editor’s note: In V7, the levels are not named, they are numbered and the [...]]]></description>
			<content:encoded><![CDATA[<p class="body">Level libraries are a MicroStation V8 enhancement                  that allow you to ensure consistency by offering an easy way to                  standardize level settings in your design files. Level libraries                  are very similar to the LVL files found in previous versions of                  MicroStation [Editor’s note: In V7, the levels are not named,                  they are numbered and the names are just aliases stored in a text                  file with the extension .lvl.].</p>
<table border="0" cellspacing="5" cellpadding="0" width="100" align="center">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/mst/aug06/levelmgr1.jpg" alt="" width="250" height="175" /></td>
</tr>
<tr>
<td class="bodyCaptions">Find the Level Manager display under                      the Settings dropdown.</td>
</tr>
</tbody>
</table>
<p><strong class="bodyBold">Making a Level Library</strong><br />
<span class="body">The Level Manager (Settings | Level | Manager)                  dialog box is where you create, modify and manage the levels you                  are working with.</span></p>
<p class="body">First, you need to build your library:</p>
<table border="0" cellspacing="5" cellpadding="0" width="100" align="center">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/mst/aug06/levelmgr2.jpg" alt="" width="250" height="180" /></td>
</tr>
<tr>
<td class="bodyCaptions">Click the New Level icon to create                      a new level.</td>
</tr>
</tbody>
</table>
<p><span class="body">When your library is complete, go to Levels                  | Export to export your level library as a DGNLIB file or as a                  CSV file.</span><br />
<strong class="bodyBold">Attaching a Level Library</strong><br />
<span class="body">From the Level Manager dialog box, select “Attach”                  from the Levels drop down menu. This opens the Attach Level Library                  dialog box where you can browse and attach a level library.</span></p>
<table border="0" cellspacing="5" cellpadding="0" width="100" align="center">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/mst/aug06/levelmgr3.jpg" alt="" width="250" height="166" /></td>
</tr>
<tr>
<td class="bodyCaptions">Select “Attach” from the                      drop down menu.</td>
</tr>
</tbody>
</table>
<table border="0" cellspacing="5" cellpadding="0" width="100" align="center">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/mst/aug06/levelmgr4.jpg" alt="" width="250" height="127" /></td>
</tr>
<tr>
<td class="bodyCaptions">Browse to find the appropriate library.                      Hit &lt;OK&gt; to attach the library.</td>
</tr>
</tbody>
</table>
<table border="0" cellspacing="5" cellpadding="0" width="100" align="center">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/mst/aug06/levelmgr5.jpg" alt="" width="250" height="95" /></td>
</tr>
<tr>
<td class="bodyCaptions" height="26">The Level Manager dialog                      will now display the levels in the attached level library.</td>
</tr>
</tbody>
</table>
<p><strong class="bodyBold">Filtering Out the Library Name</strong><br />
<span class="body">When a level library is attached to a design                  file, the name of the level library (filename) shows up next to                  the level name. Sometimes, depending on the length and complexity                  of your level and level library names, the Level Manager dialog                  box can get cluttered and can be hard to read with the level name                  and level library filename together. Using a handy configuration                  variable, you can hide the level library filename from view so                  that it does not show next to the level name. </span></p>
<p><span class="body">Here’s how:<br />
1. Open the “Configuration: User” dialog (Workspace                  | Configuration).<br />
2. Select “Level” as the category and click &lt;New&gt;.                  Enter the following variable into the New Configuration Variable                  dialog:<br />
MS_HIDE_LIBRARY_SOURCE_NAMES = 1</span></p>
<table border="0" cellspacing="5" cellpadding="0" width="100" align="center">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/mst/aug06/levelmgr6.jpg" alt="" width="250" height="177" /></td>
</tr>
<tr>
<td class="bodyCaptions">Enter in the new configuration variable.</td>
</tr>
</tbody>
</table>
<p class="body">3. Accept and save the configuration variable.<br />
4. Close MicroStation and relaunch it.</p>
<p><span class="body"><br />
Now, look at the Level Manager dialog and you will notice that                  the level library filename is gone, leaving you with a simplified                  display in the Level Manager dialog.</span></p>
<table border="0" cellspacing="5" cellpadding="0" width="100" align="center">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/mst/aug06/levelmgr7.jpg" alt="" width="250" height="95" /></td>
</tr>
<tr>
<td class="bodyCaptions">End result: clarity!</td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/introduction-to-level-libraries/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
