I'll commit what I've done so far so you can have a look. Its just a revved up console window. I wanted to wait until I was super happy with it, but I'll do it in bits at a time. Its basically a multiline edit control used to input the script (so it is a completely editable source area, replaceable with someones coloured in text component at some stage no doubt) and you use ctrl+enter to execute a command, ctrl+up arrow to go back one in the history, and ctrl+down arrow to go forward in command history. Nothing very flash. I think I've made it sound like its some brilliant thing, I didn't mean to, and its not that great at all, so don't get your hopes up :) The script window should have remained unchanged so even if the console window doesn't work as it should you can still execute scripts. > -----Original Message----- > From: aztec-users-bounce@xxxxxxxxxxxxx > [mailto:aztec-users-bounce@xxxxxxxxxxxxx]On Behalf Of Alexander Enzmann > Sent: Monday, 15 July 2002 9:41 PM > To: aztec-users@xxxxxxxxxxxxx > Subject: [aztec-users] Re: Script Window And editing > > > > > > Phillip Martin wrote: > > > > Its a horrible trade off, but there are not very many ways to handle it. > > > > The reason its there is because its a milti line control, and > there are two > > things that the enter key should do: > > > > Put a carriage return into the multi line edit control > > Execute the contents of the edit control. > > > > The typical way of handling this is to make one of then > ctrl+return, and the > > other one just return. I just picked ctrl+enter for execution, > and the enter > > key to add a line. Perhaps a Go button that is clickable would > be good that > > also has the keyboard shortcut "ctrl+enter" included in its tool tip. > > Understand problem. > > When doing the up arrow thing, how do you handle inputs that covered > multiple lines? > > Will I be able to move the cursor up and down across multiple lines when > entering a function to edit things that weren't quite right? > > Xander >