computeBounds() breaking change in 4.1.0 about pixie HOT 2 CLOSED

Thanks Ryan,
layoutBounds works perfectly for what I'm currently doing. I just didn't know where to look :)
I want to thank you and treeform for a fantastic suite of packages. I'm using vmath and pixie, in the process of test driving windy and fidget. I'm also eyeing flatty, netty, zippy and spacy. You guys are Nim Rockstars!

from pixie.

The previous version of computeBounds is now layoutBounds.

There exists fonts where the previous version of computeBounds does not work. This is related to some fonts having glyphs for characters that go outside of the glyph typsetting rect (see https://github.com/treeform/pixie/blob/master/tests/fonts/rendered/spans7.png).

Using the previous computeBounds works for most fonts, but not all. If it works for your purposes, you can simply switch to that and be all good as an easy fix. The new computeBounds is actually correct, but a little bit more complicated to use to actually get things correct in all cases. Here is how to use it: https://github.com/treeform/pixie/blob/master/tests/test_fonts.nim#L1018

Basically, bounds.wh will work for sizing the image and you'll need to translate the origin a bit by bounds.xy to make room for potentially larger glyphs.

from pixie.