如何通过LWJGL3获取的NSWindow指针在Objective-C中操作窗口？

Absolutely! You can fully interact with the native NSWindow instance retrieved from LWJGL 3's GLFWNativeCocoa#glfwGetCocoaWindow(long window) method. Here's a step-by-step breakdown of how to do this safely and effectively:

1. Cast the GLFW pointer to an NSWindow reference #

The long value returned by glfwGetCocoaWindow() is a direct pointer to the underlying NSWindow object. In Objective-C, you can cast this pointer to an NSWindow reference using a bridge cast (critical for ARC compatibility):

// 'windowPtr' is the long value obtained from LWJGL's GLFWNativeCocoa call
NSWindow *nativeWindow = (__bridge NSWindow *)(void *)windowPtr;

The __bridge keyword tells ARC that we're just converting a pointer type without transferring ownership—GLFW retains ownership of the window, so you shouldn't let ARC deallocate it.

2. Perform low-level macOS window operations #

Once you have the NSWindow reference, you can use any of macOS's native window APIs to modify behavior or add native UI elements. For example:

// Update the window title
[nativeWindow setTitle:@"Native macOS Window"];

// Toggle borderless mode
nativeWindow.styleMask = NSWindowStyleMaskBorderless | NSWindowStyleMaskClosable;

// Add a native button to the window's content view
NSView *contentView = nativeWindow.contentView;
NSButton *nativeButton = [[NSButton alloc] initWithFrame:NSMakeRect(40, 40, 120, 36)];
[nativeButton setTitle:@"Click Me!"];
[nativeButton setTarget:self];
[nativeButton setAction:@selector(buttonClicked:)];
[contentView addSubview:nativeButton];

3. Critical Caveats to Avoid Issues #

• Don't take ownership of the window: GLFW is responsible for creating and destroying the window. Never call [nativeWindow release] (non-ARC) or allow ARC to deallocate it—always use glfwDestroyWindow() to clean up.
• Main thread requirement: macOS UI operations must run on the main thread. If your LWJGL code runs on a separate thread, dispatch your Objective-C calls to the main queue:

  dispatch_async(dispatch_get_main_queue(), ^{
      // Your NSWindow operations go here
      [nativeWindow setTitle:@"Updated Safely on Main Thread"];
  });
  

• Avoid conflicting changes: If you modify window properties (like size, position, or style) via both GLFW and native Objective-C, you may encounter unexpected behavior. Stick to one approach for each property, or test thoroughly to ensure compatibility.

内容的提问来源于stack exchange，提问作者yaenk