Forum Replies Created
-
AuthorPosts
-
still there is some strange behavior. I open a ufo and delete some glyphs with alt + delete so the “cells” are gone. Then I save and close the ufo. When I reopen the ufo the empty glyphs are back.
When I sort before saving and closing the deletion is “final”. So they are gone also when reopening the font.hey sami,
are you looking for this:
• alt delete also removes the template glyph ?
cheers,
jothanks! works perfectly now.
I just did a quick test of some of your other extensions and there seems to be a problem with text(). The pointCounter and drawReferenceGlyph extensions give the Traceback: text() takes exactly 3 arguments (4 given), but as far as I can tell there are only three arguments given.
thanks,
jothanks for super fast reply !
looking forward to v 1.3thanks for adding f.info.asDict()
about the crashes: I cannot say for sure. it happens rarely and I have no idea how to reproduce it. I just remember that it happens after clicking font info.
I found a crash report in my Library/Logs/ from the most recent crash but I am not able to make sense of it.thanks jo
hi frederik,
thanks again for this and all the other replies!I did some minor changes (like printing a better report in the output window).
The latest version can be found here:
http://langustefonts.com/dwld/Componitor1.3.1.zipthanks, jo
I hope somebody will post a more elaborate answer but I think you should convert the non ascii characters so python can read them.
Seconds = u”\u00E0 \u00E9 \u00EF \u00F8 \u00FB”
hey,
thanks a lot for the input!
I added a check for CurrentFont() is not None.
Also changed the color conversion.About the closing window behavior:
I added and removed the close function a few times but I guess it is a question how the extension is used.
Personally i am happy about every click / mouse movement / typing i can avoid.
In this case I don’t really need the window anymore after the new glyphs are built.
So why not close it automatically instead of clicking once more to close it.
I commented it out in the latest version:
http://langustefonts.com/dwld/Componitor3.1.zipJust as a general question: are there any extension building guidelines (for design or behavior)?
Maybe a bit off-topic but somehow related:
In the “Add component” window the “copy metrics” is active if there is at least one outline in the glyph but turned off if there is a component. Shouldn’t “Copy metrics” be active by default only if the glyph is empty?June 1, 2012 at 13:29 in reply to: some characters not showing in space center after copy pasting #4169The new font i am copying the “radical” to just has the default “Latin-1” character set. So there is no template for the radical. When i paste it (from the font that has the “radical”) it just adds it as a new glyph with the name radical (no .copy_1 suffix). In the inspector i see the unicode value, width and margins. Just in the space center it does not show the glyph.
Even more surprising. I just copied the radical a second time to the new font so it adds the “radical.copy_1” glyph. If i select the “radical” and the “radical.copy_1” and open the space center it shows the “radical.copy_1” but not the first version.is there a way to post screen shots?
thanks
June 1, 2012 at 11:48 in reply to: some characters not showing in space center after copy pasting #4162sorry for the confusing post.
i have a font with eg the glyph radical. I copy it from the font collection and do File –> New font. Then with no glyph selected in the new font I press paste. I can see the radical in the font collection. I select it and open a space center window. The radical is shown in the “input bar” but not in the actual window. Also in the metrics i can see the radical but no values for width, left and right margin.
if i close the font and then reopen it everything is fine.
Sorry again and thanks for the quick reply.
-
AuthorPosts