<?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; Key-in Tips</title>
	<atom:link href="http://microstationtips.com/category/microstationtips/key-in-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://microstationtips.com</link>
	<description>Time-saving MicroStation Tips and Tricks</description>
	<lastBuildDate>Tue, 27 Dec 2011 14:09:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>The Incremental Update Command</title>
		<link>http://microstationtips.com/the-incremental-update-command/</link>
		<comments>http://microstationtips.com/the-incremental-update-command/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 18:05:31 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Key-in Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[Bob Knepp]]></category>
		<category><![CDATA[key-in]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=165</guid>
		<description><![CDATA[By Bob Knepp of American Electric Power Ever have one of those drawings that contain lots of graphics and when you click “Update” it seems to take forever? The only reason you are updating the view is because you just deleted this big ’ole heavy weight line that left all those gaps in the view. [...]]]></description>
			<content:encoded><![CDATA[<p class="body"><span class="bodyHeader2">By Bob Knepp of American Electric Power</span></p>
<p class="body">Ever have one of those drawings                              that contain lots of graphics and when you click “Update”                              it seems to take forever? The only reason you are                              updating the view is because you just deleted this                              big ’ole heavy weight line that left all those                              gaps in the view. Granted, the update probably only                              takes a few seconds but it still seems like an eternity                              when the boss is breathing down your neck. Your solution                              is the incremental update command &lt;iupdate&gt;.</p>
<p class="body">In the “Key-in”                              browser type &lt;iupdate&gt;, then click on a data                              point in the related view. This will only update the                              active elements that need to be updated and will not                              update reference files. To update the reference file                              you must use the regular “Update” command.</p>
<p class="body">There are several options                              available with this command. Using the “Key-in”                              browser you will see that you can also use &lt;iupdate                              1&gt;, &lt;iupdate view&gt;, etc. Now you can really                              get fancy and set this up as a function key or in                              a custom tool box.</p>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/the-incremental-update-command/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Executing Long Sets of Key-in Strings</title>
		<link>http://microstationtips.com/executing-long-sets-of-key-in-strings/</link>
		<comments>http://microstationtips.com/executing-long-sets-of-key-in-strings/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 18:04:00 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Key-in Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=163</guid>
		<description><![CDATA[Many dialog boxes in MicroStation have limitations to the length of strings that can be entered into them. For example the “Function Keys” dialog when creating or editing a function key value has a 56 character limitation. Let’s say that you want to set up a function key that allows you set up an active [...]]]></description>
			<content:encoded><![CDATA[<p><span class="body">Many dialog boxes in MicroStation have limitations                              to the length of strings that can be entered into                              them. For example the “Function Keys” dialog                              when creating or editing a function key value has                              a 56 character limitation. </span></p>
<p class="body">Let’s say that you want                              to set up a function key that allows you set up an                              active design file’s settings and view display                              for a customer submittal and because you have a lot                              of drawings to get ready you will need to do this                              many times.</p>
<p class="body">Because the quantity of settings                              you want to ensure is large, the key-ins required                              will take far more than 56 characters, so you can’t                              do the whole thing with one function key.</p>
<p class="body">The solution for this is really                              simple. Create a text file that contains all the key-in                              commands that you want to run in the appropriate order,                              one command to a line. Save this text file with an                              appropriate name in a directory that is not too deep                              in the directory structure. Make sure that you do                              not use spaces in the file name or place it in a directory                              path that has a space in it.</p>
<p class="body">Now all you need to do to                              run this script from the MicroStation key-in browser                              or from a function key is to call it using the “@”                              character and the full path of the text file. Here’s                              an example of what you would type if the path to your                              script file was “c:\scripts\project35\setdgn.txt”:</p>
<p class="body">@c:\scripts\project35\setdgn.txt</p>
<p class="body">Make sure there are no spaces                              used anywhere in the string and also make sure that                              the full string does not exceed the maximum characters                              allowed in the dialog box.</p>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/executing-long-sets-of-key-in-strings/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quick two-letter key-ins</title>
		<link>http://microstationtips.com/quick-two-letter-key-ins/</link>
		<comments>http://microstationtips.com/quick-two-letter-key-ins/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 18:02:59 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Key-in Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[key-in]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=161</guid>
		<description><![CDATA[Although a graphical interface is great for many things, sometimes it&#8217;s faster to use two-letter MicroStation key-ins to adjust settings. For example, to set the active scale to 2.0, you can simply type &#8220;as=2&#8243; in the key-in browser. MicroStation has quite an extensive list of these two-letter key-ins for setting all manner of things from [...]]]></description>
			<content:encoded><![CDATA[<p class="body">Although a graphical interface is great for many                  things, sometimes it&#8217;s faster to use two-letter MicroStation key-ins                  to adjust settings. For example, to set the active scale to 2.0,                  you can simply type &#8220;as=2&#8243; in the key-in browser. MicroStation                  has quite an extensive list of these two-letter key-ins for setting                  all manner of things from the active level and color, which just                  about everyone is familiar with, to saving or activating views.                  The following is a list of two-letter key-ins separated by categories                  (do not use a space before the equal sign for these key-ins):</p>
<p class="body"><a href="http://www.axiomint.com/images/tips/quick_two_letter_keyins.pdf">Click                  here</a> to download a PDF version of this list.</p>
<p><span class="bodyBold">View manipulation</span><br />
<span class="body">OF= Turn off levels by number<br />
ON= Turn on levels by number<br />
RV= Rotate view(s) about center<br />
WO= Set view origin<br />
SV= Save view<br />
VI= Attach saved view<br />
DV= Delete saved view</span></p>
<p><span class="bodyBold">Text and dimensioning</span><br />
<span class="body">FT= Active font<br />
DF= Opens font dialog box<br />
TH= Active height<br />
TW= Active width<br />
TX= Active height and width<br />
LL= Active line length<br />
LS= Active line spacing<br />
TB= Tab spacing for importing text<br />
TI= Tag Increment amount<br />
LD= Dimension level<br />
TV= Upper and lower dimension tolerance limits</span></p>
<p><span class="bodyBold">Settings</span><br />
<span class="body">AA= Active angle<br />
AS= Active scale<br />
XS= Active x scale<br />
YS= Active y scale<br />
ZS= Active z scale<br />
GU= Master/Grid<br />
GR= Reference grid<br />
KY= (Snap) Divisor<br />
UR= (Unit Lock) Distance</span></p>
<p><span class="bodyBold">Set element and pattern attributes</span><br />
<span class="body">AP= Active pattern cell<br />
LV= Active level<br />
CO= Active color<br />
PA= Active pattern angle<br />
LC= Active line style<br />
PD= Active pattern spacing<br />
WT= Active line weight<br />
PS= Active pattern scale</span></p>
<p><span class="bodyBold">Precision input</span><br />
<span class="body">XY= &lt;x,y,z&gt; from origin along design                  files axes<br />
DI= &lt;distance, direction&gt; from last data or tentative point                  relative to view axes<br />
DL= &lt;Dx, Dy, Dz&gt; from last data or tentative point in design                  coordinates<br />
DX= &lt;Dx, Dy, Dz&gt; from last data or tentative point in view                  coordinates<br />
AX= Distance from Auxiliary Coordinate System (ACS) origin<br />
AD= Distance from last data or tentative point in ACS coordinates</span></p>
<p><span class="bodyBold">Cells</span><br />
<span class="body">AC= Set active cell and select place active                  cell tool with relative off<br />
AR= Set active cell and select place active cell tool with relative                  on<br />
CM= Place active cell matrix tool<br />
PT= Active point<br />
LT= Active terminator<br />
TS= Terminator scale<br />
CR= Edit cell information<br />
CD= Delete cell from cell library<br />
CC= Create cell</span></p>
<p><span class="bodyBold">3D modeling</span><br />
<span class="body">DP= Set the display depth from 0.0 of view&#8217;s                  z-axis<br />
DD= Distance to move display depth from current values<br />
AZ= Set the active depth from 0.0 of the view&#8217;s z-axis<br />
DZ= Distance to move active depth from current value<br />
SX= Save ACS<br />
RX= Attach ACS<br />
PX= Delete ACS</span></p>
<p><span class="bodyBold">File management</span><br />
<span class="body">RD= Open design file<br />
XD= Open design file with active design&#8217;s view configuration<br />
RC= Attach cell library<br />
RF= Attach reference file<br />
DR= Displays contents of a text file<br />
CT= Attach color table<br />
AM= Attach and activate menu<br />
AT= Activate tutorial</span></p>
<p><span class="bodyBold">Database</span><br />
<span class="body">AE= Define active entity<br />
DA= Displayable attribute type<br />
DB= Attach control file<br />
DS= Specify fence filter<br />
FI= Set database row as active entity<br />
RA= Set attribute review selection criteria<br />
RS= Name report table </span></p>
<p><span class="bodyBold">Digitizing</span><br />
<span class="body">SD= Active stream delta<br />
ST= Active stream tolerance</span></p>
<p><span class="bodyBold">User command</span><br />
<span class="body">UC= Activate user command<br />
UCC= Compile user command<br />
UCI= User command index<br />
OX= Retrieve user command index</span></p>
<p><span class="bodyBold">Other</span><br />
<span class="body">EL= Create element list file<br />
FF= Copy fence contents to new design file<br />
GO= Global origin<br />
SF= Move fence contents to new design file</span></p>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/quick-two-letter-key-ins/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The &#8220;Save View&#8221; key-in and reference files (for V7 and V8)</title>
		<link>http://microstationtips.com/the-save-view-key-in-and-reference-files-for-v7-and-v8/</link>
		<comments>http://microstationtips.com/the-save-view-key-in-and-reference-files-for-v7-and-v8/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 18:00:24 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Key-in Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[key-in]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=159</guid>
		<description><![CDATA[By Larry Shields, Graphics Designer at Stanley Consultants in Muscatine, Iowa If there is a particular area in a design file that you want so see as a reference file, then go into the file you will attach, zoom in to the area you want to see and save that view by using the key [...]]]></description>
			<content:encoded><![CDATA[<p class="body"><span class="bodyBold">By Larry Shields, Graphics                  Designer at Stanley Consultants in Muscatine, Iowa</span><br />
If there is a particular area in a design file that you want so                  see as a reference file, then go into the file you will attach,                  zoom in to the area you want to see and save that view by using                  the key in &#8220;sv=(name of saved view)&#8221;. Be sure to include                  the parentheses and not the quotes.</p>
<p><img src="http://www.axiomint.com/images/tips/tip_keyin.gif" alt="" width="327" height="139" /></p>
<p class="body">Now go into the master file you want to attach the                  view to. Open the &#8220;Reference Files&#8221; dialog box in MicroStation.                  When the &#8220;Attach Reference File&#8221; dialog box comes up,                  select the &#8220;Saved Views&#8221; name you gave it.</p>
<p><img src="http://www.axiomint.com/images/tips/tip_attach.gif" alt="" width="351" height="377" /></p>
<p class="body">Then, place the attachment where you want it. This                  works great when you only want to reference a certain area of                  a design file and nothing else.</p>
<p class="body">Thanks again, Larry!</p>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/the-save-view-key-in-and-reference-files-for-v7-and-v8/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The &#8220;RD=&#8221; Key-in</title>
		<link>http://microstationtips.com/the-rd-key-in/</link>
		<comments>http://microstationtips.com/the-rd-key-in/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 17:59:11 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Key-in Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=157</guid>
		<description><![CDATA[In MicroStation V8, you can open a file and go right into the model of your choice by using the &#8220;RD=&#8221; key-in. For example, &#8220;RD=project.dgn,sheet file&#8221; opens project.dgn and goes directly to the model called Sheet File. Assign this to a function key while you are working on a particular section of a project and [...]]]></description>
			<content:encoded><![CDATA[<p><span class="bodyHeader"><br />
</span><span class="body">In MicroStation V8, you can open a file                  and go right into the model of your choice by using the &#8220;RD=&#8221;                  key-in. For example, &#8220;RD=project.dgn,sheet file&#8221; opens                  project.dgn and goes directly to the model called Sheet File.</p>
<p>Assign this to a function key while you are working on a particular                  section of a project and you will save yourself a couple of minutes                  every day.<br />
</span></p>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/the-rd-key-in/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The SET RANGE key-in command</title>
		<link>http://microstationtips.com/the-set-range-key-in-command/</link>
		<comments>http://microstationtips.com/the-set-range-key-in-command/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 17:57:46 +0000</pubDate>
		<dc:creator>MicroStation User</dc:creator>
				<category><![CDATA[Key-in Tips]]></category>
		<category><![CDATA[MicroStation Tips]]></category>
		<category><![CDATA[key-in]]></category>
		<category><![CDATA[Steve Palmer]]></category>

		<guid isPermaLink="false">http://microstationtips.com/?p=155</guid>
		<description><![CDATA[By Steve Palmer, Axiom&#8217;s Executive Product Manager The SET RANGE key-in command is not documented, but is supported in all versions of MicroStation. This command displays element ranges on the screen. [Editor's note: The range of an element is given by the lower-left and upper-right coordinates of the smallest box that will contain the element. [...]]]></description>
			<content:encoded><![CDATA[<p><span class="bodyBold">By Steve Palmer, Axiom&#8217;s Executive Product                  Manager</span><span class="bodyHeader2"><br />
</span><span class="body">The SET RANGE key-in command is not                  documented, but is supported in all versions of MicroStation.                  This command displays element ranges on the screen. [Editor's                  note: The range of an element is given by the lower-left and upper-right                  coordinates of the smallest box that will contain the element.                  You can think of the range of an element as a box - parallel to                  the x and y-axis of the design plane - that precisely encompasses                  the element.] Below is an example of how elements look after keying                  the SET RANGE command and updating the desired view:</span></p>
<p><img src="http://www.axiomint.com/images/tips/april-04-tip-1.gif" alt="" width="208" height="98" /></p>
<p class="body">The SET RANGE command displays the range data that&#8217;s                  stored in the element (V7 or V8). This key-in command can be used                  to diagnose why you can&#8217;t snap to or select an element or why                  an element is excluded from fence operations.</p>
<p class="body">Below is an example where the range for a shared                  cell is wrong (taken from an actual Axiom customer file):</p>
<table border="0" cellspacing="0" cellpadding="0" width="100">
<tbody>
<tr>
<td><img src="http://www.axiomint.com/images/tips/april-04-tip-2.gif" alt="" width="479" height="147" /></td>
</tr>
<tr>
<td class="bodyCaptions">The bold red rectangle identifies the                      incorrect range rectangle for the &#8220;S&#8221; shaped element.                      This range error throws off the range for the whole shared                      cell.</td>
</tr>
</tbody>
</table>
<p class="body">The SET RANGE command graphically illustrates that                  the stored range is incorrect, as illustrated above. As a strange                  side effect of this range error, other elements near this shared                  cell were un-selectable. To remedy this, you could redraw the                  shared cell definition — or you can automatically handle                  this and any other corruption in the MicroStation file using <em>FileFixer</em>.</p>
<p class="body">The SET RANGE command is also useful when examining                  elements with Axiom&#8217;s <em>Problem Element Viewer</em> — the                  utility that let&#8217;s you graphically view the problem elements found                  by <em>FileFixer</em> or EdG.</p>
]]></content:encoded>
			<wfw:commentRss>http://microstationtips.com/the-set-range-key-in-command/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

