Skip to contents

Changelog

Source: NEWS.md

gridpattern v1.6.0 (development)

Breaking Changes

  • A length-one NaN value of any pattern parameter is now treated as unset so pattern-specific (or else generic) defaults apply (a parameter without any default is then NULL i.e. the same as if it wasn’t supplied so new ggpattern aesthetics and new defaults don’t change what a NaN means). This is the new ggpattern default for its aesthetics that should fall back to the pattern’s defaults (e.g. the “wave” frequency of 1 / spacing, the “regular_polygon” scale 0.5, the “text” shape "X", and the “crosshatch” / “weave” pattern_fill2 of pattern_fill). An NA value keeps its meaning (e.g. a transparent colour or a “pch” shape that draws nothing) except for pattern_type, pattern_subtype, pattern_gravity, and pattern_res for which a length-one NA is still also treated as unset.
  • The default shape of grid.pattern_regular_polygon() (and the registered default pattern_shape of the “regular_polygon” pattern) is now "convex6" (hexagons) instead of "convex4" (matching the previous ggpattern default). Use shape = "convex4" to restore the previous appearance.
  • The default fill of grid.pattern_magick() is now gp$fill %||% "grey80" (previously "grey20" ignoring gp$fill) matching the generic default pattern_fill that patternGrob() / ggpattern already used for the “magick” pattern. Use fill = "grey20" to restore the previous appearance.
  • The default linewidth (when none of linewidth, size, nor gp$lwd is given) is now 0.5 (matching ggpattern) instead of 1 for both patternGrob() and the grid.pattern_<name>() functions so default lines are now half as thick. The generic default of pattern_size is likewise now gp$lwd %||% 0.5.
  • The spare ggpattern aesthetics pattern_phase and pattern_option_1 - pattern_option_5 (which no builtin pattern uses) now have a generic default of 0 (the default ggpattern already used for them). A custom pattern drawn by patternGrob() that used params$pattern_option_1 %||% my_default (or checked is.null(params$pattern_phase)) to pick its own default when unset now always gets 0 and should instead register its defaults with register_pattern(defaults = ).
  • The default resolution pattern_res (res argument) of array patterns, the “gradient” pattern, and the raster fallbacks of alphaMaskGrob() and clippingPathGrob() (if the package option ggpattern_res is unset) is now computed when drawn from the resolution of the graphics device instead of being 72 pixels per inch: 1.14 times the device resolution (e.g. about 82 on pdf() / svg() devices and 342 on a 300 ppi png()). This is sharper on high resolution devices but uses more memory and time. A numeric legend key’s default resolution is 1.3 * legend * pattern_key_scale_factor times the device resolution so array patterns in legend keys resemble those in the (larger) plot panels. These match the resolutions ggpattern (<= 1.3.1) computed itself. The res argument of the grid.pattern_<name>() functions, alphaMaskGrob(), and clippingPathGrob() now defaults to NULL (unset).
  • Now declares a dependency on R (>= 4.1.0) (previously declared R (>= 3.4.0)).
  • pattern_units (units argument) may no longer be “npc”, “native”, nor “null” (now an error, #115). Pattern lengths (e.g. pattern_spacing, pattern_xoffset, and pattern_yoffset) were always converted along the viewport’s width so “npc” and “native” ignored the viewport’s height (even for vertical offsets) and “null” lengths are zero (which threw an obscure error). Use “snpc” (the default) for lengths relative to the viewport or an absolute unit such as “cm” or “in”.

New features

  • The legend argument of patternGrob() / grid.pattern() may now be a non-negative number s to draw a legend key showing (the centre of) the pattern as it would be drawn in an area s times the width and height of the key (TRUE is equivalent to 1 and FALSE to 0). The pattern is drawn in a centred viewport s times larger than the key so all relative lengths (e.g. “snpc” spacings, offsets, and wave amplitudes, including those of custom patterns) scale together while absolute lengths (e.g. line widths, font sizes, “cm” units, and array pixels) don’t. The pattern functions themselves are still passed a logical legend value. ggpattern now uses this to scale its legend keys instead of rescaling pattern_spacing, pattern_xoffset, and pattern_yoffset itself.
  • A numeric legend key is now zoomed by the pattern_key_scale_factor parameter (key_scale_factor argument): the legend viewport is legend * pattern_key_scale_factor times larger than the key and if pattern_units isn’t “snpc” then pattern_spacing, pattern_xoffset, and pattern_yoffset are multiplied by pattern_key_scale_factor (before any defaults computed from them e.g. the “wave” amplitude) so legend keys of patterns with absolute units (e.g. “cm”) can be zoomed too. A logical legend (as passed by ggpattern 1.3.1 and earlier, which zoom their keys themselves) is not zoomed by pattern_key_scale_factor. Previously only the “magick” pattern used pattern_key_scale_factor (which it still does for any legend key).
  • prefer_pattern()’s new must_exist argument controls what happens if a preferred pattern isn’t (yet) registered: NA (the default) warns, TRUE errors, and FALSE neither warns nor loads the pattern’s package (useful in an .Rprofile). It likewise controls what happens if the user has more than one pattern with that name (via the legacy ggpattern_geometry_funcs / ggpattern_array_funcs options). Previously preferring a pattern that wasn’t registered was always an error.
  • local_prefer_pattern() sets pattern preferences until the current function (or test) exits and then restores any previous preferences (#113).
  • local_pattern()’s new prefer argument also prefers the registered pattern until the current function (or test) exits if TRUE.
  • has_registered_pattern() returns whether a pattern name is taken (even if it doesn’t resolve e.g. because of a conflict) i.e. whether registering a pattern with that name would clobber or conflict with a pre-existing pattern.

Bug fixes and minor improvements

  • registered_patterns() and conflicting_patterns() no longer load the package of a preferred pattern (previously the first call omitted that package’s patterns and listed no pattern with that name as active).

  • A qualified pattern name "pkg::name" no longer resolves to a stale registration left behind by a {pkg} that was unloaded and can no longer be loaded (e.g. because it was removed) so has_pattern() now returns FALSE and prefer_pattern(must_exist = TRUE) now errors for it.

  • The raster fallbacks of alphaMaskGrob() and clippingPathGrob() (used by the “hatch”, “line”, “rose”, and “text” patterns when masks / clipping paths aren’t supported by the graphics device) now only rasterise the (pixel-snapped) bounding box of the masker / clipper within the viewport instead of the whole viewport (if it can be computed with grobCoords() in R 4.2+). This is much faster and uses much less memory for small boundaries in large viewports, in particular for a numeric legend (e.g. ggpattern legend keys).

  • grid::grobCoords() of a patternGrob() is now the coordinates of its boundary (without building the pattern). Previously it was the coordinates of whatever the pattern drew which was slow for some patterns, empty for array patterns (and raster fallbacks), and too large for masked patterns like “rose” and “text”.

  • Drawing patterns, alphaMaskGrob(), and clippingPathGrob() no longer call grDevices::dev.set() to restore the graphics device when the current device never changed (which needlessly triggered the device’s (de)activate callbacks e.g. window title updates for quartz()) and never call grDevices::dev.set(1L) (which would open a new device) (#120). Drawing array patterns (e.g. “image”, “magick”, “placeholder”) and the raster fallbacks of alphaMaskGrob() and clippingPathGrob() now restore the previous graphics device before closing their temporary devices (so no unrelated device briefly becomes the current device) and the raster fallbacks now also close their temporary devices if there is an error while drawing.

  • The “hatch” pattern types drawn by other patterns (e.g. “or” circles, “olive”, “proper” waves, Goodman “steel” and “copper”, and Unicode “cendree” checkers) now pass on pattern_units, pattern_xoffset, and pattern_yoffset. Previously their spacing was always interpreted as “snpc” units (while their density was computed from the spacing in pattern_units units) and their offsets were ignored.

  • The builtin patterns’ registered defaults now agree with the defaults of their grid.pattern_<name>() functions (so patternGrob() / ggpattern and grid.pattern_<name>() render the same when a parameter is unset):

  • The “seagal” and “seagalbw” placeholder types work again (their URLs used a nonexistent www. subdomain of stevensegallery.lucidinternets.com, #118).

  • Placeholder types that return greyscale images (e.g. “murray”, “murraybw”, “picsumbw”, and “seagalbw”) no longer throw an error (their single channel images weren’t promoted to RGBA arrays).

  • An unknown placeholder type now actually falls back to the “bear” placeholder (as its warning claims) instead of a “dummy” placeholder image. A placeholder type that isn’t length one now also falls back to “bear” (the default type) instead of “kitten”.

gridpattern v1.5.1

CRAN release: 2026-10-28

Breaking Changes

  • Custom patterns are no longer given generic default values for the pattern_amplitude parameter nor for the ambient noise parameters (pattern_fractal, pattern_octaves, etc.). These are now pattern-specific defaults of the builtin “wave” and “ambient” patterns. A custom pattern that reads them should now set its own defaults with register_pattern()’s defaults argument. The generic defaults for pattern_frequency and pattern_gravity are now the constants 0.1 and "center" (matching ggpattern) instead of 1 / pattern_spacing and a function of pattern_type; the “wave”, “ambient”, and “image” patterns override them. pattern_subtype now has a generic default of NA (matching ggpattern) and like pattern_type and pattern_gravity an NA value is treated as unset so pattern-specific defaults apply. An NA pattern_res is also treated as unset (previously an obscure error).

New Features

  • register_pattern() is now the recommended way for packages to register patterns (in their .onLoad() function, ideally wrapped in rlang::on_package_load()) instead of setting the ggpattern_geometry_funcs / ggpattern_array_funcs global options which may clobber other registrations (#108).

    • Patterns are owned by either the package that registered them or the user.
    • register_pattern()’s defaults argument sets pattern-specific default parameter values (constants or functions of the other parameters, named e.g. pattern_spacing or fill; unprefixed names are an error unless declared in the unprefixed argument). The builtin patterns now use this to register their pattern-specific defaults.
    • patternGrob() caches the pattern resolved when the grob is created so redraws (e.g. resizing an interactive device) still work if the pattern is later unregistered or masked.
    • Package patterns (including builtins) may be referred to by their qualified name e.g. "gridpattern::stripe" or "pkg::name".

  • unregister_pattern() can be used to unregister a pattern.

  • prefer_pattern("owner::name") sets preferences and unprefer_pattern(name) removes them (both are vectorized and return the previous preferences so they can be restored). Bare pattern names resolve to the pattern preferred by prefer_pattern() (if any) and otherwise to the pattern of the only owner (the user, gridpattern, or a package) with that name. If more than one owner has a pattern with that name there is a conflict and an error asks for either a qualified name or a prefer_pattern() preference (similar to the conflicted package).

  • conflicting_patterns() lists patterns whose bare names are shared by more than one pattern

  • has_pattern() returns whether a pattern name resolves to a pattern.

  • local_pattern() registers a pattern until the current function (or test) exits and then restores any previous registration (useful in tests and examples).

Bug fixes and minor improvements

  • Fixes a bug where the “hatch” pattern failed when pattern_subtype was NA (the ggpattern default) instead of NULL (#106).
  • Patterns set via the global options may now share a name with a builtin pattern (resolved with prefer_pattern()) instead of always throwing an error.
  • Name clashes between patterns now only throw an error when the conflicted pattern name is used rather than for every pattern.

gridpattern v1.4.2

CRAN release: 2026-06-23

Breaking Changes

  • The "indented" (formerly "triangle") wave type now uses a wider stroke in order to better match the apparent stroke widths of the new wave types. Users who relied on the previous visual appearance should reduce density to compensate.

New Features

  • New “hatch” pattern with corresponding grid.pattern_hatch() and names_hatch() (#97).

  • New “line” pattern with corresponding grid.pattern_line(). Unlike the “stripe” pattern which fills bands with solid colour, “line” draws stroked lines using the device’s native line rendering, enabling all of R’s built-in linetype values (including "dotdash", "twodash", and custom line types specified as hex strings per ?par).

  • The preexisting “wave” pattern gains ten new type values, a reverse parameter, a stagger parameter, and names_wave (#100, #101).

  • New mix_col() that mixes colors via Munsell color space using aqp::mixMunsell(). Requires the suggested package aqp.

Bug fixes and minor improvements

  • Fixes a bug where geometry-based patterns (e.g. “stripe”, “crosshatch”, “wave”) could silently disappear in small viewports when pattern_key_scale_factor was a relatively large value (#95).

  • The following “placeholder” pattern updates (#83):

    • The following placeholder pattern names are now serviced by placecats.com

      • “kitten” and “kittenbw”

    • The following placeholder pattern names are now serviced by placehold.co

      • “placeholder” and “placeholderbw”

    • The “placeholderbw” name now provides a pure black-and-white image (i.e. no grey).

  • Fixes a bug where the "wavy" (aliases "sine", "undy") and "indented" (alias "triangle") wave types had an effective wavelength of (n-1)/n times the requested wavelength, where n is the number of wavelength-spaced grid positions spanning the viewport.

gridpattern v1.3.1

CRAN release: 2025-01-16

gridpattern v1.2.2

CRAN release: 2024-06-03

Bug fixes and minor improvements

  • grid.pattern_weave() adds the new units parameter that most other “geometry” pattern functions received in gridpattern v1.2.1.

  • The “polygon_tiling” pattern should now respect the units parameter if set to a value different from the “snpc” default (#82).

  • For the “polygon_tiling” pattern type = "18.18.3*" the size of the eighteen-sided polygons have been increased a teeny bit and this polygon tiling should look a bit cleaner.

  • The following “placeholder” pattern updates (#83):

    • The following placeholder pattern names are now serviced by lucidinternets.com:

      • “cage” and “cagebw”
      • “murray” and “murraybw”
      • “seagal” and “seagalbw”

    • The following placeholder pattern names have been removed since their associated web service no longer works:

    • The “dummybw” name now provides a pure black-and-white image (i.e. no grey).

    • Fixes a regression for the “placeholderbw” name where it redirected to the “seagal” name instead of “placeholder”.

gridpattern v1.2.1

CRAN release: 2024-05-01

Breaking Changes

  • The default type for the “placeholder” pattern is now “bear” instead of “kitten”. Explicitly set type = "kitten" to continue to use the “kitten” placeholder but note that although the “kitten” placeholder website isn’t completely down it has been buggy recently (#73).

New Features

  • patternFill() wraps patternGrob() to return a grid::pattern() fill object (#70).

  • The “geometry” patterns (e.g. “circle”, “stripe”, etc.) now allow the fill to be pattern fills (#67).

  • The “geometry” patterns (e.g. “circle”, “stripe”, etc.) now allow the new units parameter to set which grid::unit() to use for the the spacing, xoffset, and yoffset parameters (and for the “wave” pattern also the amplitude and frequency parameters) (#58). By default it will continue to be “snpc” units but can now be changed to “cm”, “in”, etc.

  • update_alpha() updates fill colour and/or pattern transparency.

    • It is a fork of ggplot2::fill_alpha() by @teunbrand.
    • It does not depend on ggplot2 or scales.
    • It does not throw an error with a length one list of a vector of multiple colours.
    • It is available as a “standalone” file. You may copy its source under the permissive MIT license into your own R package by either using usethis::use_standalone("trevorld/gridpattern", "standalone-update_alpha.R") or simply copying standalone-update_alpha.R into your R directory and adding grDevices, grid, and rlang to the Imports of your DESCRIPTION file.

  • For completeness there is now a new “fill” pattern with corresponding grid.pattern_fill() which draws a simple fill pattern.

  • For completeness there is now a grid.pattern_none() corresponding to the previously supported “none” pattern which draws nothing.

Bug fixes and minor improvements

  • The wave pattern no longer quietly and incorrectly ignores the frequency parameter. The effective wavelength of the wave pattern is now 1 / frequency instead of spacing. However frequency will continue to default to 1 / spacing.
  • clippingPathGrob() can now more efficiently compute a rasterGrob() approximation via ragg::agg_capture() and for png_device functions that support the clipping path feature such aspng(type = "cairo")(#74).
  • alphaMaskGrob() can now more efficiently compute a rasterGrob() approximation for png_device functions that support the alpha mask feature such aspng(type = "cairo")(#75).
  • alphaMaskGrob() and clippingPathGrob() now switch back to the previously open graphics device if they open and close any new graphics devices.

gridpattern v1.1.1

CRAN release: 2023-10-25

  • “text” pattern example now skipped if ran within certain graphics devices like pdf() that can’t handle the playing cards Unicode glyphs (#68).

gridpattern v1.1.0

CRAN release: 2023-10-03

New Features

Bug fixes and minor improvements

  • The function guess_has_R4.1_features() is now available as a “standalone” file. You may copy its source under the permissive MIT No Attribution (MIT-0) license into your own R package by either using usethis::use_standalone("trevorld/gridpattern", "standalone-guess_has_R4.1_features.R") or simply copying standalone-guess_has_R4.1_features.R into your R directory and adding grDevices and utils to the Imports of your DESCRIPTION file.
  • If vdiffr has been updated to at least v1.0.6 (released 2023-08-25) then guess_has_R4.1_features() should now always correctly guess R4.1 feature support for the svglite::svglite() and vdiffr:::svglite() graphics devices.

gridpattern v1.0.2

CRAN release: 2022-11-07

Bug fixes and minor improvements

  • An internal function convert_polygon_sf_to_polygon_df() will now be a bit more quiet (throw WARNINGs less often).

gridpattern v1.0.1

CRAN release: 2022-08-16

Bug fixes and minor improvements

gridpattern v0.5.3

CRAN release: 2022-03-22

Bug fixes and minor improvements

  • Fixes bug with grid.pattern_image() with type = "tile" (#47). Additionally grid.pattern_image() now supports gravity argument when type = "tile".

  • If the active graphics device has also implemented the new R 4.2 dev.capabilities() support then guess_has_R4.1_features() can now better guess R 4.1 graphic feature support when called within R 4.2.

    • In particular guess_has_R4.1_features() can now better guess R 4.1 graphic feature support in the {grDevices} bitmap devices (i.e. bmp(), jpeg(), png(), tiff()) when called within R 4.2 on Windows. Previously it was not possible to easily distinguish on Windows if the device was called with type = "windows" or type = "cairo" and hence we had to conservatively guess no such support even if type = "cairo" had been specified (and within R 4.1 we must still conservatively do so).
    • Also if in the future any graphic devices add R 4.1 graphic feature support as well as R 4.2 dev.capabilities() support then we should now be able to correctly guess such support within R 4.2 without needing to manually update guess_has_R4.1_features().

  • guess_has_R4.1_features() now supports an argument features which allows one to limit the guessing of R4.1 feature support to a subset of c("clippingPaths", "gradients", "masks", "patterns"). Although all known graphic devices either implements all or none of these features this need not hold true in the future.

gridpattern v0.5.1

CRAN release: 2022-02-16

Breaking Changes

  • grid.pattern_rose() and grid.pattern_text() now “clip” their boundary using an “alpha mask” rather than a “clipping path”. Now use the argument use_R4.1_masks, the global option ggpattern_use_R4.1_masks, or the global option ggpattern_use_R4.1_features to toggle on/off the R 4.1 alpha mask feature instead of using the use_R4.1_clipping argument or the global option ggpattern_use_R4.1_clipping as before (the latter continue to toggle on/off the R 4.1 clipping path feature in clippingPathGrob()).

New Features

  • alphaMaskGrob() is a function that (alpha) masks one grob by using a second grob to specify the (alpha) mask.

    • If use_R4.1_masks is TRUE we simply use the new R 4.1 (alpha) masks feature.
    • If use_R4.1_masks is FALSE we generate a grid::rasterGrob() approximation.
    • If use_R4.1_masks is NULL try to guess an appropriate choice.
    • The default for use_R4.1_masks can be set by options("ggpattern_use_R4.1_masks").

Bug fixes and minor improvements

gridpattern v0.4.0

CRAN release: 2022-01-12

New Features

Bug fixes and minor improvements

gridpattern v0.3.1

CRAN release: 2021-12-02

Breaking Changes

  • The package magick has been downgraded from “Imports” to “Suggests” (#44). You’ll need to manually install magick with install.packages("magick") in order to use the following “array” patterns:

    • “gradient” (but only if use_R4.1_gradients is FALSE)
    • “image”
    • “magick”
    • “placeholder”
    • “plasma”

New Features

  • The following package option ggpattern_res can now be set by options(). It controls default “raster” image pattern resolution (pixels per inch). Defaults to 72 (pixels per inch).

  • grid.pattern_polygon_tiling() now supports the following additional polygon tiling type’s (#42):

    • "rhombille" implements a rhombille tiling of rhombi (#37)
    • "tetrakis_square" implements a tetrakis square tiling of isosceles right triangles (#38)
    • "2*.2**.2*.2**" implements a polygon tiling made of rhombi.
    • "2**.3**.12*" implements a polygon tiling made of rhombi, triangles, and twelve-pointed stars.
    • "3.3.3.3**" implements a polygon tiling made of triangles.
    • "3.3*.3.3**" implements a regular (star) polygon tiling made of triangles and three-pointed stars.
    • "3.3.3.12*.3.3.12*" implements a regular (star) polygon tiling made of triangles and twelve-pointed starts.
    • "3.3.8*.3.4.3.8*" implements a regular (star) polygon tiling of triangles, squares, and eight-pointed stars.
    • "3.3.8*.4**.8*" implements a regular (star) polygon tiling made of triangles, four-pointed stars, and eight-pointed stars.
    • "3.4.6.3.12*" implements a regular (star) polygon tiling made of triangles, squares, hexagons, and twelve-pointed stars.
    • "3.4.8.3.8*" implements a regular (star) polygon tiling of triangles, squares, octagons, and eight-pointed stars.
    • "3.6*.6**" implements a regular (star) polygon tiling made of triangles and six-pointed stars.
    • "4.2*.4.2**" implements a polygon tiling made of squares and rhombi.
    • "4.4*.4**" implements a regular (star) polygon tiling made of squares and four-pointed stars.
    • "4.6.4*.6" implements a regular (star) polygon tiling made of squares, hexagons, and four-pointed stars.
    • "4.6*.4.6*.4.6*" implements a regular (star) polygon of squares and six-pointed stars.
    • "4.8*.4**.8*" implements a polygon tiling of squares and eight-pointed stars.
    • "6.6*.6.6*" implements a regular (star) polygon of hexagons and six-pointed stars.
    • "8.4*.8.4*" implements a regular (star) polygon of octagons and four-pointed stars.
    • "9.3.9.3*" implements a regular (star) polygon of triangles, nonagons, and three-pointed stars.
    • "12.3*.12.3*" implements a regular (star) polygon tiling made of dodecagons and three-pointed stars.
    • "12.12.4*" implements a regular (star) polygon tiling made of dodecagons and four-pointed stars.
    • "18.18.3*" implements a regular (star) polygon tiling made of eighteen-sided polygons and three-pointed stars.

  • grid.pattern_regular_polygon() now supports a "tetrakis_left" shape and "tetrakis_right" shape which both draw an isosceles right triangle (one oriented left and one oriented right) as well as a "rhombille_rhombus" shape which draws a rhombus. These are non-regular polygons intended to help produce tetrakis square and rhombille polygon tilings.

Bug fixes and minor improvements

  • star_angle() and star_scale() now handle the n_vertices == 2 case (a “two-pointed star” polygon is a rhombus).
  • Fixes grid.pattern_gradient() when use_R4.1_gradients=TRUE to better match behavior when use_R4.1_gradients=FALSE.
  • Now allows alpha values to be specified within the fill (and fill2) colour strings for gridpattern_plasma() and gridpattern_gradient() (when use_R4.1_gradients=FALSE).
  • In pattern_square() for the “horizontal” and “vertical” types the value 1L is now guaranteed to be in the center of the pattern (#46).

gridpattern v0.2.1

CRAN release: 2021-07-17

Breaking Changes

  • “array” patterns no longer set a minimum 12 pixel image width and/or height. In particular, they can now have a zero pixel image width and/or height (in which case the array pattern returns a grid::nullGrob()).
  • “array” patterns no longer reduces the number of requested pixels when legend = TRUE.

New Features

  • Supports the following new patterns:

  • names_pattern is a new character vector of supported (builtin) patterns.

  • clippingPathGrob() is a function that clips one grob according to clipping path set by a second grob.

    • If use_R4.1_clipping is TRUE we simply use the new R 4.1 clipping path feature
    • If use_R4.1_clipping is FALSE we generate a grid::rasterGrob() approximation
    • If use_R4.1_clipping is NULL try to guess an appropriate choice.
    • The default for use_R4.1_clipping can be set by options("ggpattern_use_R4.1_clipping")

  • grid.pattern_gradient() now supports the argument use_R4.1_gradients

    • If TRUE use the new R 4.1 gradient feature
    • If FALSE use a rasterGrob approximation (old behaviour)
    • If NULL try to guess an appropriate choice.
    • The default for use_R4.1_gradients can be set by options("ggpattern_use_R4.1_gradients")

  • The following package options can now be set by options():

    • ggpattern_use_R4.1_clipping If TRUE use the grid clipping path feature introduced in R v4.1.0. If FALSE do a rasterGrob approximation of the clipped pattern. Currently used by clippingPathGrob(), grid.pattern_rose(), grid.pattern_text(), and available for custom patterns.
    • ggpattern_use_R4.1_features Set the default for all the other ggpattern_use_R4.1_* options arguments.
    • ggpattern_use_R4.1_gradients If TRUE use the grid gradient feature introduced in R v4.1.0. If FALSE do a rasterGrob approximation of the gradient pattern. Currently used by grid.pattern_gradient() and available for custom patterns.
    • ggpattern_use_R4.1_masks If TRUE use the grid mask feature introduced in R v4.1.0. Currently unused by this package but available for custom patterns.
    • ggpattern_use_R4.1_patterns If TRUE use the grid pattern feature introduced in R v4.1.0. Currently unused by this package but available for custom patterns.

Bug fixes and minor improvements

  • grid.pattern() now throws an error if there is a non-unique pattern name (set by options("ggpattern_geometry_funcs") and/or options("ggpattern_array_funcs")).
  • Fixes an error when catching a {magick} image reading error for some array patterns.

gridpattern v0.1.2

CRAN release: 2021-06-17