Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!amdahl!oliveb!amiga!mitsumi!jimm
From: jimm@mitsumi.UUCP (Jim Mackraz)
Newsgroups: comp.sys.amiga
Subject: Re: clipboard.device question - does it support random writes?
Message-ID: <986@mitsumi.UUCP>
Date: Tue, 10-Nov-87 14:33:27 EST
Article-I.D.: mitsumi.986
Posted: Tue Nov 10 14:33:27 1987
Date-Received: Fri, 13-Nov-87 04:46:59 EST
References: <562@radio.toronto.edu>
Reply-To: jimm@mitsumi.UUCP (James Mackraz)
Organization: Mitsumi Technology Inc
Lines: 25

In article <562@radio.toronto.edu> cks@radio.toronto.edu (Chris Siebenmann) writes:
) I'm working on an application that I'd like to support the clipboard.
)Unfortunately, the clipboard.device wants data in IFF format, and
)writing IFF-format data really needs something that supports writes at
)random offsets. The documentation for the clipboard.device hints that
)you can do this by playing with the io_Offset field (indeed, it hints
)at having a Seek() call of some sort), but I'd like to be sure before
)I start writing a lot of code.
)Chris Siebenmann		{allegra,mnetor,decvax,pyramid}!utgpu!radio!cks

How about writing the data to a file in the RAM disk, and copying the
result to the clipboard?  I'd like to see the standard expanded so that
the file name (in RAM:) can be passed, so that ram for just one copy
of the IFF form of the data need be around at any one moment.  It
might also be good to let the user specify (via "environment" variable
or TOOLTYPE) what directory to use for TEMP.

Anyway, this is low risk, so write that code, support that clipboard!

	jimm

-- 
	Jim Mackraz
	Mitsumi Technology, Inc.		408/980-5422
	{amiga,pyramid}!mitsumi!jimm