Richard Gaskin wrote:
J. Landman Gay wrote:
Scott Rossi 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?
...
You can use option-enter (on Windows, alt-enter) to save and close the
editor.
In my script editor I
J. Landman Gay wrote:
Scott Rossi 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?
...
You can use option-enter (on Windows, alt-enter) to save and close the
editor.
In my script editor I use Shift-Enter, becau
Recently, Dave Cragg wrote:
> I'm
> probably on your side on this one, but sometimes there is an
> advantage to the double-entry feature. I've got one of those sleek
> Apple edgeless keyboards, and I keep hitting the Enter key with my
> elbow when I reach for the phone. At those times, the doubl
It has been brought to my attention that certain flattering comments
with respect to the frequency of bugs in libUrl have been made on
this list. In line with traditional Scottish good grace, all I can
say is if it's money you're after, the answer's no.
We seem to be getting into a discuss
On Apr 26, 2006, at 11:21 AM, J. Landman Gay wrote:
[EMAIL PROTECTED] wrote:
The variable watcher misses variables (especially the clickLine).
It is possible to use the spacebar to step through code (although
there is no obvious way to know this) - except that it often will
not work for th
Richard Gaskin wrote:
J. Landman Gay wrote:
Richard Gaskin wrote:
This one is a known, and intentional, escape procedure. It happens
when there is a bug in a script that is called from your debugging
script, such as one in a library or backscript. If there is a bug in
there, the engine will g
J. Landman Gay wrote:
Richard Gaskin wrote:
This one is a known, and intentional, escape procedure. It happens
when there is a bug in a script that is called from your debugging
script, such as one in a library or backscript. If there is a bug in
there, the engine will go into an infinite loop
Now that's a bandwagon I can jump on! Dave is THE MAN :-)
libURL has probably the lowest bug density of any substantial
Transcript work I've seen. Amazing, admirable, and inspiring effort,
Dave.
I can't say enough good things about Dave. He has consistently supported
libURL like a true pro
Richard Gaskin wrote:
J. Landman Gay wrote:
Often it will step though a couple lines of code then drop to the
bottom of the handler. You can set debug checkpoints which do not
trigger the debugger at all.
This one is a known, and intentional, escape procedure. It happens
when there is a bug
On Apr 26, 2006, at 9:52 AM, David Burgun wrote:
Just a different perspective on this -
I always search out 3rd party tools once I start using a
development environment. I've never developed apps in
CodeWarrior, but for Director, Flash, etc., the 3rd party
providers were doing really cool
J. Landman Gay wrote:
Often it will step
though a couple lines of code then drop to the bottom of the handler.
You can set debug checkpoints which do not trigger the debugger at all.
This one is a known, and intentional, escape procedure. It happens when
there is a bug in a script that is cal
Recently, Geoff Canyon 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?
>
> I think you're looking for the script of field "script" of stack
> "revTemplateScriptEditor" It's easy to get at using (shameless plug
David Burgun wrote:
On 25 Apr 2006, at 19:23, Jim Ault wrote:
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
On 26 Apr 2006, at 18:12, Richard Gaskin wrote:
David Burgun wrote:
On 25 Apr 2006, at 21:06, Richard Gaskin wrote:
Ton Kuypers suggested:
> use Constellation?
A good choice. And there's MetaCard, and devolution, and you can
roll you're own
The problem is for Newbies. If you are lear
[EMAIL PROTECTED] wrote:
Good point, Dave,
But I'm not sure why we are having this discussion at all.
Whether it takes one click or two clicks to close the script editor is
the least of the problems with the editor and, worse yet, the debugger.
It opens to random window sizes. Sometimes it opens
OTOH, perhaps due to my being an old HC guy, that very behaviour is
what's burned in to my muscle memory, and I don't think I've ever had
the problem you describe - maybe I'm just luckyI'd be really
annoyed if it changed, though.
Best,
Mark
On 25 Apr 2006, at 18:30, Scott Rossi wrote:
David Burgun wrote:
On 25 Apr 2006, at 21:06, Richard Gaskin wrote:
Ton Kuypers suggested:
> use Constellation?
A good choice. And there's MetaCard, and devolution, and you can
roll you're own
The problem is for Newbies. If you are learning a new environment you
really don't want to
On 26 Apr 2006, at 16:40, Trevor DeVore wrote:
On Apr 26, 2006, at 8:18 AM, David Burgun wrote:
Also, when a newbie buys RunRev and starts to use it, depending on
their past experience, they have a big task to get their head
around, a programming language, an IDE and the whole MC concept.
On Apr 25, 2006, at 10:30 AM, Scott Rossi 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?
I think you're looking for the script of field "script" of stack
"revTemplateScriptEditor" It's easy to get at using (s
On Apr 26, 2006, at 8:18 AM, David Burgun wrote:
Also, when a newbie buys RunRev and starts to use it, depending on
their past experience, they have a big task to get their head
around, a programming language, an IDE and the whole MC concept.
They really don't want to take on any more at tha
Comments about your own experience are, of course valid.
Best,
Jerry Daniels
Consultants & Developers
http://www.daniels-mara.com
Voice: 512.879.6286
Skype: jerry.daniels
On Apr 26, 2006, at 10:18 AM, David Burgun wrote:
On 26 Apr 2006, at 15:59, Jerry Daniels wrote:
If I read this thre
Message-
From: David Burgun <[EMAIL PROTECTED]>
To: How to use Revolution
Sent: Wed, 26 Apr 2006 14:01:01 +0100
Subject: Re: Turn Off Double-Entry?
On 25 Apr 2006, at 21:06, Richard Gaskin wrote:
> Ton Kuypers suggested:
> > use Constellation?
>
> A good choice. And ther
On 26 Apr 2006, at 15:59, Jerry Daniels wrote:
If I read this thread correctly, it isn't that the Rev IDE is
untrustworthy, but rather that the second typing of an enter key
closes the Rev script editor.
Yes, bad UI design. It's not just that though, there are loads of
problems in the ID
, but history is not encouraging.
Paul Looney
-Original Message-
From: David Burgun <[EMAIL PROTECTED]>
To: How to use Revolution
Sent: Wed, 26 Apr 2006 14:01:01 +0100
Subject: Re: Turn Off Double-Entry?
On 25 Apr 2006, at 21:06, Richard Gaskin wrote:
> Ton Kuypers suggested:
&g
If I read this thread correctly, it isn't that the Rev IDE is
untrustworthy, but rather that the second typing of an enter key
closes the Rev script editor.
If basic development environments didn't have third party tools, they
wouldn't last long. Third party products exist to enrich a platf
On 25 Apr 2006, at 21:06, Richard Gaskin wrote:
Ton Kuypers suggested:
> use Constellation?
A good choice. And there's MetaCard, and devolution, and you can
roll you're own
The problem is for Newbies. If you are learning a new environment you
really don't want to add to the learnin
On 25 Apr 2006, at 19:23, Jim Ault wrote:
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
Scott Rossi 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
Scott Rossi 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
Scott,
How about a frontScript which catches closeStack and enterKey -
1) Snoop for a closeStack sent to the script editor
2) Don't pass any enterKey messages within a threshold (say 1 second)
of closing the script editor
Wrap up, throw in a plugin... should work?
- Brian
I don't suppose th
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 switc
use Constellation?
;-)
Warm regards,
Ton Kuypers
Digital Media Partners bvba
Tel. +32 (0)477 / 739 530
Fax +32 (0)14 / 71 03 04
http://www.dmp-int.com
On 25-apr-06, at 19:30, Scott Rossi wrote:
I don't suppose there's any way to turn off or otherwise disable the
double-entry key sequence t
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
33 matches
Mail list logo
