Here's another one, folks!

Problem:
Cutting or Copying text from a room or item description field into any field when editing a script causes the UI to fubar.

Description:
When selecting text from the description field of a room or object (so as to put it in a script, to be printed under the 'right circumstances') and cutting or copying (Ctrl-X or Ctrl-C) it, then trying to paste it into any field in any script editor window, it messes up the program as if it were attempting to interpret the pasted text as a script (or something)!

To Replicate:
1) Make a new project, and add a room to it. Select the newly created room, then type something in its 'Description:' field. Select all the text you just typed, and Ctrl-X to cut to the clipboard.
2) Change the Style: from "Standard" to "Run Script".
3) Click on the "Edit..." button by the script pane. The "Print | Print a Message" action should be active. Do a Ctrl-V to try to paste the cut text here.
4) Whoops! Where did it go? Now there's no script whatsoever!!

Workaround:
You'll have to type everything into a script manually.

Hopefully a fix for this will appear in the next version, too!

See...that is the bug I was talking about. I got so tired of typing stuff over and over instead of being able to copy and paste that I just went ahead and bought ADRIFT and have been using that to make this years contest entry.

I still love Quest, but until this bug is fixed I can not really make use of it.

Hopefully soon it will be fixed and I can continue to use Quest as I still feel that is the most powerful of the available editors.

I think the new keyboard shortcuts for cut/copy/paste on the Script Editor are interfering.

You can work around the problem by right-clicking and choosing "Paste".

Nope, same thing happens with Edit | Paste as with Ctrl-V. Bugfix time!

Oops, ignore the above. I knew there was a reason to not post to forums during my naptime!
So to summarize: Ctrl-V and Edit | Paste don't work if you paste text into a script field somewhere, but the contextual menu does work.
That workaround is now confirmed.
Whew! That'll make life easier!