Thanks a ton for the resource, Frederik! Looks like my tool window is now going to be a landscape image;)

@frederik said in how to add custom button to the SpaceCenter's display menu ?: for now this is not possible... Space center menus are on the restructuring table. To split up into a menu for display options and a menu for typographic options. I can imagine adding a similar notification like in a glyph window or font overview So I imagine that it is also not possible for the right-click menu in SpaceCenter? this button, on top of the SC, for now, should be enough. Thanks!

Oh my, I really did overthink the issue — reorganizing my functions just a little and adding the self.updateFont(None) solved it!! Thanks for the help, Gustavo!

Thanks for the info.

Its indeed similar to a pen. This allows easy subclassing of internal tools by simply adding behaviour to a tool. This tool is subclassing _mouseDragged as it needs the same behaviour but with the shift constrain disabled, as this tool will perform his own shift behaviour.

@frederik Thanks!!

a pull request to https://github.com/Typefounding/copyGlyphs is made FYI: the bug was that keys of a dictionary are not a list anymore... so they cannot be sorted see https://github.com/Typefounding/copyGlyphs/pull/3

@frederik @gferreira Ah thanks, guys! I was trying to do it in lib and not mojo 🤦‍♂️

Lifesaver! Thanks @frederik

maybe you have to explain what you want to achieve... A space center object has getRaw which returns the input text as seen in the control and get which returns a list of glyph names, those are parsed from the input controls.

its been described here https://docs.microsoft.com/en-us/typography/opentype/spec/features_ko#lfbd You can use pos in an feature to position a character or a pair (like kerning) or even contextual move characters around.

Thanks @gferreira!

similar as to vanilla SplitViews an AccordionView will get: anAccordionView.isPaneVisible(label) anAccordionView.showPane(label, animate=True) anAccordionView.togglePane(label, animate=True)

Thanks, @frederik!

That is True! for now the inspector is made for inspecting single glyphs. An extension can add a inspector pan with this behaviour!

For maximum flexibility each glyph has his own undo manager. You dont want to use a single undo manager for everything. I understand in this case a single cmd-Z should perform actions in multiple glyphs. A while ago Ive made dirty hack... let me see if I can clean it up.

@JustJoeDesign That said, it’s not impossible to use UFO2 files + makeotf on Catalina. install the AFDKO command line tools via pip https://pypi.org/project/afdko/ build your OTF file using makeotf -f my_font.ufo The only hard requirement is that the UFO has a PostScript name. (Font → Font Info → PostScript → FontName)

hello @bahman, representations are handled by defcon, the docs are here. glyph = CurrentGlyph() path = glyph.naked().getRepresentation("defconAppKit.NSBezierPath") cheers!

this is pretty cool: import AppKit import defcon from fontTools.ufoLib.glifLib import writeGlyphToString, readGlyphFromString # get the paste board pasteboard = AppKit.NSPasteboard.generalPasteboard() # get the data possibleGlifXML = pasteboard.stringForType_(AppKit.NSPasteboardTypeString) # maybe its glif xml, could also just be normal text print(possibleGlifXML) # get a dummy glyph dummyGlyph = RGlyph() succes = False try: # try to read the xml readGlyphFromString(possibleGlifXML, dummyGlyph, dummyGlyph.getPointPen()) succes = True except Exception as e: # if not valid fail print(f"Not valid glif xml!\nerror: {e}\ndata: \"{possibleGlifXML}\"") if succes: # do something with the glyph dummyGlyph.moveBy((50, 50)) # get the glif xml glifXML = writeGlyphToString(dummyGlyph.name, dummyGlyph, dummyGlyph.drawPoints) print(glifXML) # clear the past board pasteboard.clearContents() # write it back in to the paste board pasteboard.setString_forType_(glifXML, AppKit.NSPasteboardTypeString)

oh, idd not working as it should be... will be fixed in next beta/release thanks