Closed thomgb closed 9 years ago
Should be solved in the last version as well, I’ll wait until you confirm before closing this.
Nope. Still errors. :( I start to think its in the UFO... (is that even possible?) I have all the same errors on Yosemite and Snow Leopard (old RF), on both 3,06 GHz Intel Core 2 Duo and 2,66 GHz Intel Core i7.
I'll do some test with fresh UFOs... Did some test. Same errors...
:(
This one defeats me, I don’t quite see what’s happening there. From what I understand, the unicodes attributes (which is supposed to be a list) has a None
value, but I have no idea how and why. Does it happen with specific glyphs only?
It happens to zero contour glyphs, if there is a mode set in the operation. But now there are no errors, only the lowercase-x-with-white-capital-N-within shows :) And this glyph is also generated. I believe it should be a empty glyph with the right with... :)
Yes I’ve added those error glyphs to try and show what’s happening wrong, the x with a N means that somewhere in the process, a glyph was null, which can happen with some booleanOperations from what I tested. I prefer to have a visual feedback of the error than an empty glyph, but it’s a matter of preference, I can make this an option.
Did some tests. But the initial filters, Flatten & Spike in a group, using spaces in txtInput goes good!
But if I use some of mine the following error pops up. Are my filters wrong? Please tell me :)