Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!steinmetz!trub!perley
From: perley@trub.steinmetz (Donald P Perley)
Newsgroups: comp.sys.amiga
Subject: Re: TSNIP and UW
Keywords: tsnip uw
Message-ID: <13458@steinmetz.ge.com>
Date: 27 Mar 89 22:42:39 GMT
References: <669@wsu-cs.uucp>
Sender: news@steinmetz.ge.com
Reply-To: perley@trub.steinmetz.ge.com (Donald P Perley)
Distribution: na
Organization: GE Corp. R & D, Schenectady, NY
Lines: 22

In article <669@wsu-cs.uucp> jal@wsu-cs.uucp (Jason Leigh) writes:
>
>Does anyone know how I can get TSNIP to work properly with UW?

I am going to guess that the problem is in offset (how far UW puts 
characters from the window edges). Both my solutions are really avoiding
the problem.

1) use DNET instead of UW.

2) use snipit instead of tsnip. Snipit allows you to adjust the x and y 
   offset it uses when scanning your region for characters.  Sort of like
   fine tuning. That is, unless I got the two mixed up....  You need the
   one with the control window.  Anyway... try slightly adjusting the 
   offset until it starts finding letters instead of garbage.  Remember
   the numbers, because you will have to adjust back to 0,0 to cut out
   of CLI windows.  This adjustment should have no effect on the window you
   are pasting to, just the one you cut from.  If you don't want to
   adjust back and forth, you can run both snipit and tsnip at the same
   time, as the mouse button manipulations are different.

-don perley