I’m writing an add-on / extension which requires hardening of Blender’s Scripting & Security policy for imported scripts (wasn’t the original purpose of the add-on, lol, but is necessary)…
And discovered that Swedish, of all languages, is not translating properly for the Auto Script Execution Warning Dialog that pops up when you try to open a file with a Registered script.
…and IDK if anyone’ll care for the bug report anyway since the issue is resolved in 5.2, at least. (Didn’t test 5.1, but issue persists in 5.0.)
…AND now I have to code around it.
The good news, I suppose, is that I had to code around it already, since Blender doesn’t provide access to the dialog from bpy, which I suppose is fair, I guess, so I coded a replacement.
I did an absolutely amazing job, too, lol. I finally cracked how to do an actual modal button dialog with Blender’s UI — something that no one has believed can be done for ages.
I’m actually kind of afraid to release it into the wild since that’ll just tell other people how to do the deep magic, and then it’ll immediately get abused and devs will have to do something to break the magic and I’ll be sad.
For comparison, here’s Blender’s dialog on the left and my version of it on the right:
This image was snagged from 4.5, sorry, 5.something introduced the red bar at the top, which it is not possible to do in bpy. It is also not possible to get the “bold” (brighter) title text from bpy. I suppose some fancy font swapping could fix that, but that’s too far a kludge for almost zero benefit and plenty of potential failure when displaying translated text.
I also removed the dumb “permanently allow” checkbox — I don’t think it belongs there, but feedback may change my mind at some future point. (If so I’ll add it in.)
And I admit that I dislike the stupid X-stop sign. Not a fatal error, just a serious warning. My yellow icon is cooler, heh.
Anyhow, it works great, responds to keyboard input, keeps alive until an option is selected either explicitly (pressing a button or a key) or implicitly (clicking outside the dialog).
The purpose of the extension / add-on is to manage scripts attached to assets, allowing you to run them or to disable them properly (to plug a security hole in Blender) — reversable, of course, so once you decide a script is safe you can one-click re-register and activate it.
Anyway, I’ve been adding translations for a good dozen languages (the ones I can manage and also don’t not want to do, heh) and discovered the Swedish issue. Now I’ve got to go update all my .mo files to use my own version of the dialog’s text instead of relying on the system translation for it. Fooey.
And I’m here blowing off a little stress from that. Making a bug report isn’t tough, but I had to create accounts on at least two Blender sites that I’ll never use again. Meh.
I suppose I should make it worth your time to have read through all this. So, here ye go:
That’s right. Y’all deserved that. You should have seen it coming. Enjoy!

