Daniel Howe
Daniel Howe
This default font is a font supplied by the browser... we can use it, but we don't get all the font data that would be needed to create a p5.Font...
So one use-case is a color-based image quad tree (like [this](https://observablehq.com/@mbostock/quadtree-art)), where, for each region of an image, you need to decide if it should be subdivided, based on how...
amazing - when will the next release happen ?
I guess I was referring to the npm version, which is currently on 2.4.2... Of course I can dl directly but I'm teaching node/npm this week, so was hoping to...
is it in any cdn, other than github ?
Can someone test if this is still an issue in p5 v2.0 ?
I think the problem here is that the variable name shadows the built-in p5 function `str()` - changing the variable name should fix it (or using `let` instead of `var`)
Thanks @davepagurek -- this is a known-issue discussed in https://github.com/processing/p5.js/pull/6967 The fix, which will hopefully be included in v2.0, is to accept `textLeading` (and all other relevant params) as part...
The API is a bit different now, as `textBounds()` is implemented on the renderer rather than p5.Font, and fontSize is not an argument. `p5.Font.textBounds()` remains for backwards compatibility but delegates...