<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Components/points merge with undisplayed components when adding a new component</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/195499/components-points-merge-with-undisplayed-components-when-adding-a-new-component</link><description>I&amp;#39;m having an issue with my templates. I have a null point to create an auxilary lane where there are the corresponding corridor references. None of the components in the Aux lane null point are used in the regular mainline and I have display rules to</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Components/points merge with undisplayed components when adding a new component</title><link>https://communities.bentley.com/thread/580365?ContentTypeID=1</link><pubDate>Tue, 14 Apr 2020 18:54:17 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f9ac362a-bbbc-4bd9-a47f-616b803003c9</guid><dc:creator>Jonathon Nichols</dc:creator><description>&lt;p&gt;Thanks Chuck! Glad to know I wasn&amp;#39;t just going crazy with things automatically merging. Hopefully they add some feature like that in the future.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Components/points merge with undisplayed components when adding a new component</title><link>https://communities.bentley.com/thread/580358?ContentTypeID=1</link><pubDate>Tue, 14 Apr 2020 18:29:16 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:360925bd-6ddc-4182-bcd4-aa7b0487e283</guid><dc:creator>caddcop</dc:creator><description>&lt;p&gt;There are times when the software tries to &amp;quot;help&amp;quot; and merge things automatically. So the methodology of bringing in an addition component group in an unconnected manner before moving it into shape is a valid workmode. Ideally, there should be a setting that can be toggled that controls the automatic merging of coincidental points. It&amp;#39;s probably hard to come up with a compact enough label to adequately describe its function.&lt;/p&gt;
&lt;p&gt;Sometimes you want to preserve certain points but don&amp;#39;t care about others. So right now, manually merging is the best way to ensure that only the points you want merged get merged.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Components/points merge with undisplayed components when adding a new component</title><link>https://communities.bentley.com/thread/580318?ContentTypeID=1</link><pubDate>Tue, 14 Apr 2020 14:28:24 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:59808d71-87a4-4317-bc15-7877b82e19b8</guid><dc:creator>Jonathon Nichols</dc:creator><description>&lt;p&gt;My current workaround is to not create the new component on the points of the other component but rather &amp;quot;off in space&amp;quot; with the two connecting points unconstrained and then manually merge them. Does anyone know why this happens? This seems like an arduous step.&lt;br /&gt;&lt;img src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/5922/pastedimage1586874562119v1.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>