[softwarelist] Re: icnclipbrd 0.12

  • From: David Pilling <flist@xxxxxxxxxxxxxxxxxxx>
  • To: davidpilling@xxxxxxxxxxxxx
  • Date: Fri, 23 Nov 2007 12:07:53 +0000

In message <2fd661424f.steve@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, Steve Fryatt <lists@xxxxxxxxxxxxxxxxxx> writes

The fault could easily lie on either side: the RAM XFer code in IcnClipBrd
had been commented out since I took over the module, and -- although I've
gone through it all carefully and tested it as much as possible -- there's
a possibility that it was disabled for a reason.

Just to keep everyone up to date. Entirely due to Steve Fryatt's efforts the problem with icnclipbrd is now solved.

I'll produce a new version of OP for RISC OS soon which fixes the problem.

The ram transfer code in OP has been making assumptions about the behaviour of other programs which are not justified by the Acorn specification of the protocol.


--
David Pilling
email: david@xxxxxxxxxxxxxxxxxxx
  web: http://www.davidpilling.net
 post: David Pilling P.O. Box 22 Thornton Cleveleys Blackpool. FY5 1LR UK
  fax: +44(0)870-0520-941



Other related posts: