![]() For now, I have simplified that to a single icon for each: The full application has a set of different icons representing different types of disk and network for different performance tiers. I have built a small example project with an object factory instead of an API connection. The hitches get far worse when I bump the number of columns up to the 20 or so I want to use in the real application. It also properly observes the disk/interface objects themselves for changes (e.g, renaming). View reuse is working, and the internal SwiftUI view properly observes the field for new or removed disks/interfaces. They then contain a SwiftUI VStack containing a ForEach which renders a row for each disk/interface. These views present an objectValue property, which gets modified as expected. I have an NSView subclass for the disk column's views and the network adapter column's views. I originally built the NSOutlineView programmatically, but I've switched to building it in Interface Builder to get the NSTableCellView reuse behavior without needing to subclass and write my own implementations. Instruments tells me they are due to expensive commits. The problem I have is that when I scroll my outline, it has significant animation hitches. The VMs can be organized in folders, so I'm trying to use NSOutlineView bound to a tree controller to show the downloaded data. For example, a single VM can have several disks or several network adapters. They also have a few properties which are lists of relationships to other things. The VMs have a lot of simple properties like a UUID, a name, a comment field, a power state, and so on. I am building an application to show a list of VMs running under my account on a hosting provider. I'm targeting macOS 11 and up, running macOS 12.4 (21F79), and working with Xcode 13.4 (13F17a). Photos that fail on macOS share as expected on iPhone from the same library. Everything works as expected when sharing Live or Portrait images taken by me. On macOS I see this error when trying to share photos that I didn't take, but have been added to my library manually, via WhatsApp for example. I have seen this error elsewhere on the forums linked to PHPickerViewController and bug 64630315.īug 64630315 is claimed fixed on iOS, but might it still be an issue on macOS? My Share Extension works correctly on iOS. Let context = NSGraphicsContext.current()?.cgContext The software will crash if old versions of ClickShare are running at the same time or have been run on the computer without it being restarted.I am using the code below to learn more about drawing but I am getting an ambiguous error on the line not sure how to resolve this. If ClickShare keeps crashing, restart the computer. ![]() Check the sound is going through ClickShare by going to System Preferences, then Sound, and changing the ‘Output’ to ClickShare.The screen should now be shared and there should be no issues with video or audio.Once the software recognises the dongle and the court room it is in, either click the white button on the dongle, or click the small white ring on the desktop software.The connection notification box for ClickShare should be located in the bottom right of the screen.If the software will not start, restart the computer. The ClickShare App should now have a tick next to it. The first time you run the software you need to enable screen recording on the MacBook for ClickShare.Open your applications folder and double-click on the white ClickShare logo, the software should open.Do not run the software that appears when you plug in the dongle. ![]()
0 Comments
Leave a Reply. |