Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!mcnc!ecsvax!dukeac!sgt
From: sgt@dukeac.UUCP (Stephen G. Tell)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Supporting the clipboard (Re: Jerry declares the 2000 as 'the most improved computer')
Summary: Clipboard does do seeks
Message-ID: <1306@dukeac.UUCP>
Date: 22 Mar 89 18:14:33 GMT
References: <8903011852.AA16426@jade.berkeley.edu> <6193@columbia.edu> <10901@well.UUCP> <794@zehntel.UUCP> <10923@well.UUCP> <6206@cbmvax.UUCP> <1989Mar19.023257.20564@ziebmef.uucp>
Reply-To: sgt@dukeac.UUCP (Stephen G. Tell)
Organization: Academic Computing, Duke University, Durham, NC
Lines: 23

In article <1989Mar19.023257.20564@ziebmef.uucp> cks@ziebmef.UUCP (Chris Siebenmann) writes:
...
> So (to turn this into a comp.sys.amiga.tech topic), having listened
>to my tale of woe, does anyone have any suggestions? Does the
>clipboard.device support random seeks after all (the documentation is
>remarkably opaque on this point)? Does anyone have a clever idea about
>how to do this, or nifty code?

The clipboard device does support seeks; I asked the same question
and answered it myself a while back by writing the code and finding
that it works.

What the world needs is a CLIP: handler that would handle a lot of the
details.  It looks easy for simple-minded clipboard use, where you
always do the actual writing.  The feature that lets you post a clip but
not actually copy data unless someone wants it may be more difficult;
I'm not sure how to fit this into a file-system paradigm.

Steve
-- 
Steve Tell:  senior, Duke University school of Engineering (please hire me).
Former Chief Engineer, Cable 13 / Duke Union Community Television.
sgt@dukeac.ac.duke.edu;     !mcnc!ecsgate!dukeac!sgt