<?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; Element Tips</title>
	<atom:link href="http://microstationtips.com/category/microstationtips/element-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://microstationtips.com</link>
	<description>Time-saving MicroStation Tips and Tricks</description>
	<lastBuildDate>Mon, 14 May 2012 14:10:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Recover Missing Elements from Your MicroStation Files</title>
		<link>http://microstationtips.com/recover-missing-elements-from-your-microstation-files/</link>
		<comments>http://microstationtips.com/recover-missing-elements-from-your-microstation-files/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 17:15:03 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Element Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[Eiren Smith]]></category>
		<category><![CDATA[FileFixer]]></category>
		<category><![CDATA[missing elements]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=111</guid>
		<description><![CDATA[By Eiren Smith, Axiom’s Vice President for Technology &#8211; www.AxiomInt.com Has this ever happened to you? You’ve been working on a design file for weeks. You’ve filled it with elements to your heart’s content. One fine morning, you load the file in MicroStation, and your eyes open wide in dismay. Hundreds of elements are missing [...]]]></description>
			<content:encoded><![CDATA[<p class="body"><span class="bodyHeader2">By Eiren Smith,                              Axiom’s Vice President for Technology &#8211; </span><a href="http://www.axiomint.com/"><span class="bodyHeader2">www.AxiomInt.com</span></a></p>
<p class="body">Has this ever happened to you?                              You’ve been working on a design file for weeks.                              You’ve filled it with elements to your heart’s                              content. One fine morning, you load the file in MicroStation,                              and your eyes open wide in dismay. Hundreds of elements                              are missing from your design! What happened? Your                              design file fell pray to file corruption.</p>
<p class="body">What you may not know is there’s                              a good chance that your elements are still in the                              design file. How could this be? To explain, let us                              take a small excursion. Think of a design file as                              a gigantic skyscraper; think of each floor of the                              skyscraper as a MicroStation element; and think of                              MicroStation itself as an elevator. To arrive at the                              bottom floor from the top floor of the skyscraper,                              an elevator has to first pass through each floor in                              between. MicroStation opens a design file in a similar                              fashion. To open a design file, MicroStation first                              scans the file from the top floor (in other words,                              from the first element in the file) all the way to                              the bottom floor (to the last element in the file).                              Just like an elevator would expect to find the bottom                              floor at the bottom of a skyscraper, MicroStation                              expects to find an “end-of-design marker”                              at the bottom of a design file. Simply put, the end-of-design                              marker tells MicroStation that the end of the file                              has been reached and that there aren’t any more                              elements to display. For various reasons (network                              glitches, hardware malfunctions, application errors                              and more), an erroneous “end-of-design marker”                              can wind up in the design file somewhere other than                              at the actual end of the file. The result: all elements                              after the erroneously placed end-of-design marker                              are no longer recognized or displayed by MicroStation!</p>
<p class="body">The easiest and safest way                              to bring back your missing elements is by using Axiom’s                             <em> FileFixer</em> &#8211; the utility that lets you fix any MicroStation                              file automatically!</p>
<p class="body">In this technical bulletin,                              I’ll show you how to set up <em>FileFixer</em> to recover                              elements that lie past an erroneous end-of-design                              file marker.</p>
<ol>
<li><span class="body"> Select <em>FileFixer </em>from                                the Axiom menu [located on the MicroStation menu                                bar].</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_01.gif" alt="" width="197" height="167" /></li>
<li> <span class="body"><em>FileFixer’s</em> main                                dialog box shows up. Make sure the repair “Mode”                                pull-down menu is set to “Automatic Design                                File Repair”.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_02.gif" alt="" width="251" height="22" /></li>
<li><span class="body"> Next, click on the &lt;Edit                                List&gt; button to select the MicroStation file                                that is missing elements. For the purposes of this                                article, we created and selected the file “eod-marker.dgn”.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_03.gif" alt="" width="431" height="22" /></li>
<li> <span class="body">Then, on the <em>FileFixer </em> menu bar, choose the “Options” menu and                                then choose “Repair”.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_04.gif" alt="" width="165" height="134" /></li>
<li> <span class="body">Once in the “Repair                                Options” dialog box, select the “Element”                                category.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_05.gif" alt="" width="219" height="186" /></li>
<li><span class="body"> Having selected the “Element”                                category, check the option “Recover elements                                past the end-of-design marker”. Click &lt;OK&gt;                                afterwards.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_06.gif" alt="" width="454" height="185" /></li>
<li><span class="body"> Back in <em>FileFixer’s </em> main dialog box, click &lt;Start&gt; to recover                                all the missing elements automatically.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_07.gif" alt="" width="101" height="24" /></li>
<li> <span class="body">After processing the design                                file, <em>FileFixer</em> prompts you to click the &lt;OK&gt;                                button. Notice that the dialog box states “Repaired                                files have .fix extension”. This is because                                <em>FileFixer</em> repairs a copy of your design file by                                default. This is a precaution to protect you in                                the unlikely event that the repair produces results                                that are less than perfect. You’ll always have                                the original file to go back to!</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/elements_recover_missing_08.gif" alt="" width="333" height="166" /></li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/recover-missing-elements-from-your-microstation-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Recover Deleted Elements You Thought to be Gone Forever</title>
		<link>http://microstationtips.com/recover-deleted-elements-you-thought-to-be-gone-forever/</link>
		<comments>http://microstationtips.com/recover-deleted-elements-you-thought-to-be-gone-forever/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 17:11:31 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Element Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[elements]]></category>
		<category><![CDATA[Fence Undelete]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=108</guid>
		<description><![CDATA[You have just executed a fence deletion and watched in horror as thousands of the wrong elements disappeared. You didn’t notice your active fence setting was set to “Void” instead of “Inside”. You try “Undo”, but there is still a large number of missing elements because the amount of information deleted was too large for [...]]]></description>
			<content:encoded><![CDATA[<p class="body">You have just executed a fence deletion and watched                              in horror as thousands of the wrong elements disappeared.                              You didn’t notice your active fence setting was                              set to “Void” instead of “Inside”.                              You try “Undo”, but there is still a large                              number of missing elements because the amount of information                              deleted was too large for the Undo buffer to handle.</p>
<p class="body">Use Axiom’s <em>Fence Undelete </em> to recover every one of the deleted elements.</p>
<ol>
<li class="bodytext"><span class="body"> Start <em>Fence Undelete</em> from the                                Axiom menu. The <em>Fence Undelete</em> tool palette comes                                up.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/fence_recover_elements_1.gif" alt="" width="176" height="56" /></li>
<li class="bodytext"><span class="body">Click on the tombstone icon to                                view all the deleted elements that did not make                                it back after using Undo.</span><br />
<table border="0" cellspacing="0" cellpadding="0" width="160">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/microstation_tips/images/fence_recover_elements_2.gif" alt="" width="176" height="56" /></td>
</tr>
<tr>
<td class="captions">The icon in red allows                                      users to view a file’s deleted elements                                      in a temporary design file.</td>
</tr>
</tbody>
</table>
</li>
<li class="bodytext"><span class="body">A temporary file is created that                                holds all the deleted elements. To recover the elements,                                click on <em>Fence Undelete’s</em> Fence icon (below                                in red). Place the fence around the deleted elements.                                You can also select elements individually.</span></li>
<li class="bodytext"><span class="body">Then, click on the Restore Fence                                Contents icon (below in red) and accept by clicking                                your mouse inside the view. You’ll notice that                                the elements disappear from the temporary file.                                They are being restored to the design file from                                which they were deleted.</span><br />
<table border="0" cellspacing="0" cellpadding="0" width="160">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/microstation_tips/images/fence_recover_elements_4.gif" alt="" width="176" height="56" /></td>
</tr>
<tr>
<td class="captions">The icon in red allows                                      users to restore deleted elements to the design                                      file from which they were deleted.</td>
</tr>
</tbody>
</table>
</li>
<li class="bodytext"><span class="body">To return to the original design                                file, click on the Return to Original File icon                                (again, below in red). You’ll now see that                                your elements are back in place where they belo</span>ng.<br />
<table border="0" cellspacing="0" cellpadding="0" width="160">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/microstation_tips/images/fence_recover_elements_5.gif" alt="" width="176" height="56" /></td>
</tr>
<tr>
<td class="captions">The icon in red allows                                      users to return to the design file that now                                      has the recovered elements in it.</td>
</tr>
</tbody>
</table>
</li>
</ol>
<p class="body">Unlike MicroStation’s                              Undo command, <em>Fence Undelete</em> can bring back deleted                              elements even after you have closed MicroStation!                              This only requires that the file not be com-pressed                              after the elements have been deleted.</p>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/recover-deleted-elements-you-thought-to-be-gone-forever/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Easily Delete Linear Elements Partially Overlapping Other Linear Elements</title>
		<link>http://microstationtips.com/easily-delete-linear-elements-partially-overlapping-other-linear-elements/</link>
		<comments>http://microstationtips.com/easily-delete-linear-elements-partially-overlapping-other-linear-elements/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 17:08:40 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Element Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[dulpicate element]]></category>
		<category><![CDATA[Eiren Smith]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=105</guid>
		<description><![CDATA[By Eiren Smith, Axiom&#8217;s Vice President for Technology &#8211; www.axiomint.com Accidental, duplicate elements are a fact of life for nearly all MicroStation sites. They cause plotting problems, selection trouble (elements that take forever to select with the Area Selection tool, because MicroStation may be selecting dozens or even hundreds of duplicates hidden under those you [...]]]></description>
			<content:encoded><![CDATA[<p class="body"><span class="bodyHeader2">By Eiren Smith, Axiom&#8217;s Vice President for Technology &#8211; </span><a href="http://www.axiomint.com/"><span class="bodyHeader2">www.axiomint.com</span></a></p>
<p class="body">Accidental, duplicate elements                              are a fact of life for nearly all MicroStation sites.                              They cause plotting problems, selection trouble (elements                              that take forever to select with the Area Selection                              tool, because MicroStation may be selecting dozens                              or even hundreds of duplicates hidden under those                              you intended to select), deletion difficulties (“I                              just deleted that element &#8211; and it came right back!”),                              unexpected results with third-party automation software                              that has no idea that the area you asked it to process                              includes numerous duplicate elements that you didn’t                              know about and did not want processed, unnecessarily                              large files padded with duplicate elements and a host                              of other site-specific problems.</p>
<p class="body">Duplicate elements come from                              many sources and come in varied forms. That is, there                              are many ways elements can be considered “duplicates”.                              Obviously, there are the simple cases of “perfect                              duplicates.” From a programming point of view,                              those are the easiest to locate and handle. However,                              there are many other ways elements can be considered                              duplicates from a production standpoint.</p>
<p class="body">In this technical bulletin,                              I address one of the more annoying forms of duplicate                              or near-duplicate elements: linear elements fully                              overlapped by other, longer linear elements. The overlapped                              elements could be significantly smaller than their                              overlapping counterparts, making them hard, sometimes                              practically impossible, to locate without the assistance                              of advanced software. The problem is solved using                              the latest addition to Axiom’s <em>Duplicate Element                              Remover.</em> The following steps demonstrate exactly                              how to get rid of this type of duplicate element.</p>
<ol>
<li class="body"> Select <em>Duplicate Element                                Remover</em> from the Axiom pull-down menu [located                                on the MicroStation menu bar].
<p><img src="http://www.axiomint.com/microstation_tips/images/element_delete_overlap_01.gif" alt="" width="197" height="133" /></li>
<li> <span class="body"><em>Duplicate Element Remover’s </em> main dialog appears. Your active design file                                will be selected by default. To process a different                                file (or multiple files), click the &lt;Select…&gt;                                button. For the purposes of this article, we will                                work with a test design file, overlap.dgn.
<p><img src="http://www.axiomint.com/microstation_tips/images/element_delete_overlap_02.gif" alt="" width="319" height="26" /></p>
<p></span></li>
<li class="body"> To begin, we will load <em>Duplicate                                Element Remover’s </em>default settings. From                                the main dialog box, choose “Settings | Reset                                to factory defaults…” and answer &lt;Yes&gt;                                to the confirmation box that appears.</li>
<li class="body"> Once the factory settings are                                restored, go to “Settings Change Settings…”
<p><img src="http://www.axiomint.com/microstation_tips/images/element_delete_overlap_04.gif" alt="" width="254" height="123" /></li>
<li class="body"> In the Category list, choose                                “Tolerances”.</li>
<li class="body"> Turn on the checkbox next to                                “Remove linear elements overlapped by longer                                elements?” A few other options will automatically                                be activated. This is okay.
<p><img src="http://www.axiomint.com/microstation_tips/images/element_delete_overlap_06.gif" alt="" width="292" height="21" /></li>
<li class="body"> Now, keep in mind that it is                                possible for lines which look like perfect duplicates                                to be less-than-perfect duplicates if they each                                contain different non-graphic information &#8211; information                                you can’t necessarily see. Attribute linkage                                information is a good example of this. For the purposes                                of this bulletin, we are not concerned with attribute                                linkages. In order for <em>Duplicate Element Remover </em> to treat near-duplicate elements with different                                attribute linkages as perfect duplicates, simply                                set the settings under the “Attribute linkages”                                Category as in the image below or make adjustments                                according to your own preference.
<p><img src="http://www.axiomint.com/microstation_tips/images/element_delete_overlap_07.gif" alt="" width="398" height="107" /></li>
<li class="body"> Then, on the same dialog box,                                choose &lt;OK&gt; to go back to the main dialog                                box.</li>
<li><span class="body"> Back in the main dialog box,                                check the box next to “Generate report only”.                                In “Generate report only” mode, <em>Duplicate                                Element Remover</em> will not delete any elements                                &#8211; it will simply create reports of what duplicate                                elements it found.</span>
<p><img src="http://www.axiomint.com/microstation_tips/images/element_delete_overlap_09.gif" alt="" width="128" height="21" /></li>
<li class="body"> Next, uncheck the box next to                                “Interactive mode”.<br />
Note: In this article, we run <em>Duplicate Element                                Remover</em> in non-interactive mode. In non-interactive                                mode, <em>Duplicate Element Remover</em> will process                                all your elements automatically without requiring                                you to make a decision for each one. Using <em>Duplicate                                Element Remover</em> in non-interactive mode is a                                great way to quickly see how many duplicate elements                                are in your files.</p>
<p><img src="http://www.axiomint.com/microstation_tips/images/element_delete_overlap_10.gif" alt="" width="108" height="21" /></p>
<p>On the other hand, interactive mode gives you the                                finest level of control. In this mode, <em>Duplicate                                Element Remover</em> will let you “visit”                                each duplicate element it finds. While visiting                                each duplicate element, you can choose to delete                                it or not. This is a great way to get a hands-on                                feel for what types of duplicate elements exist                                in your files. In everyday operation, you can choose                                whether you want to run in interactive or non-interactive                                mode.</li>
<li class="body"> Press                                &lt;Start&gt; to begin processing the design file.</li>
<li class="body"> After                                processing the design file, <em>Duplicate Element                                Remover</em> creates two report files:<br />
<strong>•</strong> A text report file (*.trf) which is                                a simple text file listing all the duplicate elements                                found; and<br />
<strong>•</strong> A design report file (*.drf), my personal                                favorite. Design report files graphically show you                                exactly what duplicate elements were found, presented                                in their relative location to the other elements                                in your file. You can think of design report files                                as “duplicate element X-ray glasses.”                                With them, you can essentially look right into a                                file and see only its duplicate elements.</li>
<li><span class="body">To see what duplicate elements                                <em>Duplicate Element Remover</em> found, press the                                &lt;View Design Report File&gt; button. The green                                elements are the duplicates; the white (color 0)                                elements are all the non-duplicate elements in the                                file, included (and turned white) to distinguish                                them from the duplicate elements.<br />
</span><br />
<img src="http://www.axiomint.com/microstation_tips/images/element_delete_overlap_13.gif" alt="" width="508" height="441" /></li>
<li class="body">If you agree that the green elements                                shown in the design report file are valid duplicates,                                process the file once again with the “Generate                                report only“ box unchecked, and, at your discretion,                                process the file in either interactive or non-interactive                                mode. After this step, you will find that your duplicate                                elements are gone. That’s all it takes!</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/easily-delete-linear-elements-partially-overlapping-other-linear-elements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MicroStation Tip Corner</title>
		<link>http://microstationtips.com/microstation-tip-corner/</link>
		<comments>http://microstationtips.com/microstation-tip-corner/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 17:06:07 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Element Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[elements]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=103</guid>
		<description><![CDATA[Easily re-select V8 elements Bored of having to re-select the same elements over and over again, especially when you have carefully selected a group of components and then click on the view window deactivating the selection? You can key in the function &#8220;choose previous&#8221; and your previous selection will be activated!]]></description>
			<content:encoded><![CDATA[<p><span class="bodyHeader2">Easily re-select V8 elements</span></p>
<p class="body">Bored of having to re-select the same elements over                  and over again, especially when you have carefully selected a                  group of components and then click on the view window deactivating                  the selection?</p>
<p class="body">You can key in the function &#8220;choose previous&#8221;                  and your previous selection will be activated!</p>
<p><img src="http://www.axiomint.com/images/tips/v8-key-in-choose.gif" alt="" width="230" height="242" /></p>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/microstation-tip-corner/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quick element selection — for V7 and V8!</title>
		<link>http://microstationtips.com/quick-element-selection-%e2%80%94-for-v7-and-v8/</link>
		<comments>http://microstationtips.com/quick-element-selection-%e2%80%94-for-v7-and-v8/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 17:04:12 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Element Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[element selection]]></category>
		<category><![CDATA[Rick DeWitt]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=101</guid>
		<description><![CDATA[by Rick DeWitt, Axiom&#8217;s Senior Technology Officer You probably know that if you drag the element selection tool, you can select any element that is completely inside the selection area (shown as a dashed line below). But, what you may not know is that by holding down the &#60;Ctrl&#62; and &#60;Shift&#62; keys while dragging the [...]]]></description>
			<content:encoded><![CDATA[<p><span class="bodyBold">by Rick DeWitt, Axiom&#8217;s Senior Technology                  Officer<br />
</span><span class="body">You probably know that if you drag the                  element selection tool, you can select any element that is completely                  inside the selection area (shown as a dashed line below).</span></p>
<p><span class="body">But, what you may not know is that by holding                  down the &lt;Ctrl&gt; and &lt;Shift&gt; keys while dragging the                  selection pointer, you can select the elements inside the selection                  area and elements that merely cross it. This is very helpful for                  quickly selecting elements whose endpoints intersect an element                  that you do not want included in the selection set (in this example,                  this element is the green box shown below).<br />
</span></p>
<table border="0" cellspacing="0" cellpadding="0" width="100">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/tips/quick-selection.gif" alt="" width="288" height="350" /></td>
</tr>
<tr>
<td class="bodyCaptions">By holding down &lt;Ctrl&gt; and &lt;Shift&gt;                      while dragging the element selection tool over the elements                      you want to select, you can quickly include elements that                      are completely inside the selection area and elements that                      merely overlap the selection area. It beats &lt;Ctrl&gt; clicking                      on each element!</td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/quick-element-selection-%e2%80%94-for-v7-and-v8/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Easily trim elements using the Trim Element tool.</title>
		<link>http://microstationtips.com/easily-trim-elements-using-the-trim-element-tool/</link>
		<comments>http://microstationtips.com/easily-trim-elements-using-the-trim-element-tool/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 17:00:36 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Element Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[American Electric Power]]></category>
		<category><![CDATA[Bob Knepp]]></category>
		<category><![CDATA[elements]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=98</guid>
		<description><![CDATA[By Bob Knepp of American Electric Power, Gahanna, Ohio Do you have new users that don&#8217;t really get the IntelliTrim tool yet? Here is an easy way to trim several elements very quickly using the MicroStation Trim Element command along with the PowerSelector tool. [Note: You can also use the regular Element Selection tool to [...]]]></description>
			<content:encoded><![CDATA[<p><span class="bodyBold">By Bob Knepp of American Electric                  Power, Gahanna, Ohio</span></p>
<p class="body">Do you have new users that don&#8217;t really get the                  IntelliTrim tool yet? Here is an easy way to trim several elements                  very quickly using the MicroStation Trim Element command along                  with the PowerSelector tool. [Note: You can also use the regular                  Element Selection tool to select multiple elements. Just hold                  down the &lt;Ctrl&gt; key while you select your elements.]</p>
<p><span class="body">1) First, pick the PowerSelector tool and                  select the elements you want to trim.</span></p>
<table class="bodyCaptions" border="0" cellspacing="0" cellpadding="0" width="100">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/tips/tip_trim_element_1.jpg" alt="" width="281" height="273" /></td>
</tr>
<tr>
<td>Select the elements using your favorite selection tool.                      For this tip, we will be using PowerSelector.</td>
</tr>
</tbody>
</table>
<table class="bodyCaptions" border="0" cellspacing="0" cellpadding="0" width="100">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/tips/tip_trim_element_2.jpg" alt="" width="231" height="189" /></td>
</tr>
<tr>
<td>Select all elements you want to be able to trim.</td>
</tr>
</tbody>
</table>
<p class="body">2) Next, click on the Trim Elements tool.</p>
<table class="bodyCaptions" border="0" cellspacing="0" cellpadding="0" width="100">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/tips/tip_trim_element_3.jpg" alt="" width="281" height="273" /></td>
</tr>
<tr>
<td>After you select the elements you want to trim, select the                      Trim Elements tool from the &#8220;Modify&#8221; toolbar.</td>
</tr>
</tbody>
</table>
<p class="body">You will notice that once you select the Trim Elements                  tool, the selected elements will no longer be &#8220;highlighted.&#8221;                  Don&#8217;t worry, that&#8217;s okay!</p>
<p class="body">3) Next, click on the portion of the element you                  want to trim.</p>
<table class="bodyCaptions" border="0" cellspacing="0" cellpadding="0" width="100">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/tips/tip_trim_element_4.jpg" alt="" width="208" height="201" /></td>
</tr>
<tr>
<td>The &#8220;X&#8221;s correspond to the areas I want to trim.                      Notice how the elements trim in the graphic on the right.                      Try this a few times to get the hang of it.</td>
</tr>
</tbody>
</table>
<p class="body">Once you are done, you do not have to unselect the                  elements. They are automatically dropped from the selection set.                  That&#8217;s it!</p>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/easily-trim-elements-using-the-trim-element-tool/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Align Tool in MicroStation J</title>
		<link>http://microstationtips.com/align-tool-in-microstation-j/</link>
		<comments>http://microstationtips.com/align-tool-in-microstation-j/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 16:59:01 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Element Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[align elements]]></category>
		<category><![CDATA[Rick DeWitt]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=96</guid>
		<description><![CDATA[by Rick DeWitt, Axiom&#8217;s Senior Technology Officer Let&#8217;s say you&#8217;ve got a bunch of text elements that need to be left aligned due to the fact that they were placed without regard for alignment and look rather sloppy. To fix this, use the &#8220;Align Edges&#8221; tool and have it done in no time flat. This [...]]]></description>
			<content:encoded><![CDATA[<p><span class="bodyBold">by Rick DeWitt, Axiom&#8217;s Senior Technology                  Officer<br />
</span><span class="body">Let&#8217;s say you&#8217;ve got a bunch of text                  elements that need to be left aligned due to the fact that they                  were placed without regard for alignment and look rather sloppy.                  To fix this, use the &#8220;Align Edges&#8221; tool and have it                  done in no time flat. This tool works on any element type and                  makes it quick and easy to align elements to others along the                  top, bottom, left, right or center points of the element.</span></p>
<p class="body">To align these off-kilter text elements, select                  the &#8220;Align Edges&#8221; tool located within the &#8220;Manipulate&#8221;                  toolbox.</p>
<p class="body"><img src="http://www.axiomint.com/images/tips/tip_align_manipulate.gif" alt="" width="230" height="56" /></p>
<p class="body">Then set the &#8220;Align&#8221; setting to &#8220;Left&#8221;                  in the &#8220;Tool Settings&#8221; dialog box.</p>
<p class="body"><img src="http://www.axiomint.com/images/tips/tip_align_edges.gif" alt="" width="198" height="69" /></p>
<p class="body">Next, select the text that you want the other elements                  to align to.</p>
<p><img src="http://www.axiomint.com/images/tips/tip_align_point_1.gif" alt="" width="166" height="155" /></p>
<p class="body">Accept it with another data point and then select                  each element whose left edge you want to align to the original                  element selected.</p>
<p><img src="http://www.axiomint.com/images/tips/tip_align_point_2.gif" alt="" width="166" height="155" /></p>
<p class="body">Now click the &lt;OK&gt; button on the dialog box,                  and your cell library will be converted. Easy as pie.</p>
<p class="body">If you make a mistake by selecting an element you                  do not want to align, just reset once and the element moves back                  to its original position. Then you can continue to select more                  elements. When the last element you want to move has been processed,                  accept it with a data point and then reset to start over with                  a new set of elements or select another tool. Very slick.</p>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/align-tool-in-microstation-j/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

