Forum Replies Created
-
Posts
-
Thanks for letting me know, Frederik. Not meaning to rush, I was just wondering :)
Hey, I came across this old thread while searching for ways to force quit a running script. Is there anything like cmd-. that works to cancel when a script gets stuck?
Thanks :)
ninaThat helps! Thanks. :)
OK, thank you, Frederik. Hmm, that sort of confirms what I suspected. I was hoping there was a way to generally «unlink» the leftMargin of the component from that of the base glyph; because even when this routine is set to ignore/bypass components (as in your first code example), the fact that if I change the leftMargin of the “O”, inside an “Odieresis” the “O” part (but not the “dieresis” part) will by default be moved along, means the relative placement of diacritics and other components is lost when spacing of the base glyph is changed. True? I’m probably completely failing to express this clearly (sorry!) but I’ll try to build upon your «solution #2» in my script to try to move the other components along, or something. :) Thanks again.
First post, newbie, hi!
(Please forgive me (but tell me) if this is a stupid beginner’s question and/or in the wrong place)Allow me to piggyback – I’ve been playing around with something in this direction and noticed something I wanted to ask about: shifting components upon respacing of base glyphs.
Say I have a base glyph O and a destination glyph Odieresis, which is made up of an “O” component and a “dieresis” component. Upon changing the left sidebearing of the base glyph (O), doing an update() on the Odieresis glyph shifts the O component within it to match the new sidebearing of the O, resulting in a correct left sidebearing but a misplaced diacritic (and unchanged width, etc.)
Is this the intended behaviour? Is there already a «predefined» way to avoid components «moving» with their base glyphs?Thanks, N