Posts

Post not yet marked as solved
2 Replies
Hi Michael, Thanks for your reply. I did find the post you refer to myself as well a couple of days ago. Actually I wanted to post this link myself, but I did not yet, as I did not get things working. The (extensive) code example the Apple engineer posted looks promising, but in my code I could not get it to work: I did notice that as soon as I set the focusValue, my app goes haywire: my codebase has some NSViewControllerRepresentable's and the update method is called endlessly as soon as the Focusvalue is set. This causes my app to show the spinner and become unresponsive. I suspect it is a bug, but I am not sure. I posted a bug report to Apple, hoping they will ever read and fix it. In the meantime, I keep trying myself and I am hoping someone on this forum might come up with some great solution. While I am at it: I think the demo code is the way to go, but it raised an additional question for me: suppose one has an embedded AppKit outlineView (or whatever) and want to update menu, for example because. that outline view has the focus on some selected items: how to (best) use "focus value" from within appkit?
Post marked as solved
2 Replies
Post marked as solved
1 Replies
Update: working in Big Sur beta 9, XCode12.2 beta 2.
Post not yet marked as solved
3 Replies
Same question here... I have been puzzling on this for many hours. How is this supposed to work Apple? It is nice that you think up new magic stuff, but please add some instructions on how it is supposed to be used, using real-world examples. I watched your WWDC session, but still it is a puzzle. If an apple engineer is reading this: please enlighten us...
Post marked as solved
2 Replies
@Frameworks Engineer: how? How would you "put a NSTrackingSeparatorToolbarItem in your toolbar" if you are working in swiftUI 2.0 (not creating a toolbar in Appkit, but using the .toolbar modifier in SwiftUI?
Post not yet marked as solved
26 Replies
Suffering the same problem (still in 12.2 beta 2). It look like some empty, non translucent, view is laid over the area where the attributes should show, making it impossible to see anything. We are literally being kept in the dark. I really wonder how Apple quality control can release software like this. Don't they ever use Core Data themselves? Could it be that Beavis and B*tthead are now running development at Apple, trying to mess things up, just for fun: "let's put a blank view over everything, huh huh, yeah, yeah, huh, huh"? Please file a problem report to get the deaf and mute at Apple to notice "something is wrong".
Post not yet marked as solved
13 Replies
ACK, same here. First it was one way problem only (not able to access anything on network from my TDK), now -since the beta 6 update- it is I-directional. Since latest I found that automator scripts to connect to a server do not work any more as well. What a mess.
Post not yet marked as solved
1 Replies
I am asking myself the exact same question. Did you manage to figure this out?