I saw that my Skedge plugin crashes Glyphs 3 right on start and spent over an hour trying to debug* until I nailed it down to the from vanilla import... statement.
So I tried to check for vanilla just in the Macro panel print(vanilla) or from vanilla import Window (which recently still worked, as I wrote this in some thread here). The latter shoots Glyphs off directly into the Nirvana even if you use a try:
from vanilla import Window
According to the Plugin Manager it is installed. I also tried to uninstall and reinstall.
*) There’s sth odd happening now when a plugin causes a crash. After the restart, Glyphs asks to remove the plugin. If I cancel, it appears to just not load the plugin, if I click on “remove” it removes it, but that means I have to create my Alias form my WIP plugin again and drop it into the plugins folder. Even with shortcuts this is very tedious and I spend probably 80% of that hour just doing this
from vanilla import Window runs just fine in my 3061 Glyphs. I installed vanilla from the Plugin Manager. I also installed Python from the Plugin Manager and selected in the preferences (3.8.2). macOS 11.2 (20D64)
I’m currently developing a plugin and it crashes all the time (I keep forgetting to add an _ at the end of method names ). I never saw that dialog.
Ah, so sorry you have a beautiful new Mac But seriously, there have been multiple reports on the forum where 3.9.x does not work and 3.8.x does (Speed Punk is a prominent example). I don’t have any M1 hardware, so I can’t test that.
I don’t use vanilla for my plugin (which removes many pesky underscores) and instead use vanilla plain Cocoa APIs.
Me usually too, but that doesn’t help when all my workflows are based on working plugins and suddenly don’t work anymore. The python version might be a legit pointer, as the plugins all work fine on my Mojave 2014 Mac.
Oah, thank you. I could get Glyphs back to launching by that.
For the record (my future self): Reset stored Python Framework Path via Terminal: defaults delete com.GeorgSeifert.Glyphs3 GSPythonFrameworkPath (Never delete or change in the plist file manually, this can cause trouble, big time!)
Or check for it via Terminal: defaults read com.GeorgSeifert.Glyphs3 GSPythonFrameworkPath
Georg told me I need to stick with the Python.org version in the settings. So I’ll do that.
Python is Idee broken. Try to deinstall all other plugins and the “import vanilla” might work. The KernKraft plugin is one of the few that causes the crash more than others (not your fault).
I had a combination where I could install plugin A+B or A+C or B+C but not A+B+C. One plugin I could “fix” by removing an import unittest. Go figure.
I’m trying ot understand the problem, I even just compiled Python from scratch to be able to better debug it.
That message it triggered by an attributed set on the file in the plugin folder. To reset it, remove the Alias (you are using aliases to you git repo, aren’t you) and make new one. If it is too annoying, I remove that.
Yes exactly, Aliases. I always have to cmd-opt drag the plugin into the the Plugins folder to get it back there. It’s indeed annoying, especially in the debugging, where as you know it’s currently more a poke-around-in-the-dark-debug-style Would be amazing if you could remove that behaviour.