Generic Function | Package: cg | ToC | DocOverview | CGDoc | RelNotes | FAQ | Index | PermutedIndex
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version

## standalone-application

Arguments: app

The form `(standalone-application (app *system*))` returns true if the Lisp that is running is a standalone application that was generated from an IDE project using the File | Build Project Distribution menu command or the File | Build Project Exe menu command. Otherwise `nil` is returned.

If you instead generate a standalone Common Graphics app with a direct call to generate-application, then you could set this yourself if desired in the startup code of the application by calling (setf standalone-application). This should be done after calling initialize-cg but before calling event-loop.

The value is used internally to determine what happens when an error is signaled and is not handled by application code. If set to `:debuggable`, then event-loop will use an error handler that shows a break in the console window; this will be the value in a standalone application that was generated with `:allow-runtime-debug` in the build-flags of the project (reflected by the "Enable Debugging of Runtime Errors" check-box on the Project Manager Dialog Build tab). For any other non-`nil` value, event-loop will use an error handler that displays a basic end-user dialog about an unhandled error and then exits. When `nil`, then no error handler is added by event-loop; this is the case in the IDE, where the IDE's own error handler will show the Restarts Dialog.

An application could use this value to behave differently when it is being run as a standalone application than when it is run as a project in the IDE.

Copyright (c) 1998-2022, Franz Inc. Lafayette, CA., USA. All rights reserved.
This page was not revised from the 10.0 page.
Created 2019.8.20.

|  | ToC | DocOverview | CGDoc | RelNotes | FAQ | Index | PermutedIndex
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version