I’ve just noticed on a fresh Sierra build that my 3rd party plugins don’t load when the IDE is launched. MBS, Einhuger, and my own plugins are in the Plugins folder, but they are not loaded at launch.
I’m growing very weary of the nanny-mode for OS X.
The funny thing is that if I manually start Xojo via a Terminal by /Applications/Xojo\ 2016\ Release\ 3/Xojo.app/Contents/MacOS/Xojo, it starts properly.
What’s worse than overly zealous security? Half-baked security that makes bypassing things so easy.
[quote=291790:@Tim Jones]You wouldn’t know anything about that, now would you Norman
The dumb state is that the Xojo app is properly signed, so why is it still being quarantined?[/quote]
It’s being Translocated, a slightly different thing. Finder is supposed to clear Translocation flags after you move the app yourself.
@Tim Parnell - that’s the problem then. Since the Xojo package is a drag and drop, the parent folder is moved by the user, but the Xojo.app is not being moved relatively.
I’m enjoying Sierra. I’ve had very little problems with Sierra. It’s a nice update, IMO.
deep breath
The only app I’m having this sort of trouble with is Xojo. Everything else, Pixelmator, Blocs, Xcode and a long list of other apps are behaving normally. So what’s up with that?
Assuming you are referring to plugins not loading as “trouble”, what’s up is that most of those apps don’t look for a folder next to the app to load things. They run okay even if they get translocated.
Yes, I understand. But we’re obviously not doing things properly in terms of Sierra, or this would work okay. Some of these other apps do look for template folders and the like, and they are fine.
Perhaps Xojo needs a plugin manager(*) so that the user selects the plugins to import and the app deals with them appropriately and moves them to Application Support? Likewise with the other folders such as Documentation, Example Projects etc, perhaps it’s time they should be placed somewhere else. A few years ago, I pointed out that Xojo was the only app I have installed that is inside a folder within Applications. Perhaps it’s time to fix that?