OS X Printing Problem

Ben C. Fetherston, Jr. bfether at mac.com
Wed Feb 13 11:25:01 EST 2002

I can't speak for Lee, but I have no problem with printing from any other
application I use in OS X, either Carbon or Cocoa, and my printer is a
shared printer on an AppleTalk ethernet network.

> Lee
> Sorry to ask such an obvious question, but I have never had a problem
> printing under OSX (Rev or anything else) so I just have to do it: do
> you have other Cocoa or Carbon apps printing successfully under OSX, not
> in Classic?
> How is your printer connected?
> thanks
> David
> On Wednesday, February 13, 2002, at 05:35 , Lee Perham wrote:
>> Date: Mon, 11 Feb 2002 14:28:26 -0800
>> Subject: OS X Printing Problem
>> From: "Ben C. Fetherston, Jr." <bfether at mac.com>
>> To: <use-revolution at lists.runrev.com>
>> Reply-To: use-revolution at lists.runrev.com
>> I have an application that as a standalone will print the text in a
>> field
>> under OS 9.2 without any problem.  Using the same stack in a standalone
>> under OS X, the printing won't work.  Has anyone had similar problems
>> with
>> printing in OS X?
>> Under OS X the printing just hangs and can't be cancelled.  This is true
>> under the standalone application as well as in the OS X version of
>> RunRev
>> under browse or suspend UI.
>> --
>> bfether at mac.com
>> Salem, OR USA
>> This is a known bug. I've reported it before. The same thing happens
>> with revPrintField  or when printing a long script in OSX.
>> ~ Lee Perham
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> http://lists.runrev.com/mailman/listinfo/use-revolution
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution

bfether at earthlink.net
Ben C. Fetherston, Jr.
Clark, Lindauer, Fetherston, Edmonds & Lippold, LLP
Salem, Oregon USA
This is legal advice only if you are a client.  NOTICE:  This communication
may contain privileged or other confidential information.  If you have
received it in error, please advise the sender by reply email and
immediately delete the message and any attachments without copying or
disclosing the contents.  Thank you. 

More information about the Use-livecode mailing list