objcjs-types 0.4.0 → 0.5.0

package/dist/AppKit/NSWritingToolsCoordinatorDelegate.d.ts

@@ -1,9 +1,11 @@
-import type { NobjcObject } from "objc-js";
+import type { _NSTextPreview } from "./NSTextPreview.js";
+import type { _NSView } from "./NSView.js";
 import type { _NSWritingToolsCoordinator } from "./NSWritingToolsCoordinator.js";
 import type { _NSWritingToolsCoordinatorAnimationParameters } from "./NSWritingToolsCoordinatorAnimationParameters.js";
 import type { _NSWritingToolsCoordinatorContext } from "./NSWritingToolsCoordinatorContext.js";
 import type { _NSArray } from "../Foundation/NSArray.js";
 import type { _NSAttributedString } from "../Foundation/NSAttributedString.js";
+import type { _NSUUID } from "../Foundation/NSUUID.js";
 import type { CGPoint } from "../structs/CGPoint.js";
 import type { CGRect } from "../structs/CGRect.js";
 import type { NSRange } from "../structs/NSRange.js";
@@ -15,54 +17,54 @@ export interface _NSWritingToolsCoordinatorDelegate {
     /**
      * Asks your delegate to provide the text to evaluate during the Writing Tools operation. - Parameters: - writingToolsCoordinator: The coordinator object requesting information from your custom view. - scope: The amount of text the coordinator requested. Use this property to determine if Writing Tools is evaluating all of your text or only a subset. - completion: A completion block to execute with the required information. You must execute this block once at end of your method's implementation. The block has no return value and takes an array of ``NSWritingToolsCoordinator/Context`` objects that contain the requested information. At the start of every operation, the ``NSWritingToolsCoordinator`` object calls this method to request the text to evaluate. Use this method to create one or more ``NSWritingToolsCoordinator/Context`` objects with your view’s text. Create only one ``NSWritingToolsCoordinator/Context`` object if your view has only one text storage object. If your view contains multiple text storage objects, create separate ``NSWritingToolsCoordinator/Context`` objects for each text storage object. Writing Tools returns updates for each context object separately, making it easier for you to incorporate changes into the correct text storage object. Don’t create multiple context objects if your view has only one text storage object. The `scope` parameter tells you what content Writing Tools expects you to provide in your context object. For example, Writing Tools expects you to provide the selected text when the parameter contains the ``NSWritingToolsCoordinator/ContextScope/userSelection`` option. When Writing Tools requests a subset of your overall text, include some of the surrounding text in your context object too. Writing Tools can use the extra text you provide to improve the results of its evaluation. For example, it might use an entire paragraph, instead of only the selected sentence, to evaluate ways to rewrite that sentence. It’s best to include the text up to the nearest paragraph boundary before and after the selection. If you include extra text in your context object, set the ``NSWritingToolsCoordinator/Context/range`` property to the range of the selected text. > Note: When a context object stores only a subset of your view’s text, record additional information to map the location of that text to the correct location in your view’s text storage. Keep that information up-to-date throughout the Writing Tools session. Pass the context objects you create to the provided completion handler before your method returns. Writing Tools waits for you to call the completion handler before proceeding with the operation.
      */
-    writingToolsCoordinator$requestsContextsForScope$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, scope: NSWritingToolsCoordinatorContextScope, completion: NobjcObject): void;
+    writingToolsCoordinator$requestsContextsForScope$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, scope: NSWritingToolsCoordinatorContextScope, completion: (arg0: _NSArray) => void): void;
     /**
      * Tells the delegate that there are text changes to incorporate into the view. - Parameters: - writingToolsCoordinator: The coordinator object providing the changes to your custom view. - range: A range of text to update. This range is relative to the text in your context object, and it’s your responsibility to match that location to the correct location in your text storage. If you initialized the context object with the entire contents of your view’s text storage, you can use `range` as-is to access that text storage. However, if you initialized the context object with only a portion of your view’s text, add the starting location of your context object’s text to this value to get the correct range for that text storage. - context: The context object that contains the original text to modify. Use this object to locate the correct text storage object for your view. - replacementText: The text to insert in place of the current text at `range`. You can insert this text as-is, insert a modified version of this string, or reject the replacement text altogether. - reason: The type of replacement Writing Tools performs. This parameter indicates whether Writing Tools is replacing the text with or without animations. - animationParameters: The animation parameters for any interactive changes, or `nil` if the changes aren’t interactive. Use this object to create any additional animations for the system to run alongside the changes Writing Tools makes. For example, use it to update other views that contain related information. - completion: A completion handler to execute with the results of the operation. The handler has no return value and takes an optional attributed string as a parameter. If you incorporate the replacement text, either as-is or with modifications, pass the actual string you incorporated to the completion block. If you reject the suggested change and leave the original text unchanged, specify `nil` for this parameter. Use this method to update your view’s text storage with the proposed changes. Writing Tools can call this method multiple times during the course of a session to notify you of changes to different ranges of text. Incorporate the changes into your view’s text storage and notify your layout manager so it can refresh the view. > Important: When integrating changes, remember to update `range.location` as needed to get the correct location in your view’s text storage. Remove the text in the appropriate range of your text storage, and replace it with the contents of `replacementText`. When you finish, call the completion handler and pass in the replacement text you inserted. If you change the string in `replacementText` before incorporating it into your text storage, return your modified string instead. Returning the string lets Writing Tools track any alterations you made to it. You can also pass `nil` to the completion handler if you don’t incorporate the replacement text. For interactive changes, Writing Tools works with your delegate to animate the removal of the old text and the insertion of any replacement text. If you need to modify other parts of your interface to reflect the changes, use the provided ``NSWritingToolsCoordinator/AnimationParameters`` object to create additional animations to run at the same time as the system-provided animations.
      */
-    writingToolsCoordinator$replaceRange$inContext$proposedText$reason$animationParameters$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, range: NSRange, context: _NSWritingToolsCoordinatorContext, replacementText: _NSAttributedString, reason: NSWritingToolsCoordinatorTextReplacementReason, animationParameters: _NSWritingToolsCoordinatorAnimationParameters | null, completion: NobjcObject | null): void;
+    writingToolsCoordinator$replaceRange$inContext$proposedText$reason$animationParameters$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, range: NSRange, context: _NSWritingToolsCoordinatorContext, replacementText: _NSAttributedString, reason: NSWritingToolsCoordinatorTextReplacementReason, animationParameters: _NSWritingToolsCoordinatorAnimationParameters | null, completion: ((attributedString: _NSAttributedString) => void) | null): void;
     /**
      * Asks the delegate to update your view’s current text selection. - Parameters: - writingToolsCoordinator: The coordinator object making the change to your view. - ranges: One or more ranges of text to select. Each range is relative to the text in your context object, and it’s your responsibility to match each location to the correct location in your text storage. If you initialized the context object with the entire contents of your view’s text storage, you can use the ranges as-is to access that text storage. However, if you initialized the context object with only a portion of your view’s text, add the starting location of your context object’s text to each value to get the correct range for that text storage. - context: The context object you use to identify the associated text storage. - completion: The completion handler to execute when your delegate finishes updating the selection. The handler has no parameters or return value. You must call this handler at some point during the implementation of your method. As Writing Tools suggests changes to your view’s text, it calls this method to update the text selection accordingly. Use this method to update the current selection in your view’s text storage. When you finish making the changes, call the provided completion block to let Writing Tools know you’re finished.
      */
-    writingToolsCoordinator$selectRanges$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, ranges: _NSArray, context: _NSWritingToolsCoordinatorContext, completion: NobjcObject): void;
+    writingToolsCoordinator$selectRanges$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, ranges: _NSArray, context: _NSWritingToolsCoordinatorContext, completion: () => void): void;
     /**
      * Asks the delegate to provide the bounding paths for the specified text in your view. - Parameters: - writingToolsCoordinator: The coordinator object requesting information from your custom view. - range: The range of text to evaluate. This range is relative to the text in your context object, and it’s your responsibility to match that location to the correct location in your text storage. If you initialized the context object with the entire contents of your view’s text storage, you can use `range` as-is to access that text storage. However, if you initialized the context object with only a portion of your view’s text, add the starting location of your context object’s text to this value to get the correct range for that text storage. - context: The context object with the target text. Use this object to find the text in your view’s text storage. - completion: A handler to execute with the required information. The handler has no return value and takes an array of Bezier paths as a parameter. You must call this handler at some point during your method’s implementation. After applying proofreading marks to your view’s text, Writing Tools lets the person accept or reject individual suggestions. To facilitate interactions, the coordinator asks your delegate to provide one or more Bezier paths that surround those proofreading suggestions. For each distinct range of text with a suggestion, it calls this method to get the Bezier paths that surround the corresponding text. After you determine the location of the specified range of text in your view’s text storage, find the rectangle around that text. If you're using TextKit, call the <doc://com.apple.documentation/documentation/uikit/nstextlayoutmanager/3809995-enumeratetextsegments> method of your view’s <doc://com.apple.documentation/documentation/uikit/nstextlayoutmanager> to compute the selection rectangles for that text. That method finds the text segments that contain the text and returns the frame rectangle for each one. Create a Bezier path for each rectangle, and convert the coordinates of each path to the coordinate space of the view in your coordinator's ``NSWritingToolsCoordinator/decorationContainerView`` property. Pass the resulting paths to the completion handler.
      */
-    writingToolsCoordinator$requestsBoundingBezierPathsForRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: NobjcObject): void;
+    writingToolsCoordinator$requestsBoundingBezierPathsForRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: (bezierPaths: _NSArray) => void): void;
     /**
      * Asks the delegate to provide an underline shape for the specified text during a proofreading session. - Parameters: - writingToolsCoordinator: The coordinator object requesting information from your custom view. - range: The range of text to evaluate. This range is relative to the text in your context object, and it’s your responsibility to match that location to the correct location in your text storage. If you initialized the context object with the entire contents of your view’s text storage, you can use `range` as-is to access that text storage. However, if you initialized the context object with only a portion of your view’s text, add the starting location of your context object’s text to this value to get the correct range for that text storage. - context: The context object with the target text. Use this object to find the text in your view’s text storage. - completion: A handler to execute with the required information. The handler has no return value and takes an array of Bezier paths as a parameter. You must call this handler at some point during your method’s implementation. When applying proofreading marks to your view’s content, the coordinator calls this method to retrieve a shape to draw under the specified text. You provide the shape using one or more Bezier paths, and the coordinator draws and animates that shape during the proofreading session. After you determine the location of the specified range of text in your view’s text storage, find the rectangle around that text. If you're using TextKit, you can call the <doc://com.apple.documentation/documentation/uikit/nstextlayoutmanager/3809995-enumeratetextsegments> method of your view’s <doc://com.apple.documentation/documentation/uikit/nstextlayoutmanager> to get the rectangles for a range of text. Convert the coordinates of each rectangle to the coordinate space of the view in your coordinator's ``NSWritingToolsCoordinator/decorationContainerView`` property. Use those rectangles to create the Bezier paths for your text. For example, you might create a path with a straight or wavy line at the bottom of the rectangle.
      */
-    writingToolsCoordinator$requestsUnderlinePathsForRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: NobjcObject): void;
+    writingToolsCoordinator$requestsUnderlinePathsForRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: (bezierPaths: _NSArray) => void): void;
     /**
      * Prepare for animations for the content that Writing Tools is evaluating. - Parameters: - writingToolsCoordinator: The coordinator object notifying you that animations are about to begin. - textAnimation: The type of animation Writing Tools is preparing. - range: The range of text affected by the animation. This range is relative to the text in your context object, and it’s your responsibility to match that location to the correct location in your text storage. If you initialized the context object with the entire contents of your view’s text storage, you can use `range` as-is to access that text storage. However, if you initialized the context object with only a portion of your view’s text, add the starting location of your context object’s text to this value to get the correct range for that text storage. - context: The context object that contains the original text. Use this object to fetch the current text, and to match that text to your underlying text storage. - completion: A completion handler to execute when you are done. The handler has no return value and takes no parameters. You must call this handler at some point during your implementation. During an interactive evaluation of your view’s text, Writing Tools creates different animations to provide feedback on what’s happening. For example, it creates an ``NSWritingToolsCoordinator/TextAnimation/anticipate`` animation to let people know the system is evaluating the text. The `textAnimation` parameter tells you what type of animation to prepare for. Use this method to prepare for the system-provided animations of your view’s content. For interactive animations, hide the text in the specified range temporarily while the system animations run. For non-interactive animations, dim the text for the duration of the animation to indicate it’s not editable. For animations to remove or insert text, you can also use this method to set up animations to reflow your view’s content to match the changes. At the end of a given animation, use your delegate’s ``writingToolsCoordinator(_:finish:for:in:completion:)`` method to undo any changes you make to your content. For a single animation type, the system calls this method, followed sequentially by the ``writingToolsCoordinator(_:previewFor:range:context:completion:)`` and ``writingToolsCoordinator(_:finish:for:in:completion:)`` methods. Each method executes asynchronously, but the system calls the next method in the sequence only after you call the completion handler of the previous method. However, multiple animations can run simultaneously, so check the `textAnimation` and `range` parameters to differentiate sequences.
      */
-    writingToolsCoordinator$prepareForTextAnimation$forRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, textAnimation: NSWritingToolsCoordinatorTextAnimation, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: NobjcObject): void;
+    writingToolsCoordinator$prepareForTextAnimation$forRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, textAnimation: NSWritingToolsCoordinatorTextAnimation, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: () => void): void;
     /**
      * Asks the delegate for a preview image and layout information for the specified text. - Parameters: - writingToolsCoordinator: The coordinator object notifying you that animations are about to begin. - textAnimation: The type of animation Writing Tools is preparing. - range: The range of text that requires a preview image. This range is relative to the text in your context object, and it’s your responsibility to match that location to the correct location in your text storage. If you initialized the context object with the entire contents of your view’s text storage, you can use `range` as-is to access that text storage. However, if you initialized the context object with only a portion of your view’s text, add the starting location of your context object’s text to this value to get the correct range for that text storage. - context: The context object that contains the original text. Use this object to fetch the current text, and to match that text to your underlying text storage. - completion: A completion handler to execute when you are done. The handler has no return value and takes an ``NSTextPreview`` object as a parameter. You must call this handler at some point during your implementation. During an interactive evaluation of your view’s text, Writing Tools creates different animations to provide feedback on what’s happening. As part of the preparation for those animations, Writing Tools asks you to provide a preview of the affected content in your view. Writing Tools uses this preview to build and execute the animations in the view stored in the ``NSWritingToolsCoordinator/effectContainerView`` property of the coordinator object. To build a preview of your content in macOS, render the specified range of text into an image with a transparent background and use that image to create your ``NSTextPreview`` object directly. Set the ``NSTextPreview/presentationFrame`` property to the rectangle in your view’s coordinate space that contains the text you captured. Set the ``NSTextPreview/candidateRects`` property to the selection rectangles for the text, which you get from your view’s layout manager. Writing Tools uses this information to place your image directly above the text in your view. For a single animation type, the system calls the ``writingToolsCoordinator(_:prepareFor:range:context:completion:)`` method, followed sequentially by this method and then the ``writingToolsCoordinator(_:finish:for:in:completion:)`` method. Each method executes asynchronously, but the system calls the next method in the sequence only after you call the completion handler of the previous method. However, multiple animations can run simultaneously, so check the `textAnimation` parameter to differentiate sequences.
      */
-    writingToolsCoordinator$requestsPreviewForTextAnimation$ofRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, textAnimation: NSWritingToolsCoordinatorTextAnimation, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: NobjcObject | null): void;
+    writingToolsCoordinator$requestsPreviewForTextAnimation$ofRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, textAnimation: NSWritingToolsCoordinatorTextAnimation, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: ((textPreviews: _NSArray) => void) | null): void;
     /**
      * Asks the delegate for a preview image and layout information for the specified text. - Parameters: - writingToolsCoordinator: The coordinator object notifying you that animations are about to begin. - rect: The portion of your view that contains the requested text. This rectangle is in the view’s coordinate system. - context: The context object that contains the original text. Use this object to fetch the current text, and to match that text to your underlying text storage. - completion: A completion handler to execute when you are done. The handler has no return value and takes an ``NSTextPreview`` object as a parameter. You must call this handler at some point during your implementation. During an interactive evaluation of your view’s text, Writing Tools creates different animations to provide feedback on what’s happening. As part of the preparation for those animations, Writing Tools asks you to provide a preview of the affected content in your view. Writing Tools uses this preview to build and execute the animations in the view stored in the ``NSWritingToolsCoordinator/effectContainerView`` property of the coordinator object. To build a preview of your content in macOS, render the requested portion of your view into an image with a transparent background and use that image to create your ``NSTextPreview`` object directly. Set the ``NSTextPreview/presentationFrame`` property to the specified rectangle. Set the ``NSTextPreview/candidateRects`` property to the selection rectangles for the associated text, which you get from your view’s layout manager. Writing Tools uses this information to place your image directly above the text in your view. For a single animation type, the system calls the ``writingToolsCoordinator(_:prepareFor:range:context:completion:)`` method, followed sequentially by this method and then the ``writingToolsCoordinator(_:finish:for:in:completion:)`` method. Each method executes asynchronously, but the system calls the next method in the sequence only after you call the completion handler of the previous method. However, multiple animations can run simultaneously, so check the `textAnimation` parameter to differentiate sequences.
      */
-    writingToolsCoordinator$requestsPreviewForRect$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, rect: CGRect, context: _NSWritingToolsCoordinatorContext, completion: NobjcObject | null): void;
+    writingToolsCoordinator$requestsPreviewForRect$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, rect: CGRect, context: _NSWritingToolsCoordinatorContext, completion: ((textPreview: _NSTextPreview) => void) | null): void;
     /**
      * Asks the delegate to clean up any state related to the specified Writing Tools animation. - Parameters: - writingToolsCoordinator: The coordinator object notifying you that animations are about to begin. - textAnimation: The type of animation Writing Tools finished. - range: The range of text that finished animating. This range is relative to the text in your context object, and it’s your responsibility to match that location to the correct location in your text storage. If you initialized the context object with the entire contents of your view’s text storage, you can use `range` as-is to access that text storage. However, if you initialized the context object with only a portion of your view’s text, add the starting location of your context object’s text to this value to get the correct range for that text storage. - context: The context object that contains the original text. - completion: A completion handler to execute when you are done. The handler has no return value and takes no parameters. You must call this handler at some point during your implementation. Use this method to clean up any data structures you created to support the specified type of Writing Tools animation. You can also use this method to restore the visibility of any text you hid previously. When you finish your cleanup work, call the completion handler to notify Writing Tools. Writing Tools calls this method only after previous calls to the ``writingToolsCoordinator(_:prepareFor:range:context:completion:)`` and ``writingToolsCoordinator(_:previewFor:range:context:completion:)`` methods for the same animation type. However, Writing Tools can interleave calls to this method with calls to prepare an animation of a different type. In your implementation of this method, make sure the actions you take don’t interfere with other in-flight animations.
      */
-    writingToolsCoordinator$finishTextAnimation$forRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, textAnimation: NSWritingToolsCoordinatorTextAnimation, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: NobjcObject): void;
+    writingToolsCoordinator$finishTextAnimation$forRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, textAnimation: NSWritingToolsCoordinatorTextAnimation, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: () => void): void;
     /**
      * Asks the delegate to divide the specified range of text into the separate containers that render that text. - Parameters: - writingToolsCoordinator: The coordinator object requesting information from your custom view. - range: The range of text to consider in the specified `context` object. The location value of this range is relative to the beginning of the text in your context object, and it’s your responsibility to match that location to the correct location in your text storage. If you initialized the context object with the entire contents of your view’s text storage, you can use `range` as-is to access that text storage. However, if you initialized the context object with only a portion of your view’s text, add the starting location of your context object’s text to this value to get the correct range for that text storage. - context: The context object that contains the text to consider. Use this object to locate the appropriate text storage object for your view. - completion: A completion handler to execute when you are done. The handler has no return value and takes an array of <doc://com.apple.documentation/documentation/foundation/nsvalue> types, each of which contains an <doc://com.apple.documentation/documentation/foundation/nsrange>. The union of the ranges you pass to this handler must equal all of the text in `range`. The order of the ranges in the array must be sequential, with each new range's starting location coming after the previous one. There must also not be any gaps or overlap between ranges. You must call this handler at some point during your implementation. If your view uses multiple ``NSTextContainer`` objects to draw text in different regions, use this method to tell Writing Tools about the containers that display the specified text. In your implementation, subdivide `range` to create one new range for each portion of text that resides in a different container object. For example, if the text in `range` is split between two containers, provide two new <doc://com.apple.documentation/documentation/foundation/nsrange> types that reflect the portion of the total text in each container. If `range` resides completely within one container, call the completion handler with `range` as the only value in the array. When configuring animations for your view, Writing Tools asks your delegate to provide separate previews for each of your view’s container object. Specifically, it calls your delegate’s ``writingToolsCoordinator(_:previewFor:range:context:completion:)`` method separately for each range of text you return in the completion handler. Your implementation of that method must create a preview suitable for animating the content from the underlying text container.
      */
-    writingToolsCoordinator$requestsSingleContainerSubrangesOfRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: NobjcObject): void;
+    writingToolsCoordinator$requestsSingleContainerSubrangesOfRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: (arg0: _NSArray) => void): void;
     /**
      * Asks the delegate to provide a decoration view for the specified range of text. - Parameters: - writingToolsCoordinator: The coordinator object requesting information from your custom view. - range: The range of text to consider in the specified `context` object. The location value of this range is relative to the beginning of the text in your context object, and it’s your responsibility to match that location to the correct location in your text storage. If you initialized the context object with the entire contents of your view’s text storage, you can use `range` as-is to access that text storage. However, if you initialized the context object with only a portion of your view’s text, add the starting location of your context object’s text to this value to get the correct range for that text storage. - context: The context object that contains the text to consider. Use this object to locate the appropriate text storage object for your view. - completion: A completion handler to execute when you are done. The handler has no return value and takes an ``NSView`` object as a parameter. You must call this handler at some point during your implementation. If your view uses multiple ``NSTextContainer`` objects to draw text in different regions, use this method to provide Writing Tools with the view to use for the specified range of text. After calling your delegate’s ``writingToolsCoordinator(_:singleContainerSubrangesOf:in:)`` method, Writing Tools calls this method for each subrange of text you provided. Find or provide a view situated visibly below the specified text in your text view. It's also satisfactory to provide a view that’s visually in front of the text. Writing Tools uses the provided view to host any proofreading marks for the specified range of text. If your view has only one text container, use the coordinator’s ``NSWritingToolsCoordinator/decorationContainerView`` property to specify the view to use for proofreading marks.
      */
-    writingToolsCoordinator$requestsDecorationContainerViewForRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: NobjcObject): void;
+    writingToolsCoordinator$requestsDecorationContainerViewForRange$inContext$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, range: NSRange, context: _NSWritingToolsCoordinatorContext, completion: (arg0: _NSView) => void): void;
     /**
      * Notifies your delegate of relevant state changes when Writing Tools is running in your view. - Parameters: - writingToolsCoordinator: The coordinator object providing information to your custom view. - state: The new state for the Writing Tools session. For information about the possible states, see ``NSWritingToolsCoordinator/State``. - text: The current text for your context object. - reason: The reason for the state change. - context: The context object that contains the original text for Writing Tools to evaluate. - completion: A handler to execute when your delegate finishes processing the change of state. The handler has no parameters or return value. You must call this handler at some point during the implementation of your method. Use state transitions to perform actions related to your view or text storage. When Writing Tools is active, it updates its state to indicate what task it’s currently performing. Writing Tools starts in the ``NSWritingToolsCoordinator/State/inactive`` state and moves to other states as it presents UI and starts interacting with your view’s content. For example, it moves to the ``NSWritingToolsCoordinator/State/interactiveUpdating`` state when it’s making changes to your view’s text storage.
      */
-    writingToolsCoordinator$willChangeToState$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, newState: NSWritingToolsCoordinatorState, completion: NobjcObject): void;
+    writingToolsCoordinator$willChangeToState$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, newState: NSWritingToolsCoordinatorState, completion: () => void): void;
     /**
      * Asks the delegate to provide the location of the character at the specified point in your view’s coordinate system. - Parameters: - writingToolsCoordinator: The coordinator object requesting information from your custom view. - point: A point in your view’s coordinate space. Find the location of the text under this point, if any. - completion: A handler to execute with the required information. This handler has no return value and takes an <doc://com.apple.documentation/documentation/foundation/nsrange> and <doc://com.apple.documentation/documentation/foundation/uuid> as parameters. Set the range to the character’s location in one of your ``NSWritingToolsCoordinator/Context`` objects, which you specify using the <doc://com.apple.documentation/documentation/foundation/uuid> parameter. You must call this handler at some point during your method’s implementation. When someone interacts with your view during a proofreading operation, Writing Tools calls this method to get the location of the interaction. If the interaction occurs in the text of one of your ``NSWritingToolsCoordinator/Context`` objects, configure an <doc://com.apple.documentation/documentation/foundation/nsrange> with the character’s location in that context object and a length of `1`. If the interaction occurs outside of the text of your context objects, configure the range with a location of `NSNotFound`. When specifying the location of a character in your context object, provide a location relative to the start of your context object’s text. The first character in a context object’s text is always at location `0`, and it’s your responsibility to track the location of the context object’s text in your text storage object. When the context object’s text begins in the middle of your text storage, subtract the starting location of the context object’s text from the location you specify in your range value. For example, if the context object’s text starts at character `100` in your text storage, and an interaction occurs with the character at location `102`, specify a range with a location of `2` and a length of `1`.
      * @deprecated In macOS 15.4 and later, NSWritingToolsCoordinator automatically determines the location of the character at the specified point in your view's coordinate system and no longer calls this method.
      */
-    writingToolsCoordinator$requestsRangeInContextWithIdentifierForPoint$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, point: CGPoint, completion: NobjcObject): void;
+    writingToolsCoordinator$requestsRangeInContextWithIdentifierForPoint$completion$?(writingToolsCoordinator: _NSWritingToolsCoordinator, point: CGPoint, completion: (range: NSRange, contextID: _NSUUID) => void): void;
 }

package/dist/AppKit/index.d.ts

@@ -1295,10 +1295,12 @@ export { NSCompositingOperation } from "./NSCompositingOperation.js";
 export { NSControlBorderShape } from "./NSControlBorderShape.js";
 export { NSControlCharacterAction } from "./NSControlCharacterAction.js";
 export { NSControlSize } from "./NSControlSize.js";
+export { NSControlStateValue } from "./NSControlStateValue.js";
 export { NSControlTint } from "./NSControlTint.js";
 export { NSCorrectionIndicatorType } from "./NSCorrectionIndicatorType.js";
 export { NSCorrectionResponse } from "./NSCorrectionResponse.js";
 export { NSCursorFrameResizeDirections } from "./NSCursorFrameResizeDirections.js";
+export { NSCursorFrameResizePosition } from "./NSCursorFrameResizePosition.js";
 export { NSDatePickerElementFlags } from "./NSDatePickerElementFlags.js";
 export { NSDatePickerMode } from "./NSDatePickerMode.js";
 export { NSDatePickerStyle } from "./NSDatePickerStyle.js";
@@ -1371,6 +1373,7 @@ export { NSMenuItemBadgeType } from "./NSMenuItemBadgeType.js";
 export { NSMenuPresentationStyle } from "./NSMenuPresentationStyle.js";
 export { NSMenuProperties } from "./NSMenuProperties.js";
 export { NSMenuSelectionMode } from "./NSMenuSelectionMode.js";
+export { NSModalResponse } from "./NSModalResponse.js";
 export { NSMultibyteGlyphPacking } from "./NSMultibyteGlyphPacking.js";
 export { NSOpenGLContextParameter } from "./NSOpenGLContextParameter.js";
 export { NSOpenGLGlobalOption } from "./NSOpenGLGlobalOption.js";
@@ -1492,6 +1495,7 @@ export { NSToolbarDisplayMode } from "./NSToolbarDisplayMode.js";
 export { NSToolbarItemGroupControlRepresentation } from "./NSToolbarItemGroupControlRepresentation.js";
 export { NSToolbarItemGroupSelectionMode } from "./NSToolbarItemGroupSelectionMode.js";
 export { NSToolbarItemStyle } from "./NSToolbarItemStyle.js";
+export { NSToolbarItemVisibilityPriority } from "./NSToolbarItemVisibilityPriority.js";
 export { NSToolbarSizeMode } from "./NSToolbarSizeMode.js";
 export { NSTouchPhase } from "./NSTouchPhase.js";
 export { NSTouchType } from "./NSTouchType.js";
@@ -1517,6 +1521,7 @@ export { NSWindowBackingLocation } from "./NSWindowBackingLocation.js";
 export { NSWindowButton } from "./NSWindowButton.js";
 export { NSWindowCollectionBehavior } from "./NSWindowCollectionBehavior.js";
 export { NSWindowDepth } from "./NSWindowDepth.js";
+export { NSWindowLevel } from "./NSWindowLevel.js";
 export { NSWindowListOptions } from "./NSWindowListOptions.js";
 export { NSWindowNumberListOptions } from "./NSWindowNumberListOptions.js";
 export { NSWindowOcclusionState } from "./NSWindowOcclusionState.js";

package/dist/AppKit/index.js

@@ -375,10 +375,12 @@ export { NSCompositingOperation } from "./NSCompositingOperation.js";
 export { NSControlBorderShape } from "./NSControlBorderShape.js";
 export { NSControlCharacterAction } from "./NSControlCharacterAction.js";
 export { NSControlSize } from "./NSControlSize.js";
+export { NSControlStateValue } from "./NSControlStateValue.js";
 export { NSControlTint } from "./NSControlTint.js";
 export { NSCorrectionIndicatorType } from "./NSCorrectionIndicatorType.js";
 export { NSCorrectionResponse } from "./NSCorrectionResponse.js";
 export { NSCursorFrameResizeDirections } from "./NSCursorFrameResizeDirections.js";
+export { NSCursorFrameResizePosition } from "./NSCursorFrameResizePosition.js";
 export { NSDatePickerElementFlags } from "./NSDatePickerElementFlags.js";
 export { NSDatePickerMode } from "./NSDatePickerMode.js";
 export { NSDatePickerStyle } from "./NSDatePickerStyle.js";
@@ -451,6 +453,7 @@ export { NSMenuItemBadgeType } from "./NSMenuItemBadgeType.js";
 export { NSMenuPresentationStyle } from "./NSMenuPresentationStyle.js";
 export { NSMenuProperties } from "./NSMenuProperties.js";
 export { NSMenuSelectionMode } from "./NSMenuSelectionMode.js";
+export { NSModalResponse } from "./NSModalResponse.js";
 export { NSMultibyteGlyphPacking } from "./NSMultibyteGlyphPacking.js";
 export { NSOpenGLContextParameter } from "./NSOpenGLContextParameter.js";
 export { NSOpenGLGlobalOption } from "./NSOpenGLGlobalOption.js";
@@ -572,6 +575,7 @@ export { NSToolbarDisplayMode } from "./NSToolbarDisplayMode.js";
 export { NSToolbarItemGroupControlRepresentation } from "./NSToolbarItemGroupControlRepresentation.js";
 export { NSToolbarItemGroupSelectionMode } from "./NSToolbarItemGroupSelectionMode.js";
 export { NSToolbarItemStyle } from "./NSToolbarItemStyle.js";
+export { NSToolbarItemVisibilityPriority } from "./NSToolbarItemVisibilityPriority.js";
 export { NSToolbarSizeMode } from "./NSToolbarSizeMode.js";
 export { NSTouchPhase } from "./NSTouchPhase.js";
 export { NSTouchType } from "./NSTouchType.js";
@@ -597,6 +601,7 @@ export { NSWindowBackingLocation } from "./NSWindowBackingLocation.js";
 export { NSWindowButton } from "./NSWindowButton.js";
 export { NSWindowCollectionBehavior } from "./NSWindowCollectionBehavior.js";
 export { NSWindowDepth } from "./NSWindowDepth.js";
+export { NSWindowLevel } from "./NSWindowLevel.js";
 export { NSWindowListOptions } from "./NSWindowListOptions.js";
 export { NSWindowNumberListOptions } from "./NSWindowNumberListOptions.js";
 export { NSWindowOcclusionState } from "./NSWindowOcclusionState.js";

package/dist/AppTrackingTransparency/ATTrackingManager.d.ts

@@ -1,4 +1,3 @@
-import type { NobjcObject } from "objc-js";
 import type { _NSObject } from "../Foundation/NSObject.js";
 import type { ATTrackingManagerAuthorizationStatus } from "./ATTrackingManagerAuthorizationStatus.js";
 export declare class _ATTrackingManager extends _NSObject {
@@ -8,7 +7,7 @@ export declare class _ATTrackingManager extends _NSObject {
     /**
      * The request for user authorization to access app-related data. The ``ATTrackingManager/requestTrackingAuthorizationWithCompletionHandler:`` is a one-time request to authorize or deny access to app-related data that can be used for tracking the user or the device. The system remembers the user’s choice and doesn’t prompt again unless a user uninstalls and then reinstalls the app on the device. Calls to the API only prompt when the application state is `UIApplicationStateActive`. The authorization prompt doesn’t display if another permission request is pending user confirmation. Concurrent requests aren’t preserved by iOS, and calls to the API through an app extension don’t prompt. Check the ``ATTrackingManager/trackingAuthorizationStatus`` for a status of ``ATTrackingManagerAuthorizationStatus/ATTrackingManagerAuthorizationStatusNotDetermined`` to determine if you need to make an additional call. The completion handler will be called with the result of the user's decision for granting or denying permission to use application tracking. The completion handler will be called immediately if access to request authorization is restricted. - Important: To use ``ATTrackingManager/requestTrackingAuthorizationWithCompletionHandler:``, the <doc ://com.apple.documentation/documentation/bundleresources/information_property_list/NSUserTrackingUsageDescription> key must be in the <doc ://com.apple.documentation/documentation/bundleresources/information_property_list>.
      */
-    static requestTrackingAuthorizationWithCompletionHandler$(completion: NobjcObject): void;
+    static requestTrackingAuthorizationWithCompletionHandler$(completion: (status: ATTrackingManagerAuthorizationStatus) => void): void;
     /**
      * The authorization status that is current for the calling application. If the user has not yet been prompted to approve access, the return value will either be ``ATTrackingManagerAuthorizationStatusNotDetermined``, or ``ATTrackingManagerAuthorizationStatusRestricted`` if this value is managed. Once the user has been prompted, the return value will be either ``ATTrackingManagerAuthorizationStatusDenied`` or ``ATTrackingManagerAuthorizationStatusAuthorized``. Use the ``ATTrackingManager/trackingAuthorizationStatus`` property to check authorization status. - Returns: Information about your application’s tracking authorization status. Users are able to grant or deny developers tracking privileges on a per-app basis. Application developers must call `requestTrackingAuthorizationWithCompletionHandler:` for the ability to track users.
      */

package/dist/AudioToolbox/AUAudioUnit.d.ts

@@ -1,6 +1,7 @@
 import type { NobjcObject } from "objc-js";
 import type { _NSArray } from "../Foundation/NSArray.js";
 import type { _NSDictionary } from "../Foundation/NSDictionary.js";
+import type { _NSError } from "../Foundation/NSError.js";
 import type { _NSObject } from "../Foundation/NSObject.js";
 import type { _NSString } from "../Foundation/NSString.js";
 import type { _AUAudioUnitBus } from "./AUAudioUnitBus.js";
@@ -19,7 +20,7 @@ export declare class _AUAudioUnit extends _NSObject {
     /**
      * @method instantiateWithComponentDescription:options:completionHandler: @brief Asynchronously create an AUAudioUnit instance. @param componentDescription The AudioComponentDescription of the audio unit to instantiate. @param options See the discussion of AudioComponentInstantiationOptions in AudioToolbox/AudioComponent.h. @param completionHandler Called in a thread/dispatch queue context internal to the implementation. The client should retain the supplied AUAudioUnit. @discussion Certain types of AUAudioUnits must be instantiated asynchronously -- see the discussion of kAudioComponentFlag_RequiresAsyncInstantiation in AudioToolbox/AudioComponent.h. Note: Do not block the main thread while waiting for the completion handler to be called; this can deadlock.
      */
-    static instantiateWithComponentDescription$options$completionHandler$(componentDescription: AudioComponentDescription, options: NobjcObject, completionHandler: NobjcObject | null): void;
+    static instantiateWithComponentDescription$options$completionHandler$(componentDescription: AudioComponentDescription, options: NobjcObject, completionHandler: ((audioUnit: _AUAudioUnit, error: _NSError) => void) | null): void;
     /**
      * @brief Register an audio unit component implemented as an AUAudioUnit subclass. @discussion This method dynamically registers the supplied AUAudioUnit subclass with the Audio Component system, in the context of the current process (only). After registering the subclass, it can be instantiated via AudioComponentInstanceNew, -[AUAudioUnit initWithComponentDescription:options:error:], and via any other API's which instantiate audio units via their component descriptions (e.g. <AudioToolbox/AUGraph.h>, or <AVFoundation/AVAudioUnitEffect.h>).
      */
@@ -47,7 +48,7 @@ export declare class _AUAudioUnit extends _NSObject {
     /**
      * @method tokenByAddingRenderObserver: @brief Add a block to be called on each render cycle. @discussion The supplied block is called at the beginning and ending of each render cycle. It should not make any blocking calls. This method is implemented in the base class AUAudioUnit, and should not be overridden. Bridged to the v2 API AudioUnitAddRenderNotify(). @param observer The block to call. @return A token to be used when removing the observer.
      */
-    tokenByAddingRenderObserver$(observer: NobjcObject): number;
+    tokenByAddingRenderObserver$(observer: (arg0: NobjcObject, arg1: NobjcObject, arg2: number, arg3: number) => void): number;
     /**
      * @method removeRenderObserver: @brief Remove an observer block added via tokenByAddingRenderObserver: @param token The token previously returned by tokenByAddingRenderObserver: Bridged to the v2 API AudioUnitRemoveRenderNotify().
      */
@@ -139,11 +140,11 @@ export declare class _AUAudioUnit extends _NSObject {
     /**
      * @property renderBlock @brief Block which hosts use to ask the unit to render. @discussion Before invoking an audio unit's rendering functionality, a host should fetch this block and cache the result. The block can then be called from a realtime context without the possibility of blocking and causing an overload at the Core Audio HAL level. This block will call a subclass' internalRenderBlock, providing all realtime events scheduled for the current render time interval, bracketed by calls to any render observers. Subclassers should override internalRenderBlock, not this property. Bridged to the v2 API AudioUnitRender().
      */
-    renderBlock(): NobjcObject;
+    renderBlock(): (arg0: NobjcObject, arg1: NobjcObject, arg2: number, arg3: number, arg4: NobjcObject, arg5: (arg0: NobjcObject, arg1: NobjcObject, arg2: number, arg3: number, arg4: NobjcObject) => number) => number;
     /**
      * @property scheduleParameterBlock @brief Block which hosts use to schedule parameters. @discussion As with renderBlock, a host should fetch and cache this block before calling allocateRenderResources, if it intends to schedule parameters. The block is safe to call from any thread context, including realtime audio render threads. Subclassers should not override this; it is implemented in the base class and will schedule the events to be provided to the internalRenderBlock. Bridged to the v2 API AudioUnitScheduleParameters().
      */
-    scheduleParameterBlock(): NobjcObject;
+    scheduleParameterBlock(): (arg0: number, arg1: number, arg2: number, arg3: number) => void;
     /**
      * @property maximumFramesToRender @brief The maximum number of frames which the audio unit can render at once. @discussion This must be set by the host before render resources are allocated. It cannot be changed while render resources are allocated. Bridged to the v2 property kAudioUnitProperty_MaximumFramesPerSlice.
      */
@@ -167,11 +168,11 @@ export declare class _AUAudioUnit extends _NSObject {
     /**
      * @property scheduleMIDIEventBlock @brief Block used to schedule MIDI events. @discussion As with renderBlock, a host should fetch and cache this block before calling allocateRenderResources if it intends to schedule MIDI events. This is implemented in the base class. It is nil when musicDeviceOrEffect is NO. Subclasses should not override. When hosts schedule events via this block, they are sent to the Audio Unit via the list of AURenderEvents delivered to internalRenderBlock. All events sent via this block will be delivered to the internalRenderBlock in the MIDI protocol returned by the AudioUnitMIDIProtocol property. For example, if AudioUnitMIDIProtocol returns kMIDIProtocol_2_0, incoming events will be translated to MIDI 2.0 if necessary. If AudioUnitMIDIProtocol is not set, events will be delivered as legacy MIDI. This bridged to the v2 API MusicDeviceMIDIEvent.
      */
-    scheduleMIDIEventBlock(): NobjcObject | null;
+    scheduleMIDIEventBlock(): ((arg0: number, arg1: number, arg2: number, arg3: NobjcObject) => void) | null;
     /**
      * @property scheduleMIDIEventListBlock @brief Block used to schedule MIDIEventLists. @discussion As with renderBlock, a host should fetch and cache this block before calling allocateRenderResources, if it intends to schedule MIDI events. When scheduling events during the render cycle (e.g. via a render observer) eventSampleTime can be AUEventSampleTimeImmediate plus an optional buffer offset, in which case the event is scheduled at the provided offset position within the current render cycle. This is implemented in the base class. It is nil when musicDeviceOrEffect is NO. Subclassers should not override. When hosts schedule events via this block, they are delivered to the Audio Unit via the list of AURenderEvents delivered to internalRenderBlock. All events sent via this block will be delivered to the internalRenderBlock in the MIDI protocol returned by the AudioUnitMIDIProtocol property. For example, if this block is called with MIDI-1.0 events but AudioUnitMIDIProtocol returns kMIDIProtocol_2_0, incoming events will be translated to MIDI 2.0. If AudioUnitMIDIProtocol is not set, events will be delivered as legacy MIDI. Note: This block should be preferred over scheduleMIDIEventBlock going forward. This bridged to the v2 API MusicDeviceMIDIEventList.
      */
-    scheduleMIDIEventListBlock(): NobjcObject;
+    scheduleMIDIEventListBlock(): (arg0: number, arg1: number, arg2: NobjcObject) => number;
     /**
      * @property MIDIOutputNames @brief Count, and names of, a plug-in's MIDI outputs. @discussion A plug-in may override this method to inform hosts about its MIDI outputs. The size of the array is the number of outputs the Audio Unit supports. Each item in the array is the name of the MIDI output at that index. This is bridged to the v2 API property kAudioUnitProperty_MIDIOutputCallbackInfo.
      */
@@ -183,13 +184,13 @@ export declare class _AUAudioUnit extends _NSObject {
     /**
      * @property MIDIOutputEventBlock @brief Block used by the host to access the MIDI output generated by an Audio Unit. @discussion The host can set this block and the plug-in can call it in its renderBlock to provide to the host the MIDI data associated with the current render cycle. All events sent via this block will be delivered to the host in the MIDI protocol returned by the hostMIDIProtocol property. For example, if hostMIDIProtocol is set to kMIDIProtocol_2_0, incoming events will be translated to MIDI 2.0. If hostMIDIProtocol is not set, events will be delivered as legacy MIDI. Note: AUMIDIEventListBlock should be preferred over this block going forward. This is bridged to the v2 API property kAudioUnitProperty_MIDIOutputCallback.
      */
-    MIDIOutputEventBlock(): NobjcObject | null;
-    setMIDIOutputEventBlock$(value: NobjcObject | null): void;
+    MIDIOutputEventBlock(): ((arg0: number, arg1: number, arg2: number, arg3: NobjcObject) => number) | null;
+    setMIDIOutputEventBlock$(value: ((arg0: number, arg1: number, arg2: number, arg3: NobjcObject) => number) | null): void;
     /**
      * @property MIDIOutputEventListBlock @brief Block used by the host to access the MIDIEventList output generated by an Audio Unit. @discussion The host can set this block and the plug-in can call it in its renderBlock to provide to the host the MIDIEventList data associated with the current render cycle. All events sent via this block will be delivered to the host in the MIDI protocol returned by the hostMIDIProtocol property. For example, if hostMIDIProtocol is set to kMIDIProtocol_2_0, incoming events will be translated to MIDI 2.0. If hostMIDIProtocol is not set, events will be delivered as legacy MIDI. Note: This block is cross-compatible with Audio Units using MIDIOutputEventBlock and should be preferred over MIDIOutputEventBlock by hosts going forward. The framework will provide the Audio Unit with both a MIDIOutputEventBlock and MIDIOutputEventListBlock, the Audio Unit is free to call either block as all messages will be translated as described above. Host should setup in the following order: - Set hostMIDIProtocol - Set MIDIOutputEventListBlock - Call allocateRenderResourcesAndReturnError This is bridged to the v2 API property kAudioUnitProperty_MIDIOutputEventListCallback.
      */
-    MIDIOutputEventListBlock(): NobjcObject;
-    setMIDIOutputEventListBlock$(value: NobjcObject): void;
+    MIDIOutputEventListBlock(): (arg0: number, arg1: number, arg2: NobjcObject) => number;
+    setMIDIOutputEventListBlock$(value: (arg0: number, arg1: number, arg2: NobjcObject) => number): void;
     /**
      * @property AudioUnitMIDIProtocol @brief The MIDI protocol used by the Audio Unit for receiving MIDIEventList data. @discussion Subclassers should override to return the desired protocol in which the Audio Unit wants to receive input MIDI data, otherwise the Audio Unit will default to receiving legacy MIDI. All translatable messages will be converted (if necessary) to this protocol prior to delivery to the Audio Unit. This is bridged to the v2 API property kAudioUnitProperty_AudioUnitMIDIProtocol.
      */
@@ -264,13 +265,13 @@ export declare class _AUAudioUnit extends _NSObject {
     /**
      * @property musicalContextBlock @brief A callback for the AU to call the host for musical context information. @discussion Note that an audio unit implementation accessing this property should cache it in realtime-safe storage before beginning to render. Bridged to the HostCallback_GetBeatAndTempo and HostCallback_GetMusicalTimeLocation callback members in kAudioUnitProperty_HostCallbacks.
      */
-    musicalContextBlock(): NobjcObject | null;
-    setMusicalContextBlock$(value: NobjcObject | null): void;
+    musicalContextBlock(): ((arg0: NobjcObject, arg1: NobjcObject, arg2: NobjcObject, arg3: NobjcObject, arg4: NobjcObject, arg5: NobjcObject) => boolean) | null;
+    setMusicalContextBlock$(value: ((arg0: NobjcObject, arg1: NobjcObject, arg2: NobjcObject, arg3: NobjcObject, arg4: NobjcObject, arg5: NobjcObject) => boolean) | null): void;
     /**
      * @property transportStateBlock @brief A callback for the AU to call the host for transport state information. @discussion Note that an audio unit implementation accessing this property should cache it in realtime-safe storage before beginning to render. Bridged to the HostCallback_GetTransportState and HostCallback_GetTransportState2 callback members in kAudioUnitProperty_HostCallbacks.
      */
-    transportStateBlock(): NobjcObject | null;
-    setTransportStateBlock$(value: NobjcObject | null): void;
+    transportStateBlock(): ((arg0: NobjcObject, arg1: NobjcObject, arg2: NobjcObject, arg3: NobjcObject) => boolean) | null;
+    setTransportStateBlock$(value: ((arg0: NobjcObject, arg1: NobjcObject, arg2: NobjcObject, arg3: NobjcObject) => boolean) | null): void;
     /**
      * @property contextName @brief Information about the host context in which the audio unit is connected, for display in the audio unit's view. @discussion For example, a host could set "track 3" as the context, so that the audio unit's view could then display to the user "My audio unit on track 3". Bridged to the v2 property kAudioUnitProperty_ContextName.
      */
@@ -311,13 +312,13 @@ export declare class _AUAudioUnit extends _NSObject {
     /**
      * @property outputProvider @brief The block that the output unit will call to get audio to send to the output. @discussion This block must be set if output is enabled.
      */
-    outputProvider(): NobjcObject | null;
-    setOutputProvider$(value: NobjcObject | null): void;
+    outputProvider(): ((arg0: NobjcObject, arg1: NobjcObject, arg2: number, arg3: number, arg4: NobjcObject) => number) | null;
+    setOutputProvider$(value: ((arg0: NobjcObject, arg1: NobjcObject, arg2: number, arg3: number, arg4: NobjcObject) => number) | null): void;
     /**
      * @property inputHandler @brief The block that the output unit will call to notify when input is available. @discussion See discussion for AUInputHandler.
      */
-    inputHandler(): NobjcObject | null;
-    setInputHandler$(value: NobjcObject | null): void;
+    inputHandler(): ((arg0: NobjcObject, arg1: NobjcObject, arg2: number, arg3: number) => void) | null;
+    setInputHandler$(value: ((arg0: NobjcObject, arg1: NobjcObject, arg2: number, arg3: number) => void) | null): void;
     /** @property device @brief Get the I/O hardware device. */
     deviceID(): number;
     /**
@@ -340,7 +341,7 @@ export declare class _AUAudioUnit extends _NSObject {
     intendedSpatialExperience(): NobjcObject;
     setIntendedSpatialExperience$(value: NobjcObject): void;
     /** Block which subclassers must provide (via a getter) to implement rendering. */
-    internalRenderBlock(): NobjcObject;
+    internalRenderBlock(): (arg0: NobjcObject, arg1: NobjcObject, arg2: number, arg3: number, arg4: NobjcObject, arg5: NobjcObject, arg6: (arg0: NobjcObject, arg1: NobjcObject, arg2: number, arg3: number, arg4: NobjcObject) => number) => number;
     /**
      * @property renderContextObserver @brief Block called by the OS when the rendering context changes. Audio Units which create auxiliary realtime rendering threads should implement this property to return a block which will be called by the OS when the render context changes. Audio Unit hosts must not attempt to interact with the AudioUnit through this block; it is for the exclusive use of the OS. See <AudioToolbox/AudioWorkInterval.h> for more information.
      */

package/dist/AudioToolbox/AUMessageChannel.d.ts

@@ -1,4 +1,3 @@
-import type { NobjcObject } from "objc-js";
 import type { _NSDictionary } from "../Foundation/NSDictionary.js";
 export interface _AUMessageChannel {
     /**
@@ -8,6 +7,6 @@ export interface _AUMessageChannel {
     /**
      * @property sendMessageToHostBlock @brief A callback for the AU to send a message to the host. @discussion The host has to set a block on this property.
      */
-    callHostBlock?(): NobjcObject | null;
-    setCallHostBlock$?(value: NobjcObject | null): void;
+    callHostBlock?(): ((arg0: _NSDictionary) => _NSDictionary) | null;
+    setCallHostBlock$?(value: ((arg0: _NSDictionary) => _NSDictionary) | null): void;
 }

package/dist/AudioToolbox/AUParameterNode.d.ts

@@ -1,6 +1,7 @@
 import type { NobjcObject } from "objc-js";
 import type { _NSObject } from "../Foundation/NSObject.js";
 import type { _NSString } from "../Foundation/NSString.js";
+import type { _AUParameter } from "./AUParameter.js";
 export declare class _AUParameterNode extends _NSObject {
     static alloc(): _AUParameterNode;
     static new(): _AUParameterNode;
@@ -12,15 +13,15 @@ export declare class _AUParameterNode extends _NSObject {
     /**
      * @method tokenByAddingParameterObserver: @brief Add an observer for a parameter or all parameters in a group/tree. @discussion An audio unit view can use an AUParameterObserver to be notified of changes to a single parameter, or to all parameters in a group/tree. These callbacks are throttled so as to limit the rate of redundant notifications in the case of frequent changes to a single parameter. This block is called in an arbitrary thread context. It is responsible for thread-safety. It must not make any calls to add or remove other observers, including itself; this will deadlock. An audio unit's implementation should interact with the parameter object via implementorValueObserver and implementorValueProvider. Parameter observers are bound to a specific parameter instance. If this parameter is destroyed, e.g. if the parameter tree is re-constructed, the previously set parameter observers will no longer be valid. Clients can observe changes to the parameter tree via KVO. See the discussion of -[AUAudioUnit parameterTree]. @param observer A block to call after the value of a parameter has changed. @return A token which can be passed to removeParameterObserver: or to -[AUParameter setValue:originator:]
      */
-    tokenByAddingParameterObserver$(observer: NobjcObject): NobjcObject;
+    tokenByAddingParameterObserver$(observer: (arg0: number, arg1: number) => void): NobjcObject;
     /**
      * @method tokenByAddingParameterRecordingObserver: @brief Add a recording observer for a parameter or all parameters in a group/tree. @discussion This is a variant of tokenByAddingParameterAutomationObserver where the callback receives AURecordedParameterEvents instead of AUParameterAutomationEvents. This will be deprecated in favor of tokenByAddingParameterAutomationObserver in a future release.
      */
-    tokenByAddingParameterRecordingObserver$(observer: NobjcObject): NobjcObject;
+    tokenByAddingParameterRecordingObserver$(observer: (arg0: number, arg1: NobjcObject) => void): NobjcObject;
     /**
      * @method tokenByAddingParameterAutomationObserver: @brief Add a recording observer for a parameter or all parameters in a group/tree. @discussion An audio unit host can use an AUParameterAutomationObserver or AUParameterRecordingObserver to capture a series of changes to a parameter value, including the timing of the events, as generated by a UI gesture in a view, for example. Unlike AUParameterObserver, these callbacks are not throttled. This block is called in an arbitrary thread context. It is responsible for thread-safety. It must not make any calls to add or remove other observers, including itself; this will deadlock. An audio unit's engine should interact with the parameter object via implementorValueObserver and implementorValueProvider. @param observer A block to call to record the changing of a parameter value. @return A token which can be passed to removeParameterObserver: or to -[AUParameter setValue:originator:]
      */
-    tokenByAddingParameterAutomationObserver$(observer: NobjcObject): NobjcObject;
+    tokenByAddingParameterAutomationObserver$(observer: (arg0: number, arg1: NobjcObject) => void): NobjcObject;
     /**
      * @method removeParameterObserver: @brief Remove an observer created with tokenByAddingParameterObserver, tokenByAddingParameterRecordingObserver, or tokenByAddingParameterAutomationObserver. @discussion This call will remove the callback corresponding to the supplied token. Note that this will block until any callbacks currently in flight have completed.
      */
@@ -38,22 +39,22 @@ export declare class _AUParameterNode extends _NSObject {
     /**
      * @brief Called when a parameter changes value. @discussion This block, used only in an audio unit implementation, receives all externally-generated changes to parameter values. It should store the new value in its audio signal processing state (assuming that that state is separate from the AUParameter object).
      */
-    implementorValueObserver(): NobjcObject;
-    setImplementorValueObserver$(value: NobjcObject): void;
+    implementorValueObserver(): (arg0: _AUParameter, arg1: number) => void;
+    setImplementorValueObserver$(value: (arg0: _AUParameter, arg1: number) => void): void;
     /**
      * @brief Called when a value of a parameter in the tree is known to have a stale value needing to be refreshed. @discussion The audio unit should return the current value for this parameter; the AUParameterNode will store the value.
      */
-    implementorValueProvider(): NobjcObject;
-    setImplementorValueProvider$(value: NobjcObject): void;
+    implementorValueProvider(): (arg0: _AUParameter) => number;
+    setImplementorValueProvider$(value: (arg0: _AUParameter) => number): void;
     /**
      * Called to provide string representations of parameter values. If value is nil, the callback uses the current value of the parameter.
      */
-    implementorStringFromValueCallback(): NobjcObject;
-    setImplementorStringFromValueCallback$(value: NobjcObject): void;
+    implementorStringFromValueCallback(): (arg0: _AUParameter, arg1: NobjcObject) => _NSString;
+    setImplementorStringFromValueCallback$(value: (arg0: _AUParameter, arg1: NobjcObject) => _NSString): void;
     /** Called to convert string to numeric representations of parameter values. */
-    implementorValueFromStringCallback(): NobjcObject;
-    setImplementorValueFromStringCallback$(value: NobjcObject): void;
+    implementorValueFromStringCallback(): (arg0: _AUParameter, arg1: _NSString) => number;
+    setImplementorValueFromStringCallback$(value: (arg0: _AUParameter, arg1: _NSString) => number): void;
     /** Called to obtain an abbreviated version of a parameter or group name. */
-    implementorDisplayNameWithLengthCallback(): NobjcObject;
-    setImplementorDisplayNameWithLengthCallback$(value: NobjcObject): void;
+    implementorDisplayNameWithLengthCallback(): (arg0: _AUParameterNode, arg1: number) => _NSString;
+    setImplementorDisplayNameWithLengthCallback$(value: (arg0: _AUParameterNode, arg1: number) => _NSString): void;
 }

package/dist/AudioToolbox/functions.d.ts

@@ -24,10 +24,10 @@ export declare function AudioComponentInstanceCanDo(inInstance: NobjcObject, inS
 export declare function AudioComponentInstanceDispose(inInstance: NobjcObject): number;
 export declare function AudioComponentInstanceGetComponent(inInstance: NobjcObject): NobjcObject;
 export declare function AudioComponentInstanceNew(inComponent: NobjcObject, outInstance: NobjcObject | null): number;
-export declare function AudioComponentInstantiate(inComponent: NobjcObject, inOptions: NobjcObject, inCompletionHandler: NobjcObject | null): void;
+export declare function AudioComponentInstantiate(inComponent: NobjcObject, inOptions: NobjcObject, inCompletionHandler: ((arg0: NobjcObject, arg1: number) => void) | null): void;
 export declare function AudioComponentRegister(inDesc: NobjcObject, inName: Uint8Array, inVersion: number, inFactory: NobjcObject): NobjcObject;
 export declare function AudioComponentValidate(inComponent: NobjcObject, inValidationParameters: NobjcObject | null, outValidationResult: NobjcObject): number;
-export declare function AudioComponentValidateWithResults(inComponent: NobjcObject, inValidationParameters: NobjcObject | null, inCompletionHandler: NobjcObject): number;
+export declare function AudioComponentValidateWithResults(inComponent: NobjcObject, inValidationParameters: NobjcObject | null, inCompletionHandler: (arg0: NobjcObject, arg1: NobjcObject) => void): number;
 export declare function AudioConverterConvertBuffer(inAudioConverter: NobjcObject, inInputDataSize: number, inInputData: Uint8Array, ioOutputDataSize: NobjcObject, outOutputData: Uint8Array): number;
 export declare function AudioConverterConvertComplexBuffer(inAudioConverter: NobjcObject, inNumberPCMFrames: number, inInputData: NobjcObject, outOutputData: NobjcObject): number;
 export declare function AudioConverterDispose(inAudioConverter: NobjcObject): number;
@@ -40,7 +40,7 @@ export declare function AudioConverterGetPropertyInfo(inAudioConverter: NobjcObj
 export declare function AudioConverterNew(inSourceFormat: NobjcObject, inDestinationFormat: NobjcObject, outAudioConverter: NobjcObject | null): number;
 export declare function AudioConverterNewSpecific(inSourceFormat: NobjcObject, inDestinationFormat: NobjcObject, inNumberClassDescriptions: number, inClassDescriptions: NobjcObject, outAudioConverter: NobjcObject | null): number;
 export declare function AudioConverterNewWithOptions(inSourceFormat: NobjcObject, inDestinationFormat: NobjcObject, inOptions: NobjcObject, outAudioConverter: NobjcObject | null): number;
-export declare function AudioConverterPrepare(inFlags: number, ioReserved: Uint8Array | null, inCompletionBlock: NobjcObject | null): void;
+export declare function AudioConverterPrepare(inFlags: number, ioReserved: Uint8Array | null, inCompletionBlock: ((arg0: number) => void) | null): void;
 export declare function AudioConverterReset(inAudioConverter: NobjcObject): number;
 export declare function AudioConverterSetProperty(inAudioConverter: NobjcObject, inPropertyID: number, inPropertyDataSize: number, inPropertyData: Uint8Array): number;
 export declare function AudioFileClose(inAudioFile: NobjcObject): number;
@@ -137,9 +137,9 @@ export declare function AudioQueueGetParameter(inAQ: NobjcObject, inParamID: num
 export declare function AudioQueueGetProperty(inAQ: NobjcObject, inID: number, outData: Uint8Array, ioDataSize: NobjcObject): number;
 export declare function AudioQueueGetPropertySize(inAQ: NobjcObject, inID: number, outDataSize: NobjcObject): number;
 export declare function AudioQueueNewInput(inFormat: NobjcObject, inCallbackProc: NobjcObject, inUserData: Uint8Array | null, inCallbackRunLoop: Uint8Array | null, inCallbackRunLoopMode: Uint8Array | null, inFlags: number, outAQ: NobjcObject | null): number;
-export declare function AudioQueueNewInputWithDispatchQueue(outAQ: NobjcObject | null, inFormat: NobjcObject, inFlags: number, inCallbackDispatchQueue: _NSObject, inCallbackBlock: NobjcObject): number;
+export declare function AudioQueueNewInputWithDispatchQueue(outAQ: NobjcObject | null, inFormat: NobjcObject, inFlags: number, inCallbackDispatchQueue: _NSObject, inCallbackBlock: (arg0: NobjcObject, arg1: NobjcObject, arg2: NobjcObject, arg3: number, arg4: NobjcObject) => void): number;
 export declare function AudioQueueNewOutput(inFormat: NobjcObject, inCallbackProc: NobjcObject, inUserData: Uint8Array | null, inCallbackRunLoop: Uint8Array | null, inCallbackRunLoopMode: Uint8Array | null, inFlags: number, outAQ: NobjcObject | null): number;
-export declare function AudioQueueNewOutputWithDispatchQueue(outAQ: NobjcObject | null, inFormat: NobjcObject, inFlags: number, inCallbackDispatchQueue: _NSObject, inCallbackBlock: NobjcObject): number;
+export declare function AudioQueueNewOutputWithDispatchQueue(outAQ: NobjcObject | null, inFormat: NobjcObject, inFlags: number, inCallbackDispatchQueue: _NSObject, inCallbackBlock: (arg0: NobjcObject, arg1: NobjcObject) => void): number;
 export declare function AudioQueueOfflineRender(inAQ: NobjcObject, inTimestamp: NobjcObject, ioBuffer: NobjcObject, inNumberFrames: number): number;
 export declare function AudioQueuePause(inAQ: NobjcObject): number;
 export declare function AudioQueuePrime(inAQ: NobjcObject, inNumberOfFramesToPrepare: number, outNumberOfFramesPrepared: NobjcObject | null): number;
@@ -160,11 +160,11 @@ export declare function AudioServicesDisposeSystemSoundID(inSystemSoundID: numbe
 export declare function AudioServicesGetProperty(inPropertyID: number, inSpecifierSize: number, inSpecifier: Uint8Array | null, ioPropertyDataSize: NobjcObject, outPropertyData: Uint8Array | null): number;
 export declare function AudioServicesGetPropertyInfo(inPropertyID: number, inSpecifierSize: number, inSpecifier: Uint8Array | null, outPropertyDataSize: NobjcObject | null, outWritable: NobjcObject | null): number;
 export declare function AudioServicesPlayAlertSound(inSystemSoundID: number): void;
-export declare function AudioServicesPlayAlertSoundWithCompletion(inSystemSoundID: number, inCompletionBlock: NobjcObject | null): void;
-export declare function AudioServicesPlayAlertSoundWithDetails(inSystemSoundID: number, inDetails: NobjcObject | null, inCompletionBlock: NobjcObject | null): void;
+export declare function AudioServicesPlayAlertSoundWithCompletion(inSystemSoundID: number, inCompletionBlock: (() => void) | null): void;
+export declare function AudioServicesPlayAlertSoundWithDetails(inSystemSoundID: number, inDetails: NobjcObject | null, inCompletionBlock: (() => void) | null): void;
 export declare function AudioServicesPlaySystemSound(inSystemSoundID: number): void;
-export declare function AudioServicesPlaySystemSoundWithCompletion(inSystemSoundID: number, inCompletionBlock: NobjcObject | null): void;
-export declare function AudioServicesPlaySystemSoundWithDetails(inSystemSoundID: number, inDetails: NobjcObject | null, inCompletionBlock: NobjcObject | null): void;
+export declare function AudioServicesPlaySystemSoundWithCompletion(inSystemSoundID: number, inCompletionBlock: (() => void) | null): void;
+export declare function AudioServicesPlaySystemSoundWithDetails(inSystemSoundID: number, inDetails: NobjcObject | null, inCompletionBlock: (() => void) | null): void;
 export declare function AudioServicesRemoveSystemSoundCompletion(inSystemSoundID: number): void;
 export declare function AudioServicesSetProperty(inPropertyID: number, inSpecifierSize: number, inSpecifier: Uint8Array | null, inPropertyDataSize: number, inPropertyData: Uint8Array): number;
 export declare function AudioSessionAddPropertyListener(inID: number, inProc: NobjcObject, inClientData: Uint8Array): number;
@@ -197,7 +197,7 @@ export declare function AudioUnitUninitialize(inUnit: NobjcObject): number;
 export declare function AudioWorkIntervalCreate(name: string, clock: NobjcObject, attr: NobjcObject | null): NobjcObject;
 export declare function AUEventListenerAddEventType(inListener: NobjcObject, inObject: Uint8Array | null, inEvent: NobjcObject): number;
 export declare function AUEventListenerCreate(inProc: NobjcObject, inUserData: Uint8Array | null, inRunLoop: Uint8Array | null, inRunLoopMode: Uint8Array | null, inNotificationInterval: number, inValueChangeGranularity: number, outListener: NobjcObject | null): number;
-export declare function AUEventListenerCreateWithDispatchQueue(outListener: NobjcObject | null, inNotificationInterval: number, inValueChangeGranularity: number, inDispatchQueue: _NSObject, inBlock: NobjcObject): number;
+export declare function AUEventListenerCreateWithDispatchQueue(outListener: NobjcObject | null, inNotificationInterval: number, inValueChangeGranularity: number, inDispatchQueue: _NSObject, inBlock: (arg0: NobjcObject, arg1: NobjcObject, arg2: number, arg3: number) => void): number;
 export declare function AUEventListenerNotify(inSendingListener: NobjcObject | null, inSendingObject: Uint8Array | null, inEvent: NobjcObject): number;
 export declare function AUEventListenerRemoveEventType(inListener: NobjcObject, inObject: Uint8Array | null, inEvent: NobjcObject): number;
 export declare function AUGraphAddNode(inGraph: NobjcObject, inDescription: NobjcObject, outNode: NobjcObject): number;
@@ -238,7 +238,7 @@ export declare function AUGraphUninitialize(inGraph: NobjcObject): number;
 export declare function AUGraphUpdate(inGraph: NobjcObject, outIsUpdated: NobjcObject | null): number;
 export declare function AUListenerAddParameter(inListener: NobjcObject, inObject: Uint8Array | null, inParameter: NobjcObject): number;
 export declare function AUListenerCreate(inProc: NobjcObject, inUserData: Uint8Array, inRunLoop: Uint8Array | null, inRunLoopMode: Uint8Array | null, inNotificationInterval: number, outListener: NobjcObject | null): number;
-export declare function AUListenerCreateWithDispatchQueue(outListener: NobjcObject | null, inNotificationInterval: number, inDispatchQueue: _NSObject, inBlock: NobjcObject): number;
+export declare function AUListenerCreateWithDispatchQueue(outListener: NobjcObject | null, inNotificationInterval: number, inDispatchQueue: _NSObject, inBlock: (arg0: NobjcObject, arg1: NobjcObject, arg2: number) => void): number;
 export declare function AUListenerDispose(inListener: NobjcObject): number;
 export declare function AUListenerRemoveParameter(inListener: NobjcObject, inObject: Uint8Array | null, inParameter: NobjcObject): number;
 export declare function AUParameterFormatValue(inParameterValue: number, inParameter: NobjcObject, inTextBuffer: string, inDigits: number): string;