Re: capi:interface-display for dialogs
"John DeSoi (as john at desoi dot dev)" <[email protected]>
| Newsgroups | gmane.lisp.lispworks.general |
|---|---|
| Message-ID | <01000196035cd8bb-bddd0b6d-a78d-4614-92cc-f96e9fb6dcc7-000000@email.amazonses.com> |
Your link says > interface-display is useful when you need to make changes to the interface which require it to be already be created. Font queries and loading images are typical cases. I'm not following why these things would be wrong for a dialog. I can show the same interface with display or display-dialog. But if I need a dialog, the same code will not work. I see now that destroy-callback is also not call when display-dialog is used. I probably just need to give up on display-dialog and implement something equivalent that only uses capi:display. Thanks, John DeSoi, Ph.D. > On Apr 4, 2025, at 10:43 AM, Martin Simmons <[email protected]> wrote: > > The primary method of interface-display does the work of displaying the > interface, which would be wrong for a dialog, so display-dialog can't call it > (https://www.lispworks.com/documentation/lw81/capi-m/capi-capi-ref-205.htm). > > Hopefully you can do the Objective-C calls in the create-callback.