making it easier for you to in the future change subscribe to listen for theme change notifications instead of the busy loop

How would this upgrade enable that specifically?

making it easier for you to in the future change subscribe to listen for theme change notifications instead of the busy loop

How would this upgrade enable that specifically?

There's two ways to listen for changes to the appearance that I know of:

• Subscribing to the "AppleInterfaceThemeChangedNotification" notification using [NSDistributedNotificationCenter] (undocumented) example.
• Using Key-Value Observing on -[NSApplication effectiveAppearance], as documented (in Swift) here.

objc2-foundation/objc2-app-kit provides you the tools to use either of these, by using the generated interfaces to NSDistributedNotificationCenter or to key-value observing categories.

Using these are possible without objc2, but it's a lot harder, as you also have to consider a bunch of memory management, and ensuring you get the method signatures correct.

This PR also fixes a memory leak in cargo run --example notify.
To test, run cargo run --example notify on master on macos and notice how the ram will stack up until it crashes.
No ram is leaking on this branch.

I don't know enough about Objective C to review the code, but since two users report this fixes a real world issue in squidowl/halloy#598 and nobody has stepped up to review this in 6 months, I'll go ahead and merge this. Thanks for the fix.

Just to be explicitly clear, can someone confirm the notify example is now working on the main branch on macOS? I want to be sure of that before the next release and I don't have a Mac to test.

@madsmtm

in the future change subscribe to listen for theme change notifications instead of the busy loop.

A PR for this would be welcome!

Just to be explicitly clear, can someone confirm the notify example is now working on the main branch on macOS? I want to be sure of that before the next release and I don't have a Mac to test.

I doubt it is, this PR doesn't actually fix that.

A PR for this would be welcome!

I've written down some notes in #47, but I suspect the problem to be more fundamentally that Rust's async and Objective-C interop just do not play well together, so I doubt this is something that rust-dark-light even can fix at the moment.

Just to be explicitly clear, can someone confirm the notify example is now working on the main branch on macOS? I want to be sure of that before the next release and I don't have a Mac to test.

I tested this on macOS and it still does not work. Also, as mentioned by @madsmtm it is extremely inefficient.