Post not yet marked as solved
It's also not clear how to call the selectors that are passed in to methods like:
canCloseDocumentWithDelegate:(id)delegate shouldCloseSelector:(nullable SEL)shouldCloseSelector contextInfo:(nullable void *)contextInfo;
shouldCloseWindowController:(NSWindowController *)windowController delegate:(nullable id)delegate shouldCloseSelector:(nullable SEL)shouldCloseSelector contextInfo:(nullable void *)contextInfo;
I'd love to see actual working examples of those methods.
Post not yet marked as solved
Any chance the 2 settings in Sound & Haptics->Keyboard Feedback for Sound and Haptics are available to keyboard extensions?
OMG, user error, but one that Apple could prevent. I revisited the docs for keyboard extensions and found it right in the first paragraph:
Custom keyboards operate in a sandboxed environment running in an isolated process. This sandbox’s default configuration disallows access to the network and prevents writing to the containing app’s shared group containers (reading is permitted). Open access lets you do things like store keyboard configuration, perform more complex analysis on text the user typed, or provide advanced features that require server support.
But Apple could help developers by mentioning RequestsOpenAccess in the error message instead of being somewhat cryptic about it.
Post not yet marked as solved
That's too bad. I'll submit a bug.
Post not yet marked as solved
I just reloaded the window in Safari showing my app, and now a couple of the screenshots *do* appear and are no longer the grey with cloud thumbnail. So I'm guessing some server is just overloaded or something and it will eventually finish. Or not.
Post not yet marked as solved
Yup. I guess we just sit and wait for somebody to fix their really obvious bug. Maybe all the developers are busy fixing the enormous number of obvious bugs in macOS 11.
Reported it via Feedback Assistant: radar://FB8976473 (if that still works for the Apple people like it used to)
Ack. Turns out I need to also turn on portraitEffectsMatteDeliveryEnabled, which is stupid. Strange that it works on my iPhone X but not on my 11" iPad Pro.
I had gone through and turned off things I didn't need, not imagining that turning off the portrait image would cause it to fail with such an unhelpful error.
Post not yet marked as solved
I've worked around this annoyance by using a regular window instead of a palette and am presenting it modally. It now appears during state restoration.
Post not yet marked as solved
Sorry this isn't a reply, but this area is severly unloved by Apple or anyone who knows how to use this framework. My question has 0 replies except for my own pokes to try to get it noticed.
Post not yet marked as solved
It's just great how 95% of the questions here go unanswered. Apple, this is a really good sign that you need to MAJOR documentation and examples for this framework. Cripes.
Post not yet marked as solved
It's annoying because it's doing the wrong thing when it should be a cakewalk.There's not much code to post:@implementation Keyword (NSScriptObjectSpecifiers)-(NSScriptObjectSpecifier*) objectSpecifier{ Document* doc = self.doc; return [[NSNameSpecifier alloc] initWithContainerClassDescription:(NSScriptClassDescription*)doc.classDescription containerSpecifier:doc.objectSpecifier key:@"scriptableKeywords" name:self.scriptableName];}@end@interface Document@property (readonly) NSArray<Asset*>* scriptableAssets;@property (readonly) NSArray<Keyword*>* scriptableKeywords;@property NSArray<Asset*>* scriptableSelection;@endRelevant portion of .sdef:<class name="asset" code="Asse" description="An asset being cataloged by the document."><cocoa class="Asset" /></class><class-extension extends="document" description="A chest document."><cocoa class="Document" /><property name="selection" code="sele" description="The selected assets."><cocoa key="scriptableSelection" /><type type="asset" list="yes" /></property><element type="asset" description="The assets being cataloged by the document."><cocoa key="scriptableAssets" /><accessor style="index" /><accessor style="id" /><accessor style="test" /></element><element type="keyword" description="The keywords known by the document."><cocoa key="scriptableKeywords" /><accessor style="index" /><accessor style="name" /><accessor style="test" /></element></class-extension><class name="keyword" code="Keyw" description="A keyword used with assets."><cocoa class="Keyword" />@property (readonly) NSString* scriptableName;</class>
