Path: utzoo!mnetor!uunet!yale!ewing
From: ewing@yale.UUCP (ken ewing)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Coral Allegro Common Lisp objects, and application hacks
Message-ID: <25513@yale-celray.yale.UUCP>
Date: 22 Mar 88 20:41:21 GMT
References: <25290@yale-celray.yale.UUCP> <1267@hqda-ai.UUCP>
Reply-To: ewing@yale-celray.UUCP (ken ewing)
Organization: Yale University Computer Science Dept, New Haven CT
Lines: 25
Keywords: CLOS coral lisp objects
Summary:

Expires:

Sender:

Followup-To:

Distribution:


In article <1267@hqda-ai.UUCP> arbaugh@hqda-ai.UUCP (Bill Arbaugh) writes:
>     The way I creatde a pseudo "application" with allegro is to
>write a function, say test,  that sets the menubar to the one for my
>application, closes the Listener window and selects my
>application window.  I then continually loop through a function
>that controls my application.  I think you could use
>window-null-event-handler here as well.  This must be done because
>if the function test returns a new listener window will be made
>and exposed.  Then at the end of the file containing my
>application I add the s-expression (TEST).  When the user double
>clicks on the application file icon the default menu bar appears for a second
>but then is quickly replaced by my own menu bar and window.  The

Instead of trying to keep any listener windows from being created, you
need only (ask *top-listener* (window-hide)).  No need for a never-
returning function at all!

>--
>==========================================================
>Bill Arbaugh                      Phone:  (202) 694-6900
>UUCP:  *!uunet!cos!hqda-ai!arbaugh ARPA:  ai02@hios-pent.arpa
>==========================================================


ken ewing   ewing@cs.yale.edu