Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!shebanow1@applelink.apple.com
From: shebanow1@applelink.apple.com (Andrew G. Shebanow)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Excel vs. MultiFinder
Message-ID: <12303@goofy.Apple.COM>
Date: 27 Feb 91 17:30:06 GMT
References: <4219@orbit.cts.com>
Sender: usenet@Apple.COM
Distribution: na
Organization: Apple Computer, Inc.
Lines: 30

In article <4219@orbit.cts.com>, pj@pnet51.orb.mn.org (Paul Jacoby) writes:
>   If a program is active in MultiFinder (Excel in this case) and you switch to
> the Finder, select a few documents, and select Print from the File menu,
> NOTHING happens.  It works fine if the parent application is NOT running
> already.  Bug?

Not a bug, unfortunately. The "standard" way of having the Finder tell an app
to print is via AppParmHandle, which is passed in at application startup. There
isn't any way to tell a running application to reexamine its AppParmHandle.
However, System 7.0 DOES provide standard AppleEvents for printing documents
at any time, so any AppleEvent aware application will be able to Print from the
Finder at any time. The Finder enables the Print item whenever you select
documents because determining whether or not all of the selected documents
belong to applications that support AppleEvents would be very time consuming,
and it would be confusing to  the user when some selections could print, and some
couldn't.

Andy Shebanow
DTS Emeritus

he bad habit of dumping HUGE core files in it's directory.  You
need to go into the directory in a Terminal window (browser will not
allow you to do this) and examine the Icon.app directory for core
files,  remove it, it is of little use to you, and certainly I don't
think NeXT would be happy if you sent them the file saying "what went
wrong?"

Pascal Chesnais, Research Specialist, Electronic Publishing Group
Media Laboratory, E15-351, 20 Ames Street, Cambridge, Ma, 02139 (617) 253-0311
email: lacsap@plethora.media.mit.edu (NeXT)