Hatch associativity a problem with xrefs

[terencechatfield]

I was going to say, (before i hit return and posted this query), that my office is finding rather a problem with the associativity of hatch objects, particularly when they are created using xrefs as the boundary. Iknow that is a problem and have seen similar query posted elsewhere, but it does not answer the question of, why?

The only way around it i have sfound so far, short of making the hatch non-associative, is to detach the xref and then attach it again, which removes the associativity. But this is rather a pain to have to do on maybe a few hundred drawings all of which have to go out sooner rather than later.

Has anyone found a way of setting the hatch to default to non-associative, given that it defaults every time to doing it?

[Anonymous]

Hi,

Yes, this is a known problem that can result in
corrupted drawings. The key is to not use the xref as your boundary. To hatch an
area use a polyline and select the polyline as your hatch boundary. Sometimes
Bpoly is a real timesaver here. Using this method will allow your hatches to
remain associative.

Hope that helps,

Dennis McNeal, AIA
Autodesk
Building Industry Division

style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">

"terencechatfield" <
href="mailto:terencechatfield@yahoo.com">terencechatfield@yahoo.com>
wrote in message
href="news:f0af7a3.0@WebX.maYIadrTaRb">news:f0af7a3.0@WebX.maYIadrTaRb...

I
was going to say, (before i hit return and posted this query), that my office
is finding rather a problem with the associativity of hatch objects,
particularly when they are created using xrefs as the boundary. Iknow that is
a problem and have seen similar query posted elsewhere, but it does not answer
the question of, why?

The only way around it i have sfound so far, short of making the hatch
non-associative, is to detach the xref and then attach it again, which removes
the associativity. But this is rather a pain to have to do on maybe a few
hundred drawings all of which have to go out sooner rather than later.

Has anyone found a way of setting the hatch to default to non-associative,
given that it defaults every time to doing it?

[Anonymous]

You should be able to change the hatch to non-assosiative. Properties
or edit hatch either one should allow you to do this.

terencechatfield wrote:

> I was going to say, (before i hit return and posted this query), that
> my office is finding rather a problem with the associativity of hatch
> objects, particularly when they are created using xrefs as the
> boundary. Iknow that is a problem and have seen similar query posted
> elsewhere, but it does not answer the question of, why?
>
> The only way around it i have sfound so far, short of making the hatch
> non-associative, is to detach the xref and then attach it again, which
> removes the associativity. But this is rather a pain to have to do on
> maybe a few hundred drawings all of which have to go out sooner rather
> than later.
>
> Has anyone found a way of setting the hatch to default to
> non-associative, given that it defaults every time to doing it?

[Anonymous]

I think the question was where can the default be changed so the Assoc.
Hatch isn't toggled on. I searched through the registry and I don't see this
value stored and it makes sense because it doesn't remember the last setting
you did.

You will have to check it off each time or change the hatch's Assoc prop in
the properties dialog.

--
|
-+-------------------------------------------------
| Rob Starz
| Stardsign cad solutions
| AEC Designer / Consultant / Developer
| iC - AEC Information Center
| www.stardsign.com/aecic.html
| "can we make it any easier?!"

[Anonymous]

Rob's right. The heart of the question is where the variable is stored &
how to change the default....

[Anonymous]

the answer is you are SOL...no way to control this.

--
|
-+-------------------------------------------------
| Rob Starz
| Stardsign cad solutions
| AEC Designer / Consultant / Developer
| iC - AEC Information Center
| www.stardsign.com/aecic.html
| "can we make it any easier?!"

[Anonymous]

Except... you could use just the generic no frills HATCH command. It
defaults to non-associative.

Rob Starz wrote:

> the answer is you are SOL...no way to control this.
>
> --
> |
> -+-------------------------------------------------
> | Rob Starz
> | Stardsign cad solutions
> | AEC Designer / Consultant / Developer
> | iC - AEC Information Center
> | www.stardsign.com/aecic.html
> | "can we make it any easier?!"

[terencechatfield]

You've got it in one Rob. Looks like the slow way again.

Either that or redefine the HATCH command, to include a routine running straight after the hatch is created turning to non-associative.

I take it (using LISP) that would be using the ENTLAST function? Though i have seen somewhere that using LISP to amend dxf settings is a bit dodgy in that the codes can change between versions, with grief the end result. Is ActiveX combine with LISP a safer route to take?

The reason im asking is it might be faster for me to write the routine and slip it into out office custom .mnl file than to have to try and explain the problem to the other 80 people i work with, and then teach them the various ways around it.