I am trying to extend a line, but for some reasons, it does not select the line that I am aiming to extend; instead it selects the line below the aimed line! Please advise.
Use tentative snap. Keep pressing tentative snap until the proper line is selected. Or, if you just data point on a line and it is not the correct line, right click and it should select the next line.
Power InRoads v8i 08.11.09.615
Microstation CONNECT 10.16.02.34
Microstation v8i SS 10 08.11.09.919
ORD CONNECT 2021 R1 10.10.1.3
Yukio said:I am trying to extend a line
Please respect the best practices and specify what do you use and its exact version (e.g. build number).
Also, in the discussed case, provide information what tool or key-in you use to extend the line, because several different options exist.
Yukio said:instead it selects the line below the aimed line!
Overlapping elements are usually selected in the same order they are stored in DGN file, but I think there is not publicly defined rule.
A selection can be "rotated" in different way, but the most typical way (as mwlong wrote already) to select "some" element using data point (left mouse button) and not the right one is selected, to use reset (right mouse button) to ask MicroStation to try to select another one in location tolerance.
Another option is to use Tab key, but it is better when snap points should be changed and also it also requires an interaction with keyboard, whereas data point / reset mechanism is "mouse only" (and so simpler and quicker) way ;-)
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
To add on to what mwlong said, if you are using AccSnap, you can press the TAB key on the keyboard to cycle through the lines.
Rod WingSenior Systems Analyst
Rod Wing said:AccSnap, you can press the TAB key on the keyboard to cycle through
Good tip, gotta try that.
Jan Šlegr said:Overlapping elements are usually selected in the same order they are stored in DGN file
Yes, order as stored. I used to leverage that when working in a DGN. But since the inception of Connect I've noticed design file order doesn't seem to follow the same behaviors it used to, sometimes seems random.
Connect r17 10.17.00.209 self-employed
Bob Rayner said:I used to leverage that when working in a DGN.
It is the topic for another (and potentially long ;-) discussion. Because I do not want to deviate from original topic, short comment only ;-)
Elements order in DGN file has became obsolete in V8 XM Edition, when display priority was introduced. From V8i, when Display Styles were implemented, it is recommended to do not rely on this feature.
Bob Rayner said:But since the inception of Connect I've noticed design file order doesn't seem to follow the same behaviors it used to, sometimes seems random.
I do not recall any scenario when the order looks random, but your are right the order in CE, even at API level, is "deprecated feature in "do not use it" mode. In my opinion it is a result of "paradigm shift", when developers work with objects (through so called element handlers) and do not care how they are stored. Even when "file position" info can be still found in some API functions, it is not ensured and code should not rely on this information.