ve got a similar issue with my package. I want to break stuff as I've thought of better ways, but I don't want the hassle and messiness of deprecating stuff. So I reckon just update with a new version - if users use renv etc, there is no breaking code

Great idea, and totally needed! Would prefer filter_keep/filter_drop naming, and deprecate filter. In my head, that is much clearer

Use ggh4x::save_plot to save it instead of the hacky code there

I just don't really have an easy way of testing if they are working. I found this site which enabled me to test for 5 modes. I got significantly different for Overlay, which made me wonder if the others had errors in too colorblendy.com

I did this using AI. For multiply/screen, it's definitely correct.. For the others, I'm less sure.. Wondering if I should release it as a standalone package, or chuck it in with the rest of my viz utils functions..

Close, but slightly different. After the blend mode algorithms that are used in photoshop etc

Good idea, can't see anything there..

Two of the best tbh

Very strange flower. Nothing else like it in nz

Rewarewa

I'm for trailing commas

I never write informative git messages or chunk commits in a logical way. Git add . Git commit -m "Update" git push

The rationale why it isn't in ggplot2 is provided here github.com/tidyverse/gg...

save_plot in DEV version of {ggh4x} by @teunbrand.bsky.social saves a plot with set panel dimensions very nicely. Apparently, it won't work 100% of the time. Hence it being in {ggh4x}, rather than {ggplot2} teunbrand.github.io/ggh4x/refere...

Same here..