AutoCAD 2023: A lisp file that can identify the Non-ISO hatch pattern and linetype with their measurement settings at time of creation,

[JamaL9722060]

AutoCAD 2023: A lisp file that can identify the Non-ISO hatch pattern and linetype with their measurement settings at time of creation,

I’m not sure if it’s applicable to have a lisp file that can identify the Non-ISO hatch pattern and linetype with their measurement settings at time of creation. This should eliminate the confusion of having identical properties for hatches\lines but with different output\presentation in the screen.

For example, in the screenshots below, the hatches are identical in terms of properties, however, their presentation in the screen is not. Then, there should be other settings\properties that need to be identified to resolve the trick

the dwg are files attached

[cadffm]

Hi,

yes it is possible. 

The only need is to inform the program what definition is the original ISO one.

For AutoCAD Standard definitiobs it is easy, the original are all in acadiso.pat and acadiso.lin

But I don't know such a tool to buy or for free (i use my own)

EDIT: Attached a sample drawing (the merged and edited the S1+S2.dwg content)

And a gif to show how such a program can work

0. Works only for hatchs which are "known" (also with custom patterns, but you need the *.pat defintions)

1. Function, it's just to detect and select non-ISO Hatchs

2. Function is the same, but include redefining the hatchdata to ISO definition and change of the scale,

so it looks like before, but now it is the ISO defintion with the scale you need that the hatch shows like before.

[JamaL9722060]

Thank you for the input

What I wanted here is just to identify hatches or line of non-ISO pattern\type along with their measurement settings at creation so that they can be fixed. I would appreciate if you could share such lisp file

[cadffm]

>>"What I wanted here is just to identify hatches or line of non-ISO pattern\type"

That's what it shows first

>>"so that they can be fixed."

That's what it shows as second. Identify&fix, both by one click.

>>"I would appreciate if you could share such lisp file"

Normally not (but I wrote a PM to you)

[JamaL9722060]

I’m again here with same issue: same properties with different output in the screen

How this ever-existing issue can be resolved?

The dwg file is attached

[cadffm]

Hi,

1. The Q55.dwg doesn't match your screenshot situation,  😕

   This is what we can see and what should the same on your side:

And this matchs the current setting (metric definitions, ansi31, scale 1), all fine!

But your pictures shows a hatch on the right created with the imperial definition of Ansi31

so you COPIED this hatch from another file - and if this file is setup well,

it is a file with imperial units und Measurement =0 .

(25.4 is the right scale to match metric defintions of Ansi31, scale 1)

2. >>"How this ever-existing issue"

     Don't mix imperial and metric content (except a sBlock or Xref)

3. >>"How this ....can be resolved?"

   -For new files, - easy!

     Take the right template (Measurement is set well and matchs the Insunits setting what you want to use)

     You want imperial units, take a template for imperial (measirement is set to 0)

     You want metric units, take a template for metric (measirement is set to 1)

    And from here: Consider point 2)

   -For existing files where all is okay:

     check the insunits setting, is it matching the drawing scale of the content? and does Measurement set well?

     Okay, now we can guess that all is fine, or we can double check it:

     Create a new Hatch/Line(type) as present, with the same property settings and compare: Looks same?

     In this case all is set and created well.

   -For existing files with problems:

    Impossible to describe it in few sentence - because there are too many combinations of issue and possible targets.

[JamaL9722060]

The dwg file does match the screenshots

I would appreciate if you could have a look on the attached video. It shows that the hatch disappears in its own as the file is closed and reopen

However, I need to confirm that the properties pane needs to include two more properties to avoid this very ever perplexing issue:

• Whether the hatch is ISO or Imperial
• The measurement system variable (0 or 1)

The dwg file is attached

[cadffm]

---

@JamaL9722060  schrieb:

>>"The dwg file does match the screenshots"

No, The Q55.dwg doesn't contain the hatch one ther right and the hatch on the left have another scale, so it isn't matching (or you forgot to explain what we can see and have to do with the file).

Your new file Q55_2.dwg is the right one.

>>"I would appreciate if you could have a look on the attached video. It shows that the hatch disappears in its own as the file is closed and reopen"

Yes, because your hatch scale is much to hight and no pattern lines are inside your boundary.

The hatch is present, but your boundary showing just a blank part of your hatch = User created problem.

Note: Iff you change the properties from a well displaying hatch to a hatch with no pattern line inside your boundary,

AutoCAD displaying the pattern as Solid. This is the moment you can see: Your fail, time to change something.

Afters save,close&re-open the hatch pattern displaying the correct way: NO line is visible.

>>"However, I need to confirm that the properties pane needs to include two more properties to avoid this very ever perplexing issue:"

• "Whether the hatch is ISO or Imperial"

       You forgot that there are unlimited number of definitions, so you need three states: Imperial,Metric and Unknown.

• "The measurement system variable (0 or 1)"

     The point would have already been answered with the previous one and there are hatchings that have nothing to do with it.
Also, it can be different for everyone! One must not forget this point either.

---

[JamaL9722060]

Thank you very much Sebastian for the elaboration.

• Correct. The dwg file I attached in my first post is different from the one that I was supposed to attach
• Getting the hatch visible before closing the file and having it disappeared when reopen it adds more confusion to the scene!

[cadffm]

>>"Getting the hatch visible before closing the file and having it disappeared when reopen it adds more confusion to the scene!"

For years, the alternative was the direct, technically correct display:
Hatching disappears immediately if you use the wrong properties,
in that case, users have not understood that the hatching still exists
and the hatch could not be selected with the mouse to correct the properties.

My Opinion: Even if it's not perfect - It's much better than it was in the past.

[JamaL9722060]

Thank you

Hatch is full of tricks and secrets!