Hey there, For a project I'm working on I've come to a situation in which in order to avoid making a lot of kerning pairs I might need to use feature classes in order to add space between them. While reading the specs for OpenType features I've come to these particular ones: · Left bounds (lfbd). · Right bounds (rtbd). The point is that I've never seen these in use or a line of text using them so I don't know exactly how they are supposed to be set. Any help? Thanks a lot!

@gferreira said in How to get programmatically highlighted glyph in the space center: (don’t know how to get the cursor position) I think I will be able to figure it out. I will post it here when I will do it Thanks a lot again!

Also the same happens in the cut method. It seems BaseEventTool is not overriding the keys meant for this methods because I get them in the keyDown, but for paste I don't see the event in keyDown, so it's working there.

hi @bahman, you can provide your own style.css file inside the same folder as the markdown or html sources, and it will override the default stylesheet. we can also try to improve the default stylesheet so that large images are scaled to fix into the window width. cheers

Ok the problem was on my end. I had a script that was running on fontWillSave, and it was raising an error. Apparently that also halted the fontWillSave notification overall... So if one script fails, others may not be called? Would it be possible to post the fontWillSave notification even if a script attaching to that event fails? Thanks!

Ive made an issue here https://github.com/roboDocs/ScaleFast/issues/8

@frederik Oh interesting! After some thought, I wouldn't lock the vertical line to 90 degrees because after you've set the baseline, I'm not sure you'd want your horizontal movement of the x-height point to unexpectedly change the decided baseline setting. Having the angle of the x-height line only react to the baseline points makes sense to me. In terms of UI interaction, the only thing I'd change from the public release is to not draw the vertical line (or maybe draw a lineDash if anything), as it doesn't seem to correspond to any UI in Glyph View. Otherwise, I think it's less about the UI than the unexpected resulting transformation.

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

Cool Ryan! I will have a look after Christmas. Maybe I will come up with some ideas how to make it work 100% nicely :D

In many cases I find a lag in RF interface. It feels RF is not responsive as before or is slow in way that is blocking me from doing a task. I forget to document or report them. So here is a start: BaseEventTool shift key release To reproduce the issue perform the following: Open a glyph which contains an anchor. Select the anchor using mouse and the basic editing tool. Drag the anchor in a fast reptitive motion. While dragging, hold the shift key and release it, but don't release the mouse while doing so. Now the anchor that was being dragged is lagging behind the cursor. Same thing happens with contour nodes. Is there any reason this is happening?

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.

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)

I think it also had to do with the OS used. I remember problems with Input Mono on 10.14, and had a discussion with Frederik about it (which is lost in the depths of a free Slack).

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

I pretty much used this script while going through my whole script folder. The folder pretty big and very unorganized at the moment, but I'll send you an email with that. Thanks for all the help, Frederik!

@frankrolf Yeah, I’m a happy MM user, but was thinking it feels like a logical extension of the info panel. @frederik Is the new MM API out? I’ll see what I can figure out with a little vanilla view.

Cool. Thank you for fixing this, and thank you for the explanation.

Looking forward to seeing this get fixed. Thank you @frederik.

Sometimes when a guideline is moved, the undo will not work. Also sometimes, the name is erased. I can reproduce with both local and global guides. Video Version 3.3 (build 1911061105)

cool! an different approache! I like it