Snap Intersection
Chuck
intersection. However it doesn't work. The definition on intersection snap
in "help" doesn't make sense-it doesn't sound like an intersection to me. A
fellow employee has been using intergraph/microstation for years and doesn't
understand why it doesn't snap to an intersection. (like where to lines
cross). Have Microstation 95 and 5.
Can anyone help me out please?
Thanks
Chuck Ainsworth
Doug Persson
The one you are probably referring is the one on the snaps menu. That
requires two tentative clicks close to the crossing lines. The keyin for this
command is: LOCK SNAP INTERSECTION 2. Not surprisingly, there is also a LOCK
SNAP INTERSECTION 1. This is the one you are probably looking for. It will
cause the cursor to snap to an intersection with one tentative click. You
have to keyin this one. Why the interface people at Bentley decided make the
number 2 snap the default is anyone's guess.
In article <79taor$7v0$1...@oak.prod.itd.earthlink.net>, "Chuck"
For email replies, remove the ".junk"
from my email address.
For Ustn 3D Info Visit the M3D site at
http://www.teleport.com/~dpersson
Thomas Voghera
As others have pointed out there is two snaps for intersection. BOTH is useful.
Search www.dejanews.com for this issue.
Thomas V
Chuck wrote:
> I've been training on microstation for about 4 weeks. There is a snap to
> intersection. However it doesn't work. The definition on intersection snap
> in "help" doesn't make sense-it doesn't sound like an intersection to me. A
> fellow employee has been using intergraph/microstation for years and doesn't
> understand why it doesn't snap to an intersection. (like where to lines
> cross). Have Microstation 95 and 5.
>
> Can anyone help me out please?
>
> Thanks
>
> Chuck Ainsworth
--
******************************************************************
Thomas Voghera, TVAK
Box 8215, 163 08 SPÅNGA, SWEDEN
Tel +46 8 795 7630 Fax +46 8 795 7587 Mob +46 70 695 7630
e-mail: vog...@ibm.net
******************************************************************
Phil Chouinard [Bentley]
> I've been training on microstation for about 4 weeks. There is a
> snap to intersection. However it doesn't work. The definition on
> intersection snap in "help" doesn't make sense-it doesn't sound like
> an intersection to me. A fellow employee has been using
> intergraph/microstation for years and doesn't understand why it
> doesn't snap to an intersection. (like where to lines cross). Have
> Microstation 95 and 5.
Sent this privately last night... figured that it might be beneficial to
post here.
The process of identifying the intersection of two linear elements
involves enabling the intersect snap lock and then selecting each of the
elements in question by identifying them with a tentative point.
Similarly, element location via keypoint snap highlights elements in the
order in which they are located distance-wise from the cursor's
position, regardless of the order that they exist in the design
file--the element that is closest to the cursor is highlighted first,
and so on until no more elements fall in the locate tolerance. The
search then starts again with the closest element.
Previous to Version 5, these processes operated a little bit
differently. Intersection snap allowed users to find the intersection of
linear elements by identifying a single tentative point close to where
the elements *crossed.* Keypoint snap tentative points *cycled* through
all of the elements that fell within the cursor's locate tolerance and
highlighted elements as they sequentially existed in the design file.
When no more elements could be located, the tentative selection acted as
though an element could not be found. A subsequent tentative point would
start the search over from the beginning of the design file.
This functionality was changed in Version 5 primarily in response to
users' change requests (as well as to provide *apparent intersects*,
which can not be done using a single data point selection). And while
these new abilities were added to MicroStation, the Version 4.x styles
of operation were not removed. In order to make these particular
operations the same in MicroStation now as in Version 4.x, the following
key-ins can be executed while in a MicroStation design session:
lock snap intersect 1
lock snap keypoint 1
NOTE: These settings are not stored in the design file. To retain these
tentative abilities, the above commands should be executed each time you
enter a design file. You can assign these key-ins to function keys or
custom palette icons to make them easily accessible. HTH
============== One of "The People Behind MicroStation" ==============
Phil Chouinard - ITO Phone: (610) 458-5000
Bentley Systems, Inc. Fax: (610) 458-1060
685 Stockton Drive CompuServe: 75300,3376
Exton, PA USA 19341-0678 mailto:Phil.Ch...@Bentley.com
================== Engineering the Future Together ==================
Phil Chouinard [Bentley]
> Actually, there are two intersection snaps and yes, they both work.
>
> The one you are probably referring is the one on the snaps menu. That
> requires two tentative clicks close to the crossing lines. The keyin
> for this command is: LOCK SNAP INTERSECTION 2. Not surprisingly,
> there is also a LOCK SNAP INTERSECTION 1. This is the one you are
> probably looking for. It will cause the cursor to snap to an
> intersection with one tentative click. You have to keyin this one.
> Why the interface people at Bentley decided make the number 2 snap the
> default is anyone's guess.
Doug: You are correct, Lock Snap Intersection 1 does utilize single
location functionality as it existed previous to Version 5. Regarding
Lock Snap Intersection 2, actually 2 just so happens to work. In fact,
any number other than 1 will do the same thing.
Jud Caswell
because it is more useful. It allows you to easily snap to the intersection
of two lines that don't actually cross -- in other words, it allows you to
easily snap to the projected intersection of two lines. (or a line and a
circle.)
-Jud
Doug Persson wrote in message ...
Bernhard Leicher
Phil Chouinard [Bentley] schrieb in Nachricht <36C2DB...@Bentley.com>...
>Chuck wrote:
(SNIP)
the following
>key-ins can be executed while in a MicroStation design session:
>
> lock snap intersect 1
> lock snap keypoint 1
>
>NOTE: These settings are not stored in the design file. To retain these
>tentative abilities, the above commands should be executed each time you
>enter a design file. You can assign these key-ins to function keys or
>custom palette icons to make them easily accessible. HTH
>
And NOTE: lock snap intersect 1 is broken in the one or other version of
MicroStation. At least it used to be in MicroStation 95 (5.5.3.54).
Regards, Bernhard Leicher
Chris Zakrewsky
As far as I remember, Rob Brown fixed it for SE.
And you are right, there were several builds of 95 with this
key-in broken.
Phil just forgot to mention it ;-)
--
Cheers,
/Chris Zakrewsky
+------------------------------------------------------+
| *** WE HAVE MOVED! *** |
| ch...@cadperf.se http://www.ustation.se |
+------------------------------------------------------+
| Team uStation AB (CAD Perfect) |
| Älta Strandväg 37B, S-138 33 ÄLTA, SWEDEN |
| tel +46 8 773 1003 fax +46 8 773 3004 |
+------------------------------------------------------+
| Bentley Sales Center, Independent Software Developer |
+------------------------------------------------------+
Bernhard Leicher <bernhard...@t-online.de> wrote in article <79ve59$751$2...@news01.btx.dtag.de>...
Daniel Beekwilder
It is absolutely astonishing that with considerable experience just trawling
through a newsgroup can bring enlightment and improve productivity, who said
the internet was crap?
But the question remains why do a lot of really useful tools such as all the
snaps and some old commands such as active angle pt 3 lack a graphical
representation in the new interface?
Or how do I incorporate a set of frequently used snaps into a custom built
tool frame for the selfish motive of saving screen real estate?
These questions will probably remain mysteries!
Phil, thanks for the tip re intersection snap
Daniel
Chris Zakrewsky wrote in message <01be561b$41d55bc0$656f7a7b@kitty>...
Jud Caswell
Daniel Beekwilder wrote in message <36c3f...@139.134.5.33>...
>Of all the obscure things you learn!
>But the question remains why do a lot of really useful tools such as all
the
>snaps and some old commands such as active angle pt 3 lack a graphical
>representation in the new interface?
I can see where you're coming from, but as you state (below) saving real
estate is an important issue. There's also the issue of the interface
getting so big and unwieldy that it scares the newbies. That being said, I
do wish there was active angle by 3 points (and /actan2) and how about
"change dimension extension" to turn on and off the display of those pesky
extension lines? That's critical, from my standpoint.)
I think rather than incorporating all these options into the graphic user
interface, there should be a list of old keyins (or how about ALL keyins --
for the benefit of developers/tweakers) that lists what command is invoked.
>
>Or how do I incorporate a set of frequently used snaps into a custom built
>tool frame for the selfish motive of saving screen real estate?
Workspace menu, customize. Make yourself a new toolbox (or frame).
-Jud
Doug Persson
>
>Daniel Beekwilder wrote in message <36c3f...@139.134.5.33>...
>>Of all the obscure things you learn!
>I think rather than incorporating all these options into the graphic user
>interface, there should be a list of old keyins (or how about ALL keyins --
>for the benefit of developers/tweakers) that lists what command is invoked.
In the ../ustation/mdl/include directory (for SE and earlier Ustn's) there is
a file called CMDLIST.H. Open this file with a text editor. This file contains
probably most if not all the possible keyins for Ustn. They are listed in this
fashion:
#define CMD_DEPTH_DISPLAY 0x12010000 /* VIEWPARAM */
#define CMD_DEPTH_DISPLAY_PRIMITIVE 0x12010100 /* VIEWPARAM */
#define CMD_DEPTH_DISPLAY_INTERACTIVE 0x12010200 /* VIEWPARAM */
#define CMD_DEPTH_ACTIVE 0x12020000 /* VIEWPARAM */
All you have to remember is not to keyin the "CMD" and the underbars. This
files will contain many commands you may have not heard before. This file
does not contain the the two letter equal type keyins. ex. lv=1
Dan Lynch
missing from the on-screen menus and a DIFFERENT set missing from the
tablet menus? I have /active angle pt 3/ on the default tablet menu
which ships with MicroStation, yet it is missing some crazy things like
/insert vertex/. Very weird
Dan Lynch
Daniel Beekwilder wrote:
>
> But the question remains why do a lot of really useful tools such as all the
> snaps and some old commands such as active angle pt 3 lack a graphical
> representation in the new interface?
--
Replies to me will bounce
unless you debounce my address
MPalicki
You have to snap to one element, then the other, and it will highlite and dash
both and snap to their intersection, either actual or projected.
In article <79taor$7v0$1...@oak.prod.itd.earthlink.net>,
"Chuck" <im...@earthlink.net> wrote:
> I've been training on microstation for about 4 weeks. There is a snap to
> intersection. However it doesn't work. The definition on intersection snap
> in "help" doesn't make sense-it doesn't sound like an intersection to me. A
> fellow employee has been using intergraph/microstation for years and doesn't
> understand why it doesn't snap to an intersection. (like where to lines
> cross). Have Microstation 95 and 5.
>
> Can anyone help me out please?
>
> Thanks
>
> Chuck Ainsworth
>
>
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Fpmann
>do wish there was active angle by 3 points
There is! Just key-in ACT ANGLE PT3 for you 3 point angle and ACT ANGLE PT2
for the two point variety.
>and how about
>"change dimension extension"
There too! Key-in CHANGE DIM WITNESS TOGGLE and select the dimension line;
this will even turn a dimension line on, too!
Jim Weisgram
>I'd say that Bentley chose the two-tentative snap as the default mode
>because it is more useful. It allows you to easily snap to the intersection
>of two lines that don't actually cross -- in other words, it allows you to
>easily snap to the projected intersection of two lines. (or a line and a
>circle.)
>
>-Jud
>
Another good thing about the 2-tentative snap is that in very dense areas, a
1-tentative snap can be maddening trying to get to the right one.s
--
Jim Weisgram
Oregon Department of Transportation
email: jwei...@hotmail.com
All opinions expressed are mine and not my employers (but they ought to be)
Gary N. Wood
wrote:
>"Jud Caswell" <judca...@caswelleng.com> wrote:
>
>>I'd say that Bentley chose the two-tentative snap as the default mode
>>because it is more useful. It allows you to easily snap to the intersection
>>of two lines that don't actually cross -- in other words, it allows you to
>>easily snap to the projected intersection of two lines. (or a line and a
>>circle.)
>>
>>-Jud
>>
>
>Another good thing about the 2-tentative snap is that in very dense areas, a
>1-tentative snap can be maddening trying to get to the right one.s
Yep. Those are the two HUGE advantages of the "identify two lines"
method of finding intersections.
Unfortunately, it seems that ever since Vellum on the Macintosh with
it's "intelligent cursor", lot's of folks think they want a "snap to
the point I want when I pick here" or even a "snap to all possible
points continuously as I move the cursor".
It demos real well. Its wizzy. And I have to admit there are certain
scenarios where it does save a little time over the "pick the two
lines" method.
Where it falls down big-time, is in Jud's scenario where there isn't
yet a point of intersection, or in Jim's scenario were there are many.
With software that only allows the "auto" mode or the "one-point"
mode, it just isn't possible for the software to know which is the
right point. Worse, even if it gets the right point, you can't confirm
that it is correct without zooming way in.
At that point, it is far less productive then MicroStation's current
default.
-Gary
-------------------
Gary N. Wood
Compute Abilities
gw...@comabi.mv.com
Tel: (603) 924-2310
-------------------
Bruce E. Irving
Gary N. Wood wrote in message <36c80ca...@news-pnh.mv.net>...
>
>With software that only allows the "auto" mode or the "one-point"
>mode, it just isn't possible for the software to know which is the
>right point. Worse, even if it gets the right point, you can't confirm
>that it is correct without zooming way in.
>
>At that point, it is far less productive then MicroStation's current
>default.
>
I tend to agree that the current default is rather more productive. The
problems arise from it being unexpected behavior to new users. Its plenty
quick and with great visual feedback to just snap-snap-data.
Just a thought - What if the intersection snap would look for two elements
within tollerance and highlight both if found; but if not just highlight
one. In other words combine the behavoir of the two modes.
I think this might be able to fool most users into thinking it works the way
they prefer. If you're accustomed to snapping to two elements separately,
then your surely not going to point to a crowded area, but rather to the
individual elements where they are separate. So you might not notice the
difference.
--Bruce Irving
Gary N. Wood
<bir...@my-dejanews.com> wrote:
>Just a thought - What if the intersection snap would look for two elements
>within tollerance and highlight both if found; but if not just highlight
>one. In other words combine the behavoir of the two modes.
>I think this might be able to fool most users into thinking it works the way
>they prefer. If you're accustomed to snapping to two elements separately,
>then your surely not going to point to a crowded area, but rather to the
>individual elements where they are separate. So you might not notice the
>difference.
>
This would work as long as it was used the way you describe.
I think there are some UI issues howwever as soon as someone clicks on
an area where there are more than two lines within the proximity
sensor. What two lines get selected? How do you change it if it is
wrong?
Currently when you pick one line and then another, if it happend to be
wrong, you can just tentative on another line and the oldest one is
discarded.
If the software automatically picked two lines for you, and one or
both were wrong, it becomes problematic how to get the correct lines
involved.
There may be a convenient solution that is consistent with
MicroStation behavior, but it isn't immediately obvious.
Greg Jackson
> This would work as long as it was used the way you describe.
>
> I think there are some UI issues howwever as soon as someone clicks on
> an area where there are more than two lines within the proximity
> sensor. What two lines get selected? How do you change it if it is
> wrong?
>
> Currently when you pick one line and then another, if it happend to be
> wrong, you can just tentative on another line and the oldest one is
> discarded.
>
> If the software automatically picked two lines for you, and one or
> both were wrong, it becomes problematic how to get the correct lines
> involved.
>
> There may be a convenient solution that is consistent with
> MicroStation behavior, but it isn't immediately obvious.
>
How about adding (or giving users the ability to add) a button for
_both_ snap modes to the button bar? Since reading this thread, i have
already created a toolbar mapping the one-click keyin to it and docked
it next to the button bar, and switch between the two. Or is it already
possible to modify the button bar/shift+tentative menu ?
Greg
Chris Zakrewsky
The setting is saved to the same bit in DGN header.
When you save setting, it is ambiguous in this case.
So, the decision was to NOT save the older (classic) behavior.
HTH
--
Remaining With Our Very Best Regards,
/Chris Zakrewsky
+------------------------------------------------------+
| *** WE HAVE MOVED! *** |
| ch...@cadperf.se http://www.ustation.se |
+------------------------------------------------------+
| Team uStation AB (CAD Perfect) |
| Älta Strandväg 37B, S-138 33 ÄLTA, SWEDEN |
| tel +46 8 773 1003 fax +46 8 773 3004 |
+------------------------------------------------------+
| Bentley Sales Center, Independent Software Developer |
+------------------------------------------------------+
Greg Jackson <gre...@hotmail.com> wrote in article <36C7C7D5...@hotmail.com>...
Chris Zakrewsky
> If the software automatically picked two lines for you, and one or
> both were wrong, it becomes problematic how to get the correct lines
> involved.
Not necessarily.
Intelligent UI could make a qualified guesses depending on mouse moves
before Accept.
But this is probably scheduled for indefinite future... ;-)
Bernhard Leicher
Gary N. Wood schrieb in Nachricht <36c80ca...@news-pnh.mv.net>...
>mode, it just isn't possible for the software to know which is the
>right point. Worse, even if it gets the right point, you can't confirm
>that it is correct without zooming way in.
>
>At that point, it is far less productive then MicroStation's current
>default.
>
>-------------------
>Gary N. Wood
>Compute Abilities
>gw...@comabi.mv.com
>Tel: (603) 924-2310
>-------------------
But aren't those two cases "Density" and "No apparent intersection" the rare
cases and snapping to an obvious, clear intersection of two elements the
regular one?
And I can't see what's productive about
1. Click (to activate snap mode)
2. Click (to get the one element)
3. Click (to get the other element)
4. Click (to accept tentative point)
as opposed to 2 clicks (just one would be even better).
Regards, Bernhard Leicher
Gary N. Wood
(Bernhard Leicher) wrote:
>
>But aren't those two cases "Density" and "No apparent intersection" the rare
>cases and snapping to an obvious, clear intersection of two elements the
>regular one?
>
Depends on your files.
For demo files, and classroom exercises, absolutely! That's part of
how the feature demos so well.
For REAL work, maybe/maybe not. That's why it's nice to be able to
have both a one point intersection snap, and a two point.
I prefer the two point as a default, and as the first one to teach,
because it ALWAYS works.
The one point version is a little quicker, when it is applicable.
For myself, I probably lose as much deciding about it, as it would
cost me two pick the two lines even when I didn't really have to, so I
just stick with the two line version, and take comfort knowing that if
I pick 'em right, I'm guaranteed the right intersection.
Jim Weisgram
>
>Gary N. Wood schrieb in Nachricht <36c80ca...@news-pnh.mv.net>...
>>On Sat, 13 Feb 1999 19:31:50 GMT, jwei...@hotmail.com (Jim Weisgram)
>>wrote:
>
>But aren't those two cases "Density" and "No apparent intersection" the rare
>cases and snapping to an obvious, clear intersection of two elements the
>regular one?
>
>And I can't see what's productive about
>1. Click (to activate snap mode)
>2. Click (to get the one element)
>3. Click (to get the other element)
>4. Click (to accept tentative point)
>
>as opposed to 2 clicks (just one would be even better).
>
>Regards, Bernhard Leicher
>
I am sure it varies considerably from discipline and application within
discipline. Probably our most common use is working on maps showing the results
of topographic surveys, plus making plan sheets of the above.
In which case dense linework is the norm on an urban project, less so on most
rural projects.
But it isn't the only thing we do.
So I can see it both ways. In my opinion I would say that given a choice between
maddening behavior for some of our operators, and a training inconvenience for
many of our users, I would pick the latter, if I was given a choice.
What stunned me, however, was learning that many of our experienced operators
never realized that the intersection snap behavior had changed! I wonder what
kind of results they have been getting all this time?
Which kind of makes the case against my preference, I suppose.
Tracy Clarke
of the reasons given by others already. And if you are snapping to a
clear intersection (where many think the single tentative point mode is
better) simply place the cursor over the intersection and double click
the tentative button and accept, WooHhoo :-)
HTH. (My $0.02)
Tracy.
Chris Zakrewsky wrote:
>
> Hi,
>
> The setting is saved to the same bit in DGN header.
>
> When you save setting, it is ambiguous in this case.
>
> So, the decision was to NOT save the older (classic) behavior.
>
> HTH
Nathan Emerson
at 15/02/99 17:19
<snip>
>
>But aren't those two cases "Density" and "No apparent intersection" the rare
>cases and snapping to an obvious, clear intersection of two elements the
>regular one?
>
>And I can't see what's productive about
>1. Click (to activate snap mode)
>2. Click (to get the one element)
>3. Click (to get the other element)
>4. Click (to accept tentative point)
>
>as opposed to 2 clicks (just one would be even better).
>
>Regards, Bernhard Leicher
16/02/99 08:27
By your reasoning it would still be 3 clicks using the 1 click intersect
snap, not 2:
1. Click (to activate snap mode)
2. Click (to get the elements)
3. Click (to accept tentative point)
Just how much time does the loss of one click save you considering how
rarely you use intersect snap?
-------
Nathan
ChrisCH
<tcla...@cgocable.net> écrit:
> I recommend ALWAYS use the (default) two tentative snap mode, because
>of the reasons given by others already. And if you are snapping to a
>clear intersection (where many think the single tentative point mode is
>better) simply place the cursor over the intersection and double click
>the tentative button and accept, WooHhoo :-)
WooHhoo - fact ::)
End of the discussion I guess.
Thank you tracy.
Chris.
Thomas Voghera
Where else in ustn is double datapoint used?
Thomas V
ChrisCH wrote:
--
Gary N. Wood
<thomas....@telia.com> wrote:
>Double click?
>Where else in ustn is double datapoint used?
>
>Thomas V
>
>ChrisCH wrote:
>
>> Le Mon, 15 Feb 1999 19:56:53 -0500, Tracy Clarke
>> <tcla...@cgocable.net> écrit:
>>
>> > I recommend ALWAYS use the (default) two tentative snap mode, because
>> >of the reasons given by others already. And if you are snapping to a
>> >clear intersection (where many think the single tentative point mode is
>> >better) simply place the cursor over the intersection and double click
>> >the tentative button and accept, WooHhoo :-)
>>
>> WooHhoo - fact ::)
>>
>> End of the discussion I guess.
>>
>> Thank you tracy.
>>
>> Chris.
Double Click the Tentative button. This is pretty easy if you have a
three button mouse, with the middle set to Tentative.
If you are using the Mac single button mouse, I guess you could still
click twice while holding the modifier key down.
The whole idea is that the first tentative finds one of the lines and
with the second, MicroStation is apparently smart enough to not pick
the same one again, if it can find another.
To answer the other question, double clicking on tools and the snap
button bar is supported.
Changes tools from default continuous mode, to a "single-shot" mode.
Changes the default snap on the button bar.
Tracy Clarke
<chomp>
>
> Double Click the Tentative button. This is pretty easy if you have a
> three button mouse, with the middle set to Tentative.
>
> If you are using the Mac single button mouse, I guess you could still
> click twice while holding the modifier key down.
>
> The whole idea is that the first tentative finds one of the lines and
> with the second, MicroStation is apparently smart enough to not pick
> the same one again, if it can find another.
Actually what I was referring to is NOT a true "double-click", you
could give the first tentative point now, then go to
lunch/dinner/coffee/a nooner/sleep... then come back and give the second
tentative point ....
>
> To answer the other question, double clicking on tools and the snap
> button bar is supported.
>
> Changes tools from default continuous mode, to a "single-shot" mode.
>
> Changes the default snap on the button bar.
Opposite for me, guess it depends on your (user) preferences.
Also try double data points (true doubles) on many Dialog boxes, i.e.
Reference files...
HTH.
Tracy.
Keith Laurie
Is it possible to edit the "snpas" tollbar, to include a button for invoking
the single shot keyin (and vice versa)? I went for a stroll through the edit
toolbox zone, but had no luck.
Not that I intend using it, but it might be useful for those diehards who
need time to adjust to the better way.
Keith Laurie
Tracy Clarke wrote in message <36CA2D18...@cgocable.net>...
Gary N. Wood
wrote:
>Just to keep this discussion going...
>
>Is it possible to edit the "snpas" tollbar, to include a button for invoking
>the single shot keyin (and vice versa)? I went for a stroll through the edit
>toolbox zone, but had no luck.
>
The Snaps button bar sort of looks like a Tool Box, but it actually is
a somewhat different animal under the covers.
So, we don't get to edit it.
If you want to make a tool for the Key-In that invokes the Single
point snap, you'll have to put it in some other Tool Box.
Another reason to just tentative twice in a row on the same point with
the two point snap. I bet you could do that a lot faster than you
could click a button to switch to single point mode.
Daniel Beekwilder
I have had to create a toolbox of the snaps that I use just to incorporate
into a compact user interface.
Regards
Daniel
Gary N. Wood wrote in message <36cb602f...@news-pnh.mv.net>...
Tracy Clarke
>
> Just to keep this discussion going...
>
> Is it possible to edit the "snpas" tollbar, to include a button for invoking
> the single shot keyin (and vice versa)? I went for a stroll through the edit
> toolbox zone, but had no luck.
>
> need time to adjust to the better way.
Is my time here wasted? Come on! Resistance Is Futile! (one extra
simple click or a confusing set of buttons/dialogs/tool frames... to
navigate, you pick! (I Think Ustn users are smarter than that, given the
knowledge :-) )
Good Night, Tracy. ;-)
>
> Keith Laurie
>
> Tracy Clarke wrote in message <36CA2D18...@cgocable.net>...
> >"Gary N. Wood" wrote:
> ><chomp>
> >>
> >> Double Click the Tentative button. This is pretty easy if you have a
> >> three button mouse, with the middle set to Tentative.
> >>
> >> If you are using the Mac single button mouse, I guess you could still
> >> click twice while holding the modifier key down.
> >>
> >> The whole idea is that the first tentative finds one of the lines and
> >> with the second, MicroStation is apparently smart enough to not pick
> >> the same one again, if it can find another.
> >
> > Actually what I was referring to is NOT a true "double-click", you
> >could give the first tentative point now, then go to
> >lunch/dinner/coffee/a nooner/sleep... then come back and give the second
> >tentative point ....
> >
> >>
> >> To answer the other question, double clicking on tools and the snap
> >> button bar is supported.
> >>
> >> Changes tools from default continuous mode, to a "single-shot" mode.
> >>
> >> Changes the default snap on the button bar.
> >
> >Opposite for me, guess it depends on your (user) preferences.
> >
> > Also try double data points (true doubles) on many Dialog boxes, i.e.
> >Reference files...
> >
> >HTH.
> > Tracy.
> >
> >>