Turn Off Double-Entry?
Jim Ault
JimAultWins at yahoo.com
Tue Apr 25 14:23:30 EDT 2006
I also have been bitten by the design of the script editor window.
Since I usually have different palettes and windows open, I am in the habit
of clicking somewhere a window to activate it. In the script editor, once
you do a find for "tCounter", it remains in the find input box.
Later I am switching windows and happen to click on the Replace button, and
without realizing it, I have replaced the string "tCounter" with empty in
every part of my stack script. There is no undo for this, even if I
realized my mistake the moment it happens.. I wish I could get in the habit
of Always changing from the Find mode of a script window, but not yet.
I would prefer a hidden Replace function since it is so dangerous.
Jim Ault
Las Vegas
On 4/25/06 10:30 AM, "Scott Rossi" <scott at tactilemedia.com> wrote:
> I don't suppose there's any way to turn off or otherwise disable the
> double-entry key sequence to close the script editor?
>
> This is something that has always bothered me about Rev's script editor. If
> a script has been edited at all, it requires two hits of the enter key close
> the window (apply and close) while if a script has *not* been edited, only
> one hit. I find myself getting in the habit of automatically pressing enter
> twice to dismiss the script editor which, as I discovered today, is bad if
> you have an executable command sitting in the message box ("delete this
> card").
>
> I now hate the behavior of the script editor window more than ever. Is
> there anything I can do to change it?
>
> Thanks & Regards,
>
> Scott Rossi
> Creative Director
> Tactile Media, Multimedia & Design
> -----
> E: scott at tactilemedia.com
> W: http://www.tactilemedia.com
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
More information about the use-livecode
mailing list