Re: Multiple Application Frames

• To: "James L. Robins" <jlr@tycho.ncsc.mil>
• Subject: Re: Multiple Application Frames
• From: Nichael Cramer <ncramer@BBN.COM>
• Date: Tue, 5 Apr 94 9:16:27 EDT
• Cc: wwinston@medg.lcs.mit.edu, clim@BBN.COM

>Date: Tue, 5 Apr 94 07:50:59 EDT
>From: "James L. Robins" <jlr@tycho.ncsc.mil>
>Subject: Multiple Application Frames
>
>Whitney:
>	The short answer is to rebind the variable
>*application-frame*, which is recreated for every application-frame,
>and use process-run-function to handle the application-top-level.

The variable *APPLICATION-FRAME* is something that needs to be handled with
especial care when running multiple application frames.  Much code has been
written that uses this variable as quick and easy way to get ones hands on
"The Frame" while down in the bowels of the code.

However, this is an easy way to lose quickly if more than one frame is
running and if there is any interaction between the them.  For example,
consider a command in Frame A that causes a side-effect in Frame B; any of
the code on Frame B that depends on the variable *APPLICATION-FRAME* will
lose in potentially nasty ways.

A word to the wise...

Nichael

• Prev: Multiple Application Frames
• Next: Multiple Application Frames
• Index: CLIM Mailing list (1-Jun-94 to 30-Jun-95)
• Thread: CLIM Mailing list Index (1-Jun-94 to 30-Jun-95)