I have noticed maybe a glitch when using Connect Edition 14 Pattern-hatch area. When you use the "Hatch Area" and checking the option of "Associative Boundary" it is opposite of the previous version of Microstation V8i. In Microstation V8i you were able to check the Associative Boundary option and it would hatch an area with a boundary. Now when selecting the associative Boundary in Connect Edition it does not give you a boundary when hatching an area. It gives you the boundary when the option is not checked instead of when it is checked. Maybe this was meant to be the change but thought I would bring that up.
MicroStation Forum - Hatch Area in Connect Edition
I have used Flood method with unchecked the boundary appears around an area and checked has no boundary. I also used by Element and it was the same results. I just notice with using by points the associative Boundary option is greyed out.
Which method you use for hatching Flood or element?
Its not the issue that the option was changed to "Drop pattern" its that the method is opposite while using the hatch - associative boundary in connect verses using associative pattern in V8i.
Are you referring to this?
https://communities.bentley.com/products/microstation/i/drafting_and_detailing/replace-drop-pattern-with-associative-pattern-in-the-patterning-tools-tool-settings-window
I think you are mixing up Associative Pattern with Associative Boundary (understandable, it was certainly confusing).
The Associative Pattern toggle was changed to a Drop Pattern toggle to make what it does more clear (drop results in "loose" elements in a graphic group to represent the hatch").
The term "associative" when used in the context of dimensions, multilines, and cells means the element reacts/updates when other elements it depends on are modified. The Associative Pattern option didn't work that way, it just added a displayable attribute like fill to a "closed" element, there's no external element dependency.
The behavior of Associative Region Boundary, which was shortened to just Associative Boundary is unchanged. The "hatch" is created as a new element with a dependency on the selected "boundary" element(s) and automatically updates itself when the boundary elements are modified.
HTH
-B
Yea, we never close nuthin. Someone else will have this same issue, lots of folks still migrating to the bug ridden Connect software. I noticed right away I sometimes had to check drop pattern if I did not want Microstation to create a boundary line for me.
I come to realize that your statement is true "The Associative Pattern toggle was changed to a Drop Pattern toggle to make what it does more clear (drop results in "loose" elements in a graphic group to represent the hatch)". Using the Drop Pattern now is as using the Associative Pattern as in V8i. Yes it was a bit confusing at first use but now I see it takes a bit to get use to. Thanks all for the inputs. I believe this discussion can be closed now.
Thanks,
Gary T