Re: capi:interface-display for dialogs

Those things would not be wrong for a dialog.

The problem is that the primary method of interface-display actually places
the interface on the screen and returns.  That's not what is wanted for a
dialog, because it might need to wait until the user closes the dialog before
returning and then destroy the dialog.

BTW, destroy-callback works for me when using display-dialog.

-- 
Martin Simmons
LispWorks Ltd
http://www.lispworks.com/



>>>>> On Sat, 5 Apr 2025 00:32:18 +0000, John DeSoi said:
> 
> 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.
> 
> 

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
[email protected]
http://www.lispworks.com/support/lisp-hug.html