View Full Version : CTRL-V (paste) goes to wrong window in Stamp IDE v2.2
08-03-2005, 11:11 AM
Context:· Basix Stamp Editor/Development System v2.2
When I attempt to use Ctrl-V to paste the clipboard content into the Find/Replace dialog (when that dialog has focus, and either the Find or the Replace field has focus), the buffer content is placed in the IDE's editor window at the cursor.
I was expecting to be able to select and copy a string from the IDE editor window, highlight another string in the IDE, then open the Find/Replace dialog (which will defaul the Find field to the current highlighted IDE text) and paste the clipboard buffer into the Replace field.
Is my expectation different from the design intent?
08-03-2005, 11:24 AM
·· If you want a word to appear in the Find selection of the editor Find/Replace window, simply highlight it either by dragging across it or double-clicking it, then select Find/Replace from the Edit Menu.· This will place the selected text into the Find box.··Also you can select keywords the same way, then select F1 to bring up help on that command.
Parallax Tech Support
08-03-2005, 12:14 PM
I understand, and use, both of those techniques.
I'm asking about the unexpected behavior of the paste insertion point never leaving the IDE editor screen when the Find/Replace dialog is open.
My expectation is set by my experience with a number of other editors/IDEs where, as an additional step to the one you describe of automatically loading the currently highlighted text into the Find text-box, I can paste the current contents of the paste buffer into the Replace text-box.·
As it is now, I can pre-load the Find string, but I must manually type the Replace string.· This can be a problem (rather, annoyance) when the replacement string is lengthy.
Perhaps my expection is not the design intent, though.
08-03-2005, 12:58 PM
··· I will look into this tomorrow.
Parallax Tech Support
Yup, Daniel is quite right.· I have V2.2 and the same problem.· It does seem counter to the way other Windows editors work.
08-04-2005, 01:59 AM
I became aware of that problem in version 2.1 and have yet to find the reason why it is occuring (it is not intentional).· I intend to fix it for the next major release.· Sorry for the inconvenience.
· Sr. Software Engineer
· Parallax, Inc.
08-04-2005, 02:02 AM