When scrolling a basic NSScrollView there seems to be a sudden jump after each flick. Scrolling does not appear smooth and is disorientating. A scroll jump seems to happen directly after letting go of a scroll flick using a trackpad/mouse. Right at that moment the scroll turns into a momentum scroll, slowly decreasing the speed. But the first frame after the gesture the content jumps forward, more than what is expected. Observations: Counterintuitively, scrolling appears to be smoother when disabling NSScrollView.isCompatibleWithResponsiveScrolling. If disabled using a custom NSScrollView subclass there is no large jump anymore. Scrolling also appears to be smoother using a SwiftUI ScrollView. I assume that has the same behaviour as a disabled isCompatibleWithResponsiveScrolling Ironically a WKWebView scrolls much smoother. No sudden jump is observable. It also seems to scroll with faster acceleration, but the individual frames do appear smoother. Why is this better than a native NSScrollView? Elastic scrolli
Search results for
smb big sur
11,800 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I have prepared a NSSpellServer spelling and grammar checker for Slovenian proofing in macOS. My proofing service gets used when I explicitly set keyboard spelling language to Slovenian (Besana) (my proofing service). However, no matter how I set the Check Grammar With Spelling option or Check Grammar checkbox in the TextEdit.app or Mail.app, my proofing service does not get any request for grammar checking. I am supporting checkString call for Unified checking and checkingTypes never contains NSTextCheckingTypeGrammar flag. When using legacy API before Unified checking support, the checkGrammarInString is never called either. If I do the grammar regardless the checkingTypes parameter, the app shows grammar mistakes correctly. But that is bad UX. Need to follow user demand for with grammar or without grammar. I don't know what am I doing wrong? On my home iMac v11 it actually works. No idea what I did there to make it work. Just worked. On my working Mac Mini v13 it won't check grammar. On another MacBook Pro
We build mobile apps for creators to edit their videos. Post editing the video, the creator has to export the video so that it can be uploaded to Youtube. The export is a time consuming and GPU intensive process. The creator can exit the app due to various reasons like receiving the call, putting the app in background etc. This causes the export to fail :( Keeping this limitation in mind there was an announcement from Apple that with the IOS 26 launch would start to support background GPU access. Here is the official documentation: https://developer.apple.com/documentation/BundleResources/Entitlements/com.apple.developer.background-tasks.continued-processing.gpu When we tried using this feature, we were not able to get it to work on IOS 26. We stumbled upon this ticket(https://developer.apple.com/forums/thread/797538?answerId=854825022#854825022) in the Apple Developer forum, in which possibly an Apple engineer claims it is supported ONLY for iPadOS 26. This is a very big bummer for us. 96% of the us
Topic:
Media Technologies
SubTopic:
Video
Hi all, As you know, when using SwiftData Cloudkit, all relationships are required to be optional. In my app, which is a list app, I have a model class Project that contains an array of Subproject model objects. A Subproject also contains an array of another type of model class and this chain goes on and on. In this type of pattern, it becomes really taxxing to handle the optionals the correct way, i.e. unwrap them as late as possible and display an error to the user if unable to. It seems like most developers don't even bother, they just wrap the array in a computed property that returns an empty array if nil. I'm just wondering what is the recommended way by Apple to handle these optionals. I'm not really familiar with how the CloudKit backend works, but if you have a simple list app that only saves to the users private iCloud, can I just handwave the optionals like so many do? Is it only big data apps that need to worry? Or should we always strive to handle them the correct way? If that's the case
SwiftData + CloudKit uses NSPersistentCloudKitContainer under the hood, which requires all relationships must be optional. For more information, see Creating a Core Data Model for CloudKit. The requirement exists because of the latency of the synchronization: When you create an object graph in device A, which is being synchronized to device B, the system doesn't guarantee to synchronize the whole graph all at once. As a result, it's possible that an object is synchronized but its relationship is not. This situation is expressed as the relationship being nil. By checking if the relationship is nil, the app instance running on device B can consume the object appropriately. In your case, wrapping a relationship with a computed property to return an empty array if nil makes sense to me, if the other part of your app prefers to consume an empty array. It doesn't matter if the data is big or small. Best, —— Ziqiao Chen Worldwide Developer Relations.
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
Can you share the full build report? To collect it: Choose View > Navigators > Reports. Select the report associated with your app’s build in the navigator. Using the filter bar at the top of the build report, select the filter buttons for All and All Messages. Click Export in the filter bar to save the detailed build report. Depending on the size of your app, the report may be too big to attach to a post here in the forums. If that's the case, providing a URL where we can see a copy would also be fine. — Ed Ford, DTS Engineer
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
First off, on the bug front, these issues should be resolved in macOS 26.1, which we released to beta last week (25B5042k). Please test on that beta, and if you find any problem, file a new bug and post the bug number back here. Are we actually talking about the same bug though? Yes, I believe so. Coe 256 seems to be an issue only for the root drive of exFAT. The issue here was actually introduced as part of a security fix (r.151029665) and it affected exFAT, some SMB mounts, and the / AFPS mount. In both cases, the high-level issue is the same (basically, stat wasn't returning what it expected), but the underlying cause was different. In the case of exFAT, the file system is basically “too simple, so it's basically returning a synthetic (invented) value because the file system doesn't really have an alternative it can provide. In the case of APFS, the issue is that the way that data and system volumes are merged means that you can get different values for the same object, depending on exactly how yo
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Hi, I was looking for advice on the suitable mac to get for a web app development project for university . Would an Apple MacBook Air 2020 M1 8GB RAM 256GB SSD 13.3 macOS Big Sur, be sufficient ?? Or would I need a newer version !
Topic:
Business & Education
SubTopic:
General
the launchHandler is there to tell you the task has started and provide you the BGTask object you use to manage that work. No task type actually requires the work to occur inside the task. Thanks Kevin! So I need to think about this a little differently then. Instead of performing the work once you get a BGContinuedProcessingTask, just begin performing the work (the exact same way you do in iOS 18), if a BGContinuedProcessingTask starts persist it and update it as the work completes, and reset state when the work finishes or gets canceled. Basically, something like this: 1-6 I put together code to demonstrate this approach. Did I understand correctly, this should be all good with this simple counting demo? class ViewController: UIViewController { private let taskIdentifier = (Bundle.main.bundleIdentifier!).count_task private let countToNumber: Int64 = 100 private var currentBackgroundContinuedProcessingTask: BGContinuedProcessingTask? private var shouldStopCounting = false @IBOutlet var progressLabel: UILabel
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags:
When will we configure Hibernate 25? Is it valid for M series MacBooks? Is Hibernate 25 called deep sleep mode? So, let me start by quoting the man page for pmset: hibernatemode = 3 by default on portables. The system will store a copy of memory to persistent storage (the disk), and will power memory during sleep. The system will wake from memory, unless a power loss forces it to restore from hibernate image. ... hibernatemode = 25 is only settable via pmset. The system will store a copy of memory to persistent storage (the disk), and will remove power to memory. The system will restore from disk image. If you want hibernation - slower sleeps, slower wakes, and better battery life, you should use this setting. The thing to understand here is that the difference between those two ISN'T about how either mode “prepares for sleep. Both of them do exactly the same thing— that is, they flush all memory to disk, ensuring that power loss won't lose any data. The difference is that having done that flush, Hibernate 25
Topic:
Privacy & Security
SubTopic:
General
Tags:
The problem ended up being solved by calling: sfltool resetbtm in Terminal, followed of course by a restart on each affected machine. Interesting that it occurred across several machines all running macOS 13 and 14 right when we updated to Xcode 26. It does seem like the system will occasionally get upset with big changes to the app through the development cycle.
Topic:
Code Signing
SubTopic:
General
Tags:
I have an existing Mac app which has evolved through over twenty years of development. It is currently written in a mixture of C++ and Objective-C, with a bit of C and Swift in a few places. For a few years now, I have been tinkering with replacing the UI with SwiftUI. The model has been completely rewritten in Swift and works fine. After a few tries, no version has been working acceptably, so I'm thinking that I need to rethink the architecture. The UI consists of a window with a master-detail view. The detail view is what users spend most of their time with. It contains a lot of subviews, around 100 typically. Keyboard events affect the display, so I've had a dedicated data structure to hold the state that is needed for displaying all the subviews. Using Instruments, I see that the view seems to recreate the subviews three times per keyboard event, so I'm clearly doing something wrong. A second factor is that there are a couple of dozen commands that are applicable to the detail view, driven either by menu
Please check the crash files as attached. So, this is a great example of why I always ask for a crash log, as the problem here doesn't actually have anything to do with the audio system itself. The problem is that your app is stuck in an infinite loop. For future reference, the most direct proof of this is that the number of stack frames on the crashing thread is very high (860) and that the base of the stack ISN'T a valid entry point for a thread. For the main thread, this would be main, but other threads would be thread_start or a similar entry point in libpthread. Crash collection system artificially limits the number of frames it collects (otherwise you'd potentially have 1000s+ of lines of repeating frames), so you aren't actually getting the true bottom of the stack. 858 <...> closure #1 in DeviceManager.init() + 80 859 <...> partial apply for closure #1 in DeviceManager.init() + 24 (/:0) 860 <...> closure #1 in NSNotificationCenter.addObserver(forType:object:queue:using:) + 232 (GaiaN
Topic:
App & System Services
SubTopic:
Hardware
A is there a way to get big huge notitifications for Shareplay invitations ? B can i have the notifications inside the app ? we have a corporate app to check archtecture projects we want to share these 3d spaces walking inside with near users in the same place to discuss about the project .. but it takes too long shareplay invitation is a small circle on top, if the others users just put the vision without configuring eyes and hands... it's gonna be impossible thanks for sharing and giving us support
I have also just seen the height is way too big issue on Tahoe 26.0. I had recreated all my icons as all-vector PDFs with a large size and the toolbar grew to a huge depth (I presume the same size as the icon's files). Changing the page size of the PDFs to 32 (expressed in pixels in Affinity Designer) calmed this down but the icons are scaled to different sizes (mostly too small) if the sizing is left as Automatic. I had just changed them all from explicit sizes of 24-32 pix and it was all perfect on Sequoia/15.6. I though explicit sizes were deprecated so I had changed them as derisking action for Tahoe :-( Has anyone found any up-to-date documentation on NSToolbar? The only docs I have are very old.
Topic:
UI Frameworks
SubTopic:
AppKit
Tags: