Jakub

(Also: @mtennekes where can I find the list of actual colors (either as R names or hex codes) that are used in the design mode?)

Thanks, @mtennekes. Two ideas/suggestions: 1. The `overall` argument name is hard to understand (by me, at least). If I understand correctly, the first option (TRUE) shows areas, and the second...

@mtennekes include_elements (or include_content) -- I think it still may be useful for the areas -- I can imagine looking at the design mode with areas first to get the...

@mtennekes great progress. One suggestion -- maybe add the meaning of the black lines to the "Color codings:" text? (Also, have you tested other colors for these lines, e.g., white?)

Hi @mhesselbarth -- I will take a look at this in the next week or two (I have some other deadlines approaching soon).

Hi @mhesselbarth I have finally take a minute to look at this. I think you are looking for `terra::is.lonlat` -- so basically it could be something like: ```r terra::expanse(y, transform...

@edzer see this: ``` r library(sf) #> Linking to GEOS 3.12.1, GDAL 3.7.3, PROJ 9.2.1; sf_use_s2() is TRUE nc = st_read(system.file("shape/nc.shp", package = "sf")) nc_g = st_geometry(nc) nc_g = st_transform(nc_g,...

I was working on preparing an issue for GEOS, and then I found out that the **geos** package seems to return expected result. @edzer what could make a difference here?...

@mtennekes -- I think this limitation is a good idea. I've been recently working on the layout chapter, and looking at the v. long list of arguments was a bit...

@mtennekes 1. Yes -- I think that general options, such as the `text.fontfamily` argument should be in `tm_layout` 2. I like the `tm_comp_group` idea -- I think it should work...