Closed simoncozens closed 1 year ago
Ideally we should (a) allow userData on anything which can take a userData on the Glyphs side and serialise it, and (b) convert the UFO objectlibs back to Glyphs objects. But I don't need that today, and I am in a hurry. :-/
it's ok to do later, we can file an issue so we don't forget
This goes part of the way to fixing #910. It saves any userData on an anchor to the glyph's objectlib dictionary. This allows us to later get at the contextual user data attached to the anchor and generate contextual mark lookups for it.
Ideally we should (a) allow userData on anything which can take a userData on the Glyphs side and serialise it, and (b) convert the UFO objectlibs back to Glyphs objects. But I don't need that today, and I am in a hurry. :-/