--- Scott Rossi [EMAIL PROTECTED] wrote:
and if any of your mainstack cards
may be deleted?
consider relegating your deletable cards to a
substack.
that did it, thanks.
Erik Hansen
[EMAIL PROTECTED]http://www.erikhansen.org
__
Do
on Thu, 21 Apr 2005
Mikey wrote:
d) The lack of manuals means that most of the
issues are from noobs,who don't know about the
archives, or aren't used to using them before
asking questions first.
Hi Mikey,
Could you explain what you mean when you
said: The lack of manuals?
You could
Al,
I'm not going to argue with you at length on this one. The reason
there is a Revolution Documentation Project is because...
--
http://taoofrunrev.blogspot.com
http://taoof4d.blogspot.com
http://4dwishlist.blogspot.com
On the first day, God created the heavens and the Earth
On the second
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now if only more people would read the archives *before* posting the
questions, the list would have more answers to fewer questions
(allowing time for things to catch up...)
On Apr 20, 2005, at 9:28 PM, J. Landman Gay wrote:
We try to answer
The problem with the archives is that
a) responses here are very fast (in other words, y'all make it easy),
and the culture is permissive
b) Honestly, the archive search tools are not as easy to use
c) Most of the responses are not so complicated as to discourage the
responders from telling the
The problem with the archives is that
a) responses here are very fast (in other words, y'all make it easy),
and the culture is permissive
b) Honestly, the archive search tools are not as easy to use
c) Most of the responses are not so complicated as to discourage the
responders from telling the
--- Scott Rossi [EMAIL PROTECTED] wrote:
... to initialize stuff, placing the init
scripts in the first card of
your main stack causes the scripts to
run only when the main stack is
opened (preOpenStack, openStack, openCard,
etc).
and if any of your mainstack cards
may be deleted?
Erik
Recently, Erik Hansen wrote:
... to initialize stuff, placing the init
scripts in the first card of
your main stack causes the scripts to
run only when the main stack is
opened (preOpenStack, openStack, openCard,
etc).
and if any of your mainstack cards
may be deleted?
First I would
Recently, Scott Rossi wrote:
Or you can go through all substacks and place blocking handlers in each (open
preOpenStack, end preOpenstack, etc).
Actually the following is a little more clear:
on preOpenStack
end preOpenStack
on openStack
end openStack
Etc.
These are placed in your
--- Scott Rossi [EMAIL PROTECTED] wrote:
Recently, Erik Hansen wrote:
... to initialize stuff, placing the init
scripts in the first card of
your main stack causes the scripts to
run only when the main stack is
opened (preOpenStack, openStack, openCard,
etc).
and if any of
Hi,
If I have a Stack (Call iits GlobalStack that has a lot of common
funtions in the Stack Script, and those functions refer to this
Stack, which stack does that actually refer to?
e.g. if Stack A
does a start using start using stack GlobalStack
and thean Stack A calls a Function in
Hi Dave,
e.g. if Stack A
does a start using start using stack GlobalStack
and thean Stack A calls a Function in GlobalStack that refers to this
stack does that refer to Stack A or GlobalStack ?
Does this work the same way if the Stacks in question are both main stacks
and does it work the same
Hi Dave,
e.g. if Stack A
does a start using start using stack GlobalStack
and thean Stack A calls a Function in GlobalStack that refers to
this stack does that refer to Stack A or GlobalStack ?
Does this work the same way if the Stacks in question are both main
stacks and does it work the same
Hi Dave,
In any script of stack A, if you call a function placed in the script
of stack B, *this* will refer to stack A since your script has been
initiated in stack A.
Function or handler places do not matter.
The only important point is: from where do I began :-)
Le 20 avr. 05, à 17:33, David
Hi,
That's how I thought it would work. I am getting very strange results
from code that does this tho. Could the Current Stack be being lost
as a result of calling Answer or put xxx into msg box?
Thanks
Dave
Hi Dave,
In any script of stack A, if you call a function placed in the
script of stack
Hi Dave,
No.
But a statement setting the defaultStack property yes.
Best,
Le 20 avr. 05, à 18:41, David Burgun a écrit :
Hi,
That's how I thought it would work. I am getting very strange results
from code that does this tho. Could the Current Stack be being lost
as a result of calling Answer or
Hi,
Ok, I think I have found the problem! I have a openStack handler in
the script of the Stack, as so:
on openStack
local myStackFileName,myStackShortName,myGlobalStackName
put the fileName of this stack into myStackFileName
put the short name of this stack into myStackShortName
put
Hi,
openStack handler is called each time a stack is open: in the IDE it
may be when opening any script, any property window, rev error dialog,
app browser, etc..
In fact any window. That's the great thing with Rev : the IDE is built
with Rev :-)
As for your problem, you have to check when you
Hi Eric and thanks for the help!
As for your problem, you have to check when you have to trigger or
PASS a system message with a condition test.
You are right: IDE behaviour if different from stand alone environment.
You can check this too and act accordingly.
I really don't understand what you
Recently, David Burgun wrote:
I hadn't realized that the openStack handler gets called when doing a
Save. What is the recommended action for handle this?
I could do one of three things:
1. Check if myStackFileName is empty and if so skip the start uisng
2. Check the Stack Name for
On Wed, 20 Apr 2005 16:33:47 +0100, David Burgun
[EMAIL PROTECTED] wrote:
Hi,
I am confused, in the case where StackA calls a Function in
GlobalStack, when in that function should this stack return
StackA or GlobalStack ?
I want it to return StackA so that the functions are general.
I think it
Hi,
Thanks a lot for this. No, I don't have any substacks so moving it
into the card script sounds best. Ok a couple of questions of this.
You say move it to the first card, well in this stack there is only
one card so the issue doesn't come out, but for the sake of knowing,
if I have more
Recently, David Burgun wrote:
If your openStack handler is only supposed to apply to your main stack, then
place the openStack handler in the script of the *first card* of your main
stack (this goes for any initialization handlers since they are only called
when the first card is opened).
Recently, David Burgun wrote:
If your openStack handler is only supposed to apply to your main
stack, then
place the openStack handler in the script of the *first card* of your main
stack (this goes for any initialization handlers since they are only called
when the first card is opened).
On 4/20/05 2:33 PM, David Burgun wrote:
Ok, I think I understand that, in this case though, the Stack in
question *is* a main stack, does this make a difference?
Every stack has one or more cards; mainstacks, substacks, all of them.
Type this into the message box:
go card 1
Whatever card
Cards are numbered in the order you have created them. A new stack
automatically has one card. If you create another card, that will be
card 2. If you use the arrow keys to page through your stack, it will
show the cards in order. You can change the order of the cards if
necessary (though it
On 4/20/05 3:46 PM, Mikey wrote:
Cards are numbered in the order you have created them. A new stack
automatically has one card. If you create another card, that will be
card 2. If you use the arrow keys to page through your stack, it will
show the cards in order. You can change the order of the
27 matches
Mail list logo
