Printing all permutations

Question

Hi,
My sister is a CS student, and she currently learns recursion. She's got an exercise is to write a program that gets an array of integers and recursively prints all of its permutations (all elements in all possible orders).
For example, if the input array is {1, 2}, the program should print this:
1 2
2 1
The code was not too difficult to write, and it works now. The exercise has a second requirement, though, that the output of our program should be identical to the output of the school solution. That is, it's not enough that we print all permutations, we must do it the same order as they do.
And that's where we're kind of stuck, because the order of the output in the school solution is not the same as ours, and we're unsure how to modify our code reproduce their output.
For example, for input array {1, 2, 3}, our code would print
1 2 3
1 3 2
2 1 3
2 3 1
3 1 2
3 2 1
whereas the school solution would print
1 2 3
1 3 2
2 1 3
2 3 1
3 2 1 //last 2 lines come in reverse order
3 1 2
More (off site) examples
{1, 2, 3, 4}: http://rafb.net/p/I2DMPZ57.nln.html
{1, 2, 3, 4, 5}: http://rafb.net/p/EkQoJ668.nln.html
{1, 2, 3, 4, 5, 6}: http://rafb.net/p/RVBtVf67.nln.html
If somebody can identify a pattern in the school solution, please give us a hint as to how we should match it with our code.
The relevant part of our code is here: http://rafb.net/p/4oEsMB53.nln.html
Thanks

Answer 1

thanks for your input.
its always good to have something to kick start you into thinking again :). rather than starting blankly and tugging your hair.
anyway .. unfortunately none of the workarounds seemed to work out. they did seem to be describing a slightly different problem though - one where the text appears but the window does not scroll .. i don't get any text at all until the end (and then it does scroll).
i tried it out with a standard TextArea and got the scrolling, the problem is it is much slower than when i run it at the command prompt, and it slows down further. is this anything to do with its running lower on memory (as cmd prompt discards most of the data as it generates more), so do i need to fix that first to cure this, or is it a problem with the TextArea. and will it be a problem with any component i choose to print out on? i guess if it is ill just have to scrap that idea.
thanks again
btw - u are right, it shouldve been long - i'd corrected it since i posted the code .. sorry