Re: capi:collect-interfaces error
"John DeSoi (as john at desoi dot dev)" <[email protected]> Thu, 2 Apr 2026 15:40:05 +0000
| Newsgroups | gmane.lisp.lispworks.general |
|---|---|
| Message-ID | <0100019d4eda0a19-2cd02c11-a0e0-4e7a-990e-ac149a5c21c8-000000@email.amazonses.com> |
I thought I tried :create and still had an error. I know I tried to pass nil to see if I could disable any sorting - also an error. Fortunately, I found a work-around that avoids collect-interfaces for my use case. Thanks, John DeSoi, Ph.D. > On Mar 31, 2026, at 5:07 AM, Martin Simmons <[email protected]> wrote: > > We should probably do better at preventing the error you got, but calling > capi:collect-interfaces with :sort-by :visible is not safe from a random > thread on macOS because it needs to make Cocoa calls to find the z order. > > The default :sort-by :create should be safe, but of course can return out of > date information.