A custom hatch is in a dwg from a external user, can not use that hatch again.
As per the title have not had this problem till now. I have a dwg it has a custom hatch that has been used and can be seen and identified in the dwg. Properties tells me it is Predefined/patternname.
If I try to hatch another object it errors with can not use that pattern. Yes I understand if I was to make the missing pattern then I could use it. But the issue here is that I am looking at some one else's dwg. I am surprised that the pattern is not available, given I can see and touch it. It is in response to another post about a lisp program to draw hatched rectangs.
Anybody had this issue or have any ideas how to use an existing custom hatch. When you do not have the Pat file.
Comments
-
It could be that the problem hatch is a proxy object. BricsCAD has enough information to show the graphic object (does it print OK?), but not reuse it.
0 -
The hatch is in a block, so can insert and works fine. have exploded. But if I try to just "HATCH" an object I can not use that hatch pattern. In the hatch dialog it has option "Inherent Properties" but this errors on the custom pattern. It just looks like only way is actually add the missing pat file. I may put forward a support request about this.
0 -
Not sure, how the block with a custom hatch without proper pat file can be inserted and exploded, but it's not possible to create or inherit properties of the hatch with a missing pattern definition.
0 -
Thanks @Lyubov Osina for reply, the block exists in a dwg I went to use the hatch for a different object, but I can not use that hatch pattern, I would have thought that if pattern exists in dwg then can use again. The original problem came about from a forum post about using lisp to make an object made of multiple entities including the hatch pattern. The lisp was tested using known default patterns and works. If using a dwt then maybe the hatch should be available.
0 -
Unfortunately, hatches depend on external source - pattern definitions, which can be included to the default *.pat files or custom *.pat files.
0
