LOGO-L> Re: MSWLogo - something my pupils try to do but can't

[George Mills <mills@softronix.com>]

See Online Help "Editing With Clipboard".

I hope you don't mind my posting my response.

You can copy executed code from the command Recall ListBox (what
your calling 'record' box) of the Commander to the editor. Just select the
desired code with the mouse and enter <CTRL-C> to copy it to the clipboard.
Then paste it into a procedure within the editor with <CTRL-V>
(or Menu Edit->Paste).

You can also work/test from within the editor. By selecting the code you
want to test or refine and hit "Test!" on the Editor menu. You have to watch out
for the context or scope your in while you do this. You should not select the "TO"
and "END" for example and arguments to that procedure will not be defined.

For example:

to box :size
repeat 4 [fd :size rt 90]
end

You could select the body of the procedure above (one line) but it won't know
what :size is. If you select TO/END lines as well (3 lines), it will jump into the
TO definition input box. When you use TEST! it's exactly as if you typed those
lines into the commander one after another.

So for developing/testing/refining (while in the editor) you might do this:

to box :size
make "size 100
repeat 4 [fd :size rt 90]
end

Now select the body (now 2 lines) and refine your "repeat line" as needed. Now you can
repeatedly test it with the TEST! command. In general I find using the commander directly
much quicker and easier and then copy the selected code that worked as I wanted into the
final procedure within the editor as you first described.

Let me know if this solves your dilemma.

Alan Sturgess wrote:
> 
> George -
> 
> Is there any way around a minor hassle that has cropped up with those
> pupils of mine who are starting to explore MSWLogo at home? . . .
> 
> They are used to testing ideas OUTSIDE procedures and then converting them
> into procedures by adding TO --- and END.  THis is easy in Logotron WinLogo
> and it means they can work towards the stage where they envisage a set of
> commands before writing a procedure from scratch.
> 
> It looks as if several pupils have tried the same idea in MSWLogo but can't
> make it work.  The general approach seems to be as follows:
> 
> 1)  Work on a multi-statement line of instructions or a sequence of
> instructions.
> 2)  Test and refine these as they go by flipping between the 'Record' and
> 'Command' windows in the Commander.
> 3)  Reach the stage where everything works and they want to convert it into
> a procedure.
> 4)  Try to highlight and COPY instructions into the Editor . . . but there
> seems to be no way to do this.
> 
> One bright spark tried to use the Editor itself as a writing and testing
> tool. He deleted the TO and END markers and wrote his instructions. On
> 'Save and Exit' the pattern was dutifully drawn - but the instructions
> disappeared into the ether.
> 
> So - IS there any way to work on instructions until they work - and then
> COPY them into the Editor?
> 
> For myself, I've hit the problem from another angle.  I@m writing a series
> of workbooks to guide pupils through the stages of learning Logo. I'm
> having to write instructions in Word2 - copy them - paste them into the
> 'Command' line - test them but then go back to Word2 to make changes. There
> seems to be no way to Copy out of MSWLogo into a wordprocessor.
> 
> Or have I missed something?
> 
> All the best - the program really is excellent. The more I use it, the more
> I like it.
> 
> Alan.

-- 
===============================================================
George Mills
email: mills@softronix.com
http://www.softronix.com
The www page contains some very powerful educational software.
Our single most important investment is our kids.
---------------------------------------------------------------
Please post messages to the Logo forum to logo-l@gsn.org.  Mail
questions about the list administration to logofdn@gsn.org.  To
unsubscribe send    unsubscribe logo-l    to majordomo@gsn.org.