Match prop won't match prop

[Anonymous]

Anyone have an idea as to why I can't use the match properties command on a
hatch? I've tested it on three different machines and it works on all of
them. Just not this one particular machine.


--
Jerry Logan
CAD Manager
Baker + Hogan + Houx Architecture

[Anonymous]

On that machine, start the match properties command, select an object, then type S (for Settings) and enter. Is the Hatch toggle in the Special Properties area at the bottom checked? If not, check it and it should work for hatches.

--

David Koch

[Anonymous]

That was a good one but not it.

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

On that machine, start the match properties command, select an object,
then type S (for Settings) and enter. Is the Hatch toggle in the Special
Properties area at the bottom checked? If not, check it and it should work for
hatches.

David Koch

[Anonymous]

Here is an even less likely cause: are you using the same "source" hatch for your tests on all three machines? A hatch originally created in a sufficiently old drawing (I forget which version) will not have the hatch pattern and other data stored with it, so it will not be able to be copied (or serve as the source for an inherit properties attempt from the Boundary Hatch dialog).

--

David Koch

[Anonymous]

David,

That didn't do the trick either. That was
pretty obscure. I'm still looking for an answer if anyone has
one.

Thanks David keep em coming

style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">Here
is an even less likely cause: are you using the same "source" hatch for your
tests on all three machines? A hatch originally created in a sufficiently old
drawing (I forget which version) will not have the hatch pattern and other
data stored with it, so it will not be able to be copied (or serve as the
source for an inherit properties attempt from the Boundary Hatch dialog).

David Koch

[Anonymous]

The only thing I can think of is that the pattern you are trying to copy is
not defined in the hatch pattern definitions on the machine you are having
trouble with. I think this happened here last week, I had a guy who could
see the solid hatch pattern that someone else did in a dwg, but could not
duplicate it (I think, hard to remember now) Anyway, I just updated his
hatch file, who knows why it left in the first place.

[Anonymous]

Any chance the hatch you want to match is actually exploded? Sorry if it
seems really dumb to ask but it's happened before....

Steve


"Jerry Logan" wrote in message
news:4A7DB98495F70830E6DE6164AB78F230@in.WebX.maYIadrTaRb...
David,

That didn't do the trick either. That was pretty obscure. I'm still looking
for an answer if anyone has one.

Thanks David keep em coming
Here is an even less likely cause: are you using the same "source" hatch for
your tests on all three machines? A hatch originally created in a
sufficiently old drawing (I forget which version) will not have the hatch
pattern and other data stored with it, so it will not be able to be copied
(or serve as the source for an inherit properties attempt from the Boundary
Hatch dialog).
David Koch

[Anonymous]

We just had this problem also.  In our case
the hatch pattern was not available to the computer in question.

The hatch pattern file is on the server and the
problem machine was not pathed to that location in the support file search
paths.

--
Greg Kenner
CADD Manager
LS3P Associates Ltd.
Charleston
SC

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

"Jerry Logan" <cad@bhharchitecture> wrote in message
href="news:4A7DB98495F70830E6DE6164AB78F230@in.WebX.maYIadrTaRb">news:4A7DB98495F70830E6DE6164AB7......

David,

That didn't do the trick either. That was
pretty obscure. I'm still looking for an answer if anyone has
one.

Thanks David keep em coming

style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">Here
is an even less likely cause: are you using the same "source" hatch for your
tests on all three machines? A hatch originally created in a sufficiently
old drawing (I forget which version) will not have the hatch pattern and
other data stored with it, so it will not be able to be copied (or serve as
the source for an inherit properties attempt from the Boundary Hatch
dialog).

David Koch

[Anonymous]

That sounds promising....probably solve it for him too.



"juslookin" wrote in message
news:1090C68539E559601EF502E1C1BD9AAD@in.WebX.maYIadrTaRb...
We just had this problem also. In our case the hatch pattern was not
available to the computer in question.
The hatch pattern file is on the server and the problem machine was not
pathed to that location in the support file search paths.

--
Greg Kenner
CADD Manager
LS3P Associates Ltd.
Charleston SC
"Jerry Logan" wrote in message
news:4A7DB98495F70830E6DE6164AB78F230@in.WebX.maYIadrTaRb...
David,

That didn't do the trick either. That was pretty obscure. I'm still looking
for an answer if anyone has one.

Thanks David keep em coming
Here is an even less likely cause: are you using the same "source" hatch for
your tests on all three machines? A hatch originally created in a
sufficiently old drawing (I forget which version) will not have the hatch
pattern and other data stored with it, so it will not be able to be copied
(or serve as the source for an inherit properties attempt from the Boundary
Hatch dialog).
David Koch

[Anonymous]

Learning new things every day.... If a source PAT file can not be found, then neither the MATCHPROP nor the BHATCH Inherit Properties commands will work (based on a limited experiment using only hatches defined in ACAD.pat). The BHATCH command will bark at you, with warning dialogs saying ACAD.pat was not found, but the MATCHPROP will not. (As a side note, the associativity state of the hatch is not copied, in either direction.)

Curiously, hatch entities (at least ones created in AutoCAD 2002) contain the hatch pattern definition information inside them (DXF Group Codes 53, 43, 44, 45, 46, 79, 49). The values are multiplied by the scale factor used to place the hatch, and the angles are in radians. So the data is there even if the PAT file is not (it would need to be for associative hatches to regenerate, which does work in the absence of the PAT file), but the BHATCH and MATCHPROP commands are too lazy to extract it.

--

David Koch

[Anonymous]

The pathetic things is WHY does it need a hatch pattern file. The hatch
pattern is defined in the object with the hatch or database...I can't
remember since I don't go there.
If anyone is looking for a program to extract a hatch pattern from a object
I think that was one posted in the Customization NG. You will need to do a
search...for what I don't know.

Good luck.

--
| Rob Starz
------------------------------------------------------
| president / dreamer
| Stardsign cad solutions
| 352.263.3786
| AEC Designer / Consultant / Developer
| Autodesk Architectural Desktop:
Tools: www.stardsign.com
Tech Support: www.stardsign.com/support.htm
Bring the Power of i-drop into AutoCAD with i-dock (coming soon)

[Anonymous]

And the winner Issssss. Greg hit the nail on the
head. I could have sworn two weeks ago I set the guy up with the right paths for
this very reason. He moved to another station and I forgot that I switched out
his puter as well.

Thanks for the help guys.

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

The hatch pattern file is on the server and the
problem machine was not pathed to that location in the support file search
paths.