A CAPI interface.
A screen, or any argument accepted by convert-to-screen.
A CAPI interface.
A list of keywords.
On GTK+, Microsoft Windows or Motif, a CAPI process,
nil. On Cocoa, this argument is not supported.
If process is not supplied, then if owner is supplied interface runs in owner 's process, otherwise interface runs in the process of the parent of interface if it is a document-container, or in a new process created for interface if not.
On Microsoft Windows and Motif, if
runs in a newly-created process. If process is
runs in the current process. Otherwise
is expected to be a CAPI process, and
runs in it. A CAPI process is a
mp:process which was created by calling
display. You can pass only a CAPI process as
, because it needs to handle messages using the LispWorks event loop. The default value of
On Cocoa, all CAPI interfaces run in the Cocoa Event Loop process (which is the main thread of LispWorks) and therefore the process argument is not supported. If the value of process is any process other than the Cocoa Event Loop process an error is signalled.
owner specifies an owner for interface , which should be another CAPI interface. interface inherits a number of attributes from owner , including the default process, default screen and default display state.
window-styles , if supplied, sets the window-styles slot of interface . See interface for information about window-styles .
displayhas finished preparing the interface to display, it calls interface-display to actually do the display. The primary method does the actual display, and you can
:aftermethods to execute code just before or just after the window appears.
The correct thread for CAPI operations
Host Window System-specific issues
Programming with CAPI Windows
CAPI User Guide and Reference Manual (Windows version) - 3 Aug 2017