The following solution is hacky work-around to overcome the lack of proper pattern directives. I don't like it 100%, but still it is usable.
Solution
The idea is simple. If you see FilledCurve
documentation, it supports an object with holes:
So what if you put a huge enough rectangle as an outer boundary? Then, your polygon becomes a hole and you can see through stuff behind it.
Now, few issues:
How big the boundary should be? Ideally, it should be always outside of the screen. Thankfully, it is possible by using ImageScaled
coordinates, which is supported by all 2D primitives.
Now your background color of the screen should be the face color of the outer polygon.
The hatch (pattern) should come first so that the outer polygon would be drawn on top of it.
This is the result.
Graphics[{
(* The hatch comes first *)
Sequence@
Table[Inset[Graphics[Line[{{0, 0}, {1, 1}}]], {0, 0.1 l}, {0, 0},
Scaled[{1, 1}]], {l, -10, 10}],
(* FaceForm color should be your "background" color: usually white *)
FaceForm[White], EdgeForm[Black],
(* FilledCurve syntax is essentially the same as Polygon if used with Line *)
FilledCurve[{
(* Large outer boundary. Its edges are always outside of your screen *)
{
Line[{ImageScaled[{-2, -2}],ImageScaled[{2, -2}],
ImageScaled[{2, 2}],ImageScaled[{-2, 2}]}]
},
(* Your original polygon *)
{
Line[{{0, 0}, {1, 0}, {1, 1}, {0.5, 1.5}, {0, 1}}]
}
}]
}]
Here is the result:
Generalization
The following example uses two different types of patterns (an image and a graphic), and locate them in two different places.
Graphics[{
(* Pattern for the first object *)
Inset[ExampleData[{"ColorTexture", "MultiSpiralsPattern"}],
{-.25, -.25}, {Left, Bottom}, {1.5, 1.5}],
(* Pattern for the second object *)
Inset[Graphics[Table[Circle[{i, j}, .25], {i, 10}, {j, 15}]],
{1.5, 0}, {Left, Bottom}, {1, 1.5}],
FaceForm[White], EdgeForm[Black],
FilledCurve[{
(* Outer polygon *)
{Line[{ImageScaled[{-2, 2}], ImageScaled[{2, -2}],
ImageScaled[{2, 2}], ImageScaled[{-2, 2}]}]},
(* The first object *)
{Line[Table[(.5 + .25 (-1)^t) {Cos[Pi t/5],
Sin[Pi t/5]} + {.5, .5}, {t, 0, 9}]]},
(* The second object *)
{Line[{{1.5, 0}, {2.5, 0}, {2.5, 1}, {2, 1.5}, {1.5, 1}}]}
}]
}]
Here is the result:
Pros & Cons
The benefits of this approach is:
You need to convert your polygon to inequalities to use RegionPlot
or any other solutions using Plot
with RegionFunction
which is not always possible (such as country polygons).
Anything can be a pattern as long as it is behind the polygon.
The syntax is straightforward, as long as you stays in Polygon
or even better FilledCurve
. You just have to add one extra component.
The problems:
It is tricky to handle many objects with different patterns, especially if your object contains a concave part.
Circle support is hard. In fact, circles can be described as B-splines (See the first example of Applications section), but combining it with the rest of FilledCurve
can be messy.
In fact, if you are familiar with Mac OS's graphics API (Quartz or Cocoa), this is exactly how they deal with filled polygons with patterns (link). It would have been a nice addition to Mathematica's graphics if it were built-in.
As a side note, FilledCurve
syntax is quite complex, but if you want nice graphics, it is well-worth learning. It follows the concept of path in many other graphics languages (Postscript, SVG, or system APIs) and conversion to it is usually straightforward.
AbsoluteOptions
to obtain thePlotRange
of interest of the polygon (without the insets). Then, when you plot the polygon plus insets, you can use the samePlotRange
. $\endgroup$PlotRange
withGraphics
, and that allows you to get rid of the white space. Maybe that's what @David already hinted at above... so you could add e.g.PlotRange -> {{-.1, 1.5}, {-.1, 1.5}}
. $\endgroup$AbsoluteOptions[g, PlotRange]
you can obtain the neededPlotRange
. (My answer illustrates how this is used.) $\endgroup$Inset
. Then the white-space problem would likely be fixed too. $\endgroup$Inset
was used. $\endgroup$