Help with custom .PAT file
Elaborate a bit more on it please: for example, are you needing this exact perfection in layout/display, and is that rectangle the only size?
And any reason why a BLOCK of all of that would not do well for you instead?
A Hatch pattern needs to be inherently repetitive. If it's even possible [however extraordinarily complicated] to define a pattern involving all the bits making up the letters in those words, then if there's a "word" a certain distance up and to the right of, say, the one at lower left in your example, then there would be another one up and to the right of that by the same distance, etc. Applying it in a boundary like yours would surely result in something like this:
So I don't think a Hatch pattern is what you want.
Is the idea that no matter the size of the boundary, the text pieces would be of the same size and spacing and displacement angle? If the proportions of the boundary are always the same, and if the text size can change to go along with the boundary size, then a Block would work, but I assume that's not your situation. Show some examples of what you're looking for at different boundary sizes. If it's twice as big, do you still want 5 words? Arranged similarly in relation to the boundary (e.g. same distances inboard, but spread out more -- another impossibility with a Hatch pattern)? Etc.
Can you use SUPERHATCH? These were done with it:
using a Block that looks like this:
without the dashed grey outline -- that's a 40-unit square used for spacing. I used TXTEXP to get the incomplete words Trimmable to meet the square's edges.
But that depends, again, on whether you want the words the same size and spacing no matter what the boundary size.
Late to the party but HatchKit can create hatchpatterns containing text directly from default Roman Simplex or other resident SHX fonts within an existing pattern or by this Quickfill wizard:
Text string size, spacing and orientation can be adjusted.
Resulting pattern attached.
Hugh Adamson
@Travis.Biddle wrote:
When trying to use the hatch ... I get "Error in Pattern File"
It works for me. If you happened to not use the posted file itself, but copied the definition code out and pasted it into another file, and omitted the blank line that's required at the end of the file, that would make it unusable.
