RE: Code Learning Tools

["Don Freeman" <DFreeman@xxxxxxxxxxxxxxx>]

I know that there is one thing that I have to use SEU for but it is pretty 
minor.  It comes in handy when converting MOVE statements to EVAL statements in 
Free-Form.  I can cut out a rectangular area in SEU so that I can move it to 
the other side of the '=' operator, and if there are pages of contiguous MOVE 
statements (and there frequently are) it's a real time saver.  I can not do 
this in CODE due to the way the Window's selection works. Other then that I 
would never go back to SEU except maybe for quick browsing.  

> -----Original Message-----
> From: Buck [mailto:buck.calabro@xxxxxxxxxxxx]
> Sent: Thursday, August 14, 2003 10:22 AM
> To: code400-l@xxxxxxxxxxxx
> Subject: Re: Code Learning Tools
> 
> 
> My only advice is to abandon the SEU mindset.  That is, when 
> using Code,
> don't try to do the same tasks the same as you would have in 
> SEU.  If you
> get really stuck trying to do something in Code and 
> absolutely have to do it
> NOW, try SEU mode.  Options, Key Behaviour, SEU.  At least 
> you won't have to
> close Code and open SEU...
> 
> This is a fairly low traffic list, so I think we'll get some 
> leeway when it
> comes to non-technical postings.  Could you describe one of 
> the things you
> couldn't get done in Code that you manage with SEU?
>   --buck
>