Views Not Cropping Matchlines in dependent views

[Anonymous]

Is there a way for you to make Matchlines react to cropped dependent views? we are having issues getting them to cooperate across multiple views due to this not working.

We are having to "notch" out our crop regions in some views for legends and such and the annotation crop is not mimicking our cropped view causing the Matchlines to continue to show up through the Annotation crop region and hence show up through our legends etc.

Thank you for any assistance.

[joe_keogh]

Hi @Anonymous 

I would expect to see a matchline parallel to the crop, as opposed to perpendicular?

As in "FOR CONTINUATION OF PLAN, REFER TO A01.02", What is your Matchline referencing?

[ToanDN]

Matchlines extend to the View's annotation crop.  So adjust the annotation crop if needs be.

[Anonymous]

this is just an example, we have a VERY large building, so we have matchlines going horizontally and vertically.

[Anonymous]

we do that as well, the problem is that we cannot adjust just parts of an annotation crop. we need it to be where it is in other places.

[Martijn.Pater]

...I guess use several matchlines (or have the sketch follow the crop boundary)?

[Martijn.Pater]

...or maybe edit the matchline and remove part of the line where its extending the cropregion?

[ToanDN]

---

@Anonymous wrote:

we do that as well, the problem is that we cannot adjust just parts of an annotation crop. we need it to be where it is in other places.

---

Then you need to create multiple match lines, terminate them where you want to break, and manually hide in dependent views.

[Martijn.Pater]

hmm I was thinking something more like this... but then again I may have misunderstood the screenshot. edit: I guess the above makes more sense actually^^

[Anonymous]

Yeah, i know about this already, i was trying to find an easier less time consuming fix that doesn't add elements to a project that is already bogged down because of how large it is.

[ToanDN]

---

@Anonymous wrote:
Yeah, i know about this already, i was trying to find an easier less time consuming fix that doesn't add elements to a project that is already bogged down because of how large it is.

---

Would have been nice if you could tell us you knew about that already so we needed not to bother you with a redundant workaround.

[Anonymous]

Sorry

[RDAOU]

who is complaining about redundancy 🙂 this whole forum is full of it ... one extra redundant reply won't really matter

@Anonymous 

Talking about redundancy, I'm sad to tell you that there isn't really any easier way/workaround for this ... you will have to suffer the extra clicks or if your clients are not really that picky just live with it as it is until Autodesk modifies the annotation vs view's crop behavior. There was an idea posted on the Idea forum but wasn't popular to get enough votes.

[Anonymous]

yeah, that seems to be the case. I found a temporary workaround using a mask that is less cumbersome but still not ideal.

[ToanDN]

---

@Anonymous wrote:

yeah, that seems to be the case. I found a temporary workaround using a mask that is less cumbersome but still not ideal.

---

A mask?  How?  I thought masking regions couldn't cover annotation objects including match lines.

[Martijn.Pater]

@ToanDN (almost white) text? (...as in, I don't know what he means aswell)

[Anonymous · Accepted solution]

I found it in another forum. its called an Uber mask by them, i changed the name for my own filing purposes. But i attached it.

[Anonymous]

this one can cover annotations and the like as well. its slightly cumbersome to use, but it works for my purposes and doesn't require the tedious work of have a ton of matchlines and shortening and lengthening and hiding etc.

[ToanDN]

Interesting.  Thanks for sharing.

[Martijn.Pater]

Annotation masking region! close enough guess I suppose^^ Quite a nice method though. You should mark your own answer as solution to this particular question...