of the interface) but
your comment makes me worry about the functionality of closeStack for other
users.
On Tue, Nov 10, 2009 at 6:05 PM, Robert Brenstein r...@robelko.com wrote:
On 09.11.09 at 12:48 -0400 william humphrey apparently wrote:
Thanks for everyone's replies about openstack message
william humphrey wrote:
But if you put the closeStack in the background script of the main stack
then you're back to the original problem. It gets called when you close one
of the substacks.
I notice it is working OK but it may be because that first card is always
open when the program is open
On 09.11.09 at 12:48 -0400 william humphrey apparently wrote:
Thanks for everyone's replies about openstack message confusion. Putting the
openstack (as well as closestack) items in the first card of the mainstack
solves everything and I think it is something I used to know along with a
myriad
The several proffered solutions all should work.
You can also explicitly test to see if the stack containing the handler is
the stack you want:
if the short name of this stack = yourMainStack then doThis else exit
preOpenStack
This may give you more options...
Craig Newman
with.
This is a good approach if you want to trigger an openStack handler in
some substacks but not all of them. So you can do this:
if the short name of this stack is not in substack1,substack2
then pass openStack -- or exit if you like
___
use-revolution
Thanks for everyone's replies about openstack message confusion. Putting the
openstack (as well as closestack) items in the first card of the mainstack
solves everything and I think it is something I used to know along with a
myriad of other knowledge my gradually dying brain cells once contained
dunb...@aol.com wrote:
I should have read this before I sent my own version.
Nah. More is good. :)
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
___
use-revolution
too bad that
private preopencard
ask Enter your Username with OK
end preopencard
does not work
william humphrey wrote:
Thanks for everyone's replies about openstack message confusion. Putting the
openstack (as well as closestack) items in the first card of the mainstack
solves everything
not work
william humphrey wrote:
Thanks for everyone's replies about openstack message confusion. Putting
the
openstack (as well as closestack) items in the first card of the mainstack
solves everything and I think it is something I used to know along with a
myriad of other knowledge my
Sivakatirswami wrote:
too bad that
private preopencard
ask Enter your Username with OK
end preopencard
does not work
Or maybe it works perfectly, since adding private to the handler
designation prevents it from being called by anything outside of that
script. ;)
--
Richard Gaskin
I am posting this just for other newbies out there who may find this
confusing. If you have a mainstack and lots of substacks and you put either
a preopenstack or an openstack in the mainstack you would think that it
would only be called when you first open your stack. Not true. It is called
every
william humphrey wrote:
I am posting this just for other newbies out there who may find this
confusing. If you have a mainstack and lots of substacks and you put either
a preopenstack or an openstack in the mainstack you would think that it
would only be called when you first open your stack
I think the solution is to include preOpenstack, openStack and
closeStack handlers in all your stacks. Even if the handlers are
empty. That goes for cards too.
--
Nicolas Cueto
On Mon, Nov 9, 2009 at 6:33 AM, william humphrey
b...@bluewatermaritime.com wrote:
I am posting this just for other
william humphrey wrote:
If you have a mainstack and lots of substacks and you put either
a preopenstack or an openstack in the mainstack you would think that it
would only be called when you first open your stack. Not true. It is called
every time you switch to any of the other substacks of your
Hi all,
I remember that several times some complained about openStack or
preOpenstack handlers that were not sent when double-clicking a stack
icon or using drag and drop on Rev app icon.
I was confronted to the same problem today (Rev 2.8.1) and found that
if script debug mode was off
remember that several times some complained about openStack or
preOpenstack handlers that were not sent when double-clicking a
stack icon or using drag and drop on Rev app icon.
I was confronted to the same problem today (Rev 2.8.1) and found
that if script debug mode was off when Rev launches
On Thu, 31 Jan 2008 16:20:37 +0100, Eric Chatonet wrote:
Hi all,
I remember that several times some complained about openStack or
preOpenstack handlers that were not sent when double-clicking a stack
icon or using drag and drop on Rev app icon.
I was confronted to the same problem today
Rev (I always use drag and drop), I immediately saw
that preOpenstack and openStack have not been sent (this stack is a
launcher and nothing happened).
I was surprised because I launch this project twenty or thirty times
a day... and it was the first time I was confronted with this issue.
I
Mark-
Yes. It's BZ #3843.
--
Mark Wieder
[EMAIL PROTECTED]
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
Thanks. I voted for it. I hope others will, too.
Looks like you figured out back on 1/2/08 that toggling the debug
mode fixes the issue. Think of the new Rev user who uses one of
these handlers which SHOULD work as advertised and explained in the
docs, and yet inexplicably doesn't.
Hi,
My name is songe. I'm new to runrev. I'm trying to do something
simple and can't figure out how to do it.
I need a button to be activated as soon as the stack is opened. So,
in the stack script I put the following line:
send mouseUp to bg btn id XXX.
When I quit out of it all
Hi Jonathan,
Welcome to the Revolution. I see a couple of possible problems. One
is that in Revolution, as opposed to HyperCard, you don't normally
refer to objects as background or card objects, just field, button,
group, image, whatever. (The exception is when you have directly
Isn't that what we do all the time with preference stacks etc.?
On 21/08/07, Jim Ault [EMAIL PROTECTED] wrote:
Does this work?
Compile an exe for an XP machine that does not have
Rev installed.
put a Rev stack on the hard drive
launch the exe
Use a button that says 'open stack myStack.rev'
Does this work?
Compile an exe for an XP machine that does not have
Rev installed.
put a Rev stack on the hard drive
launch the exe
Use a button that says 'open stack myStack.rev'
-- the stack opens in the exe space
I can't test this since my XP machine has Rev
installed.
My guess is 'No', but
Jim,
This would be the typical splash-stack approach. Yes, it works.
Best regards,
Mark Schonewille
--
Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.com
Quickly extract data from your HyperCard stacks with DIFfersifier.
A Rev app can open and use any stack file, as far as I know.
I do this a lot, particularly in testing. I'll build a simple one-
stack standalone that simply opens the (separate) main logic stack,
usually sending it an 'initApp command to get it running. That way I
can then edit the main
this is
not taking place on OSX. I'm not sure this is a bug, but I certainly
didn't expect this difference. At any rate, the openStack handler is
getting called properly in all cases, since the first stack disappears
after the requisite two seconds.
I'm not sure it is only a defaultFolder setting
Hello,
Could you give a try to the stack that is included to the submitted
bug #3816?
It's a stack that calls a substack in the openStack handler and with
versions 2.7.3 2.7.4 the substack is not opened as it is with
versions before.
Best,
ÉrIC
Le 26 sept. 06 à 11:17, André.Bisseret
Hi again everyone,
OK since OpenStack, OpenCard, and preOpenStack all don't work on v2.7.4 on
Mac OSX how do I work around it? If it matters I'm not using a standalone.
Joe
Orlando
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please
that is included to the submitted
bug #3816?
It's a stack that calls a substack in the openStack handler and
with versions 2.7.3 2.7.4 the substack is not opened as it is
with versions before.
Best,
ÉrIC
Le 26 sept. 06 à 11:17, André.Bisseret a écrit :
Hi,
Here on Mac OS X 10.4.7, openStack
Hi,
Here on Mac OS X 10.4.7, openStack' and openCard' handlers work
normally with RunRev v2.7.3 and v2.7.4 as well
Best regards from Grenoble
André
Le 25 sept. 06 à 21:44, [EMAIL PROTECTED] a écrit :
Hi Everyone,
I just upgraded to v2.7.4 on my Mac OSX computer. I know the
definition
Éric-
My BZ #3843 also adds a refinement to and supports your #3816.
--
-Mark Wieder
[EMAIL PROTECTED]
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
à 12:13, Éric Miclo a écrit :
Hello,
Could you give a try to the stack that is included to the
submitted bug #3816?
It's a stack that calls a substack in the openStack handler and
with versions 2.7.3 2.7.4 the substack is not opened as it is
with versions before.
Best,
ÉrIC
Le 26 sept
Hello Mark,
Matthias Rebbe on this list did make a try with the stacks that I did
submit with bug #3816 on Windows and he found out it was working
perfectly.
So it seems that something has changed in version 2.7.3 and leads to
bad behaviors perhaps with the presence of another tool.
I'm
and dragging the stack' icon onto the
Rev' icon (launching Rev).
Best regards from Grenoble
André
Le 26 sept. 06 à 12:13, Éric Miclo a écrit :
Hello,
Could you give a try to the stack that is included to the
submitted bug #3816?
It's a stack that calls a substack in the openStack handler
to the stack that is included to the
submitted bug #3816?
It's a stack that calls a substack in the openStack handler and
with versions 2.7.3 2.7.4 the substack is not opened as it is
with versions before.
Best,
ÉrIC
___
use-revolution mailing list
Hi Everyone,
I have the original problem of OpenStack, preOpenStack OpenCard not working
on a fresh version of 2.7.4 for Mac OSX. I didn't install any additional
plugins. I only use dreamcard and no standalones.
Joe
Orlando, FL
___
use-revolution
Éric-
Tuesday, September 26, 2006, 11:10:49 AM, you wrote:
So it seems that something has changed in version 2.7.3 and leads to
bad behaviors perhaps with the presence of another tool.
I'm actually unable to find out witch tool or plugin interacts with
Revolution (I've only Galaxy and
preOpen open, both Card and Stack, have been unreliable for me in
the IDE (seem to work fine in standalones, but this makes writing and
debugging difficult)
So wherever possible, I don't use these, instead, I do a manual
openStack with a message from the calling script:
send initCard
On 9/26/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi again everyone,
OK since OpenStack, OpenCard, and preOpenStack all don't work on v2.7.4 on
Mac OSX how do I work around it? If it matters I'm not using a standalone.
Joe, I haven't experienced this problem, but from reading
Éric-
I just tried your test stack in 2.7.4 and it seems to be working
properly under Windows 2000, at least within certain limits. I won't
have a chance to test this on OSX until late tonight, but I'll report
back after that.
Double-clicking First Main Stack.rev opens that stack, waits two
Hi Everyone,
I just upgraded to v2.7.4 on my Mac OSX computer. I know the definition of a
new version is Out with the old bugs and in with the new ones but this is
ridiculous.
When I open my stack it doesn't see the OpenStack or the openCard handler
now. It did that with no problem in v2.7.1
I open my stack it doesn't see the OpenStack or the openCard
handler
now. It did that with no problem in v2.7.1. What changed?
Joe
Orlando
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe
Dear Sirs :
I need to use On Openstack structure.
Where I need to put this instruction? We are working with standalones.
I know about Openstack, but in Hypercard we had Stack Script.. but in
Revolution, i dont know where to put this instruction.
Cordialmente,
Alvaro Abril
Gerente de Tecnología
:
Dear Sirs :
I need to use On Openstack structure.
Where I need to put this instruction? We are working with standalones.
I know about Openstack, but in Hypercard we had Stack Script.. but in
Revolution, i dont know where to put this instruction.
Cordialmente,
Alvaro Abril
Gerente de Tecnología
Hi Jim,
Thanks for coding up in a logical way something
I should have done myself, if I could have got my
head around it !. After absorbing your scripts and
playing around a little, I think I will end up finally
understanding message paths (after more than
10 years on HC) !
Best from Paris
Hi Jeanne,
This complements and clarifies Jims comments.
Thanks
and the Lord said - Let there be light -
and there was light !
and you could see for miles and miles !
-Francis
___
use-revolution mailing list
Hi All,
I remember a while back I saw something about the preOpenStack and
openStack handlers in Card 1 of the mainStack. Since then I have
always placed these handlers in Card 1 and passed them (via pass
command) to the Stack. However I can't seem to find that email
anymore, could
Hi Dave,
I remember a while back I saw something about the preOpenStack and
openStack handlers in Card 1 of the mainStack. Since then I have
always placed these handlers in Card 1 and passed them (via pass
command) to the Stack. However I can't seem to find that email
anymore, could someone
David Burgun wrote:
I remember a while back I saw something about the preOpenStack and
openStack handlers in Card 1 of the mainStack. Since then I have
always placed these handlers in Card 1 and passed them (via pass
command) to the Stack. However I can't seem to find that email
anymore
Moi:
The Rev Docs (at least the old ones on my Mac) are wrong.
Actually, it depends on where one looks:
The Dictionary descriptions of preOpenStack and openStack say they are
sent to the stack; but if one consults the old Dictionary's index
showing all messages received by a card, both
a
good reason.
Initialization of course needs to be done only once, and the
mainStack's first card will be the first recipient of the startup,
openStack, and preOpenStack messages. The startup message is only
sent at runtime (the IDE gets it in development), so to get
initialization
of course needs to be done only once, and the
mainStack's first card will be the first recipient of the startup,
openStack, and preOpenStack messages. The startup message is only
sent at runtime (the IDE gets it in development), so to get
initialization in both development and runtime I use
, right in the user's current session.
Initialization of course needs to be done only once, and the
mainStack's first card will be the first recipient of the
startup, openStack, and preOpenStack messages. The startup
message is only sent at runtime (the IDE gets it in
development), so to get
David Burgun wrote:
Also I am not clear of the path the preOpenStack and openStack
handlers take. For a mainStack I'm guessing its:
mainStack:Card1:preOpenStack and if not defined mainStack:
preOpenStack.
But how about a sub-stack?
subStack:preOpenStack ??
For a diagram of the firing
Hi Dave,
In the documentation, it clearly states that the OpenStack and
preOpenStack are sent to the destination card in the stack,
which will usually be card 1 (unless otherwise specified). So
your remember is correct. I had problems in this area before
I read the documentation
Dave,
You seem to have opened (a small but tangible) Pandora's box.
Several responses confidently talk about the openStack being
sent to Card 1.
Either of two things :
1 - They only have 1 card stacks ... (so it works !)
2 - They don't read the same documentation as I do
(Rev 2.6.1
the message was sent.
Exceptions can be when the lock messages is true and when there is more than
one 'on openstack' handler in the message path without the 'pass openstack'
code line at the end of the handler.
Hope this helps. Remember, there are a lot of complex, smooth-running apps
out there using
I assume this means the openStack script in whatever card
you FIRST go to in the stack This could cause a problem if
you have an openstack in a sub-stack !
Ahh, you are now bring up an event question 1st 2nd 3rd.
the setup
Main Stack - no scripts or buttons needed
At 11:23 PM +0200 3/30/2006, Francis Nugent Dixon wrote:
The doc clearly states the destination card. As I often :
go to card x of (sub)stack y
I assume this means the openStack script in whatever card
you FIRST go to in the stack This could cause a problem if
you have an openstack
Francis,
One more small point. When I drop my files onto (would
you believe it ?) a Lexar JumpDrive, and move to the PC,
I find that I have twice the files I thought. I get the same
number of Alias ? files, equivalent to the files I copied.
How do I remove this problem ?
I have simply
Francis,
One more small point. When I drop my files onto (would
you believe it ?) a Lexar JumpDrive, and move to the PC,
I find that I have twice the files I thought. I get the same
number of Alias ? files, equivalent to the files I copied.
How do I remove this problem ?
I have simply
What this article doesn't say is what happens if you don't see both
file, then what does not 'safely ignoring' the file do? Is it unsafe
to delete the file in some cases?
And how does the file get put back together? Does the OS know how to
do this?
The second new file has the name of
Those prefixed files are created everytime you copy something from
HFS, HFS+ partitions to some flat file partition such as CDFS, Fat32,
Ext2... The finder creates it so that it does not lose resource fork
information. Deleting it might endanger your app depending on how the
app was
This is exactly the same problem I had with my students last week. Only
neither one would open.
Judy
On Thu, 9 Mar 2006, Rob Cozens wrote:
Francis,
One more small point. When I drop my files onto (would
you believe it ?) a Lexar JumpDrive, and move to the PC,
I find that I have twice
Hi to all,
and thanks for your comments about the .xxx files when
moving from Mac to PC,
I think the name of the thread has now changed to
What the h are these files ?.
I more or less guessed what the files were. My problem
is not what they are for, but HOW TO STOP THEM FROM
BEING COPIED,
Francis Nugent Dixon wrote:
and thanks for your comments about the .xxx files when
moving from Mac to PC,
I think the name of the thread has now changed to
What the h are these files ?.
I more or less guessed what the files were. My problem
is not what they are for, but HOW TO STOP THEM
When you zip the files they are joined into one file, which in my
experience, allows them to survive the transit through the many
routers and other pieces of gear on the internet. This file is
usually smaller than the sum of the parts as well so there are some
time savings involved in
I more or less guessed what the files were. My problem
is not what they are for, but HOW TO STOP THEM FROM
BEING COPIED, when I move from Mac to PC. Simply
because they are a PAIN ! Sometimes I copy folders with 200
or 300 files from my Mac to my PC, and I can tell you, ignoring
these .xxx files
Hi Francis,
You say :
| The main issue I had was created by moving uncompressed stacks from
Mac
| to PC.
|
| Once I began compressing stacks on the Mac decompressing on my
TPC,
| all but minor problems went away.
Could you clarify just a little please ? My curiosity is aroused !
Hi Rob,
Thanks for the clarifications. I will zip my files now before
transferring, although I would love to know WHY this solves
problems.
One more small point. When I drop my files onto (would
you believe it ?) a Lexar JumpDrive, and move to the PC,
I find that I have twice the files I
Morning Francis,
I have other problems moving to the PC platform,
The main issue I had was created by moving uncompressed stacks from Mac
to PC.
Once I began compressing stacks on the Mac decompressing on my TPC,
all but minor problems went away.
Rob Cozens
CCW, Serendipity Software
Rob,
You say :
| The main issue I had was created by moving uncompressed stacks from
Mac
| to PC.
|
| Once I began compressing stacks on the Mac decompressing on my TPC,
| all but minor problems went away.
Could you clarify just a little please ? My curiosity is aroused !
Thanks
Thanks to Rob, Charles and Jacqueline for their counsel.
I finally read up the documentation on openStack !
(I thought it would be the same as in HyperCard,
but no). It says Put script in first card script (strange
place to put it !). So I did, and now it works.
You learn every day .
I
Hi Francis,
You wanted my openStack script, so here it is.
But I can't see anything in there that can cause
a problem. I hope it is easy to read with the folding.
It works perfectly well when I type OpenStack in the
message box (on my Mac).
Does your stack have a preOpenStack or preOpenCard
Hi from Paris,
I have just run into my first Platform problem, but in fact,
my problem started on my Mac, and hasn't gone away !.
I finished developing a stack on my Mac. During development,
I couldn't get it to run the OpenStack script (why I don't know).
I found that when using Stack Runner
Francis Nugent Dixon wrote:
So, back to the Mac to create a button to execute openStack,
then back to the PC. When I click on the button on the PC,
nothing happens, so I am back to square one. What is going
wrong, or more specifically, what am I doing wrong ?
It sounds like a platform-related
problem started on my Mac, and hasn't gone away !.
I finished developing a stack on my Mac. During development,
I couldn't get it to run the OpenStack script (why I don't know).
I found that when using Stack Runner, OpenStack WAS executed,
so while I was testing on the Mac, each time I loaded, I
Hi Jacqueline,
You wanted my openStack script, so here it is.
But I can't see anything in there that can cause
a problem. I hope it is easy to read with the folding.
It works perfectly well when I type OpenStack in the
message box (on my Mac).
Thanks for looking.
-Francis
Francis Nugent Dixon wrote:
Hi Jacqueline,
You wanted my openStack script, so here it is.
But I can't see anything in there that can cause
a problem. I hope it is easy to read with the folding.
It works perfectly well when I type OpenStack in the
message box (on my Mac).
I'm not sure why
Richard,
But in the last seven years I haven't written an app in which the
mainStack has more than one card;
That's interesting as that ability is one of the most
useful properties I've found in Rev. It's something
RealBasic flounders on. It has an object you can drop
on a Window that
On Feb 26, 2006, at 11:14 PM, Arthur Urban wrote:
Richard Gaskin wrote:
Arthur Urban wrote:
Is there a way I can detect when my main stack receives the
openStack message versus when my substacks receives the message
and pass it all the way down to the mainstack? I do once only
Is there a way I can detect when my main stack receives the openStack
message versus when my substacks receives the message and pass it all
the way down to the mainstack? I do once only initialization in my
mainstack, and I can't seem to reliably detect when a substack is
triggering
Richard Gaskin wrote:
Arthur Urban wrote:
Is there a way I can detect when my main stack receives the openStack
message versus when my substacks receives the message and pass it all
the way down to the mainstack? I do once only initialization in my
mainstack, and I can't seem to reliably
Arthur Urban wrote:
Richard Gaskin wrote:
If you put your mainStack's initialization into the card script of
your mainStack you never need to worry about substacks triggering it.
That sure is mighty clever...I might even have to do that. I'm surprised
that there is no official and correct
on preOpenStack
if the short name of this stack = the short name of me then
-- do initialization
end if
end preOpenStack
Maybe this is the better way, because you can control the message even if
your main stack has more than one card.
Greetings
Paul Claude
the socketTimeoutInterval to 10
if the windows is klimax
then accept connections on port 967 with message newconnect
else accept connections on port 9678 with message newconnect
send doGlobalsInit to btn metier
openstack
open file Lepath rev-as_log.txt for append
if the result
Hi,
Most of my apps are using both the preopenstack and openstack
handlers at launch. It seems the Rev 2.6.1 engine is unable to catch
them anymore, under the Mac OS X 10.4.3 platform at least.
All works well again, as expected, in using the Rev 2.6 issue under
the same OS X platform
Le 8 déc. 05 à 17:29, Eric Chatonet a écrit :
Hi Pierre,
I isolated a line that seems to be always false since you have more
than one window open (the message box for instance used at the
beginning of your preOpenStack handler).
With your code port 9678 will always used.
I don't if that
Thanks for your help. Also, thank you Sarah and Nicolas. It seems
odd though that the openstack handler isn't called automatically when
the new stack window first comes up, no matter where it is being
opened from.
Mark
On Jul 19, 2005, at 10:26 PM, Chipp Walters wrote:
oops, I
Ok, I'm feeling pretty dumb, but why doesn't my openstack handler
execute when my stack opens? What am I not getting? (I type
openstack into the messagebox after opening and all is well, but the
handler doesn't execute when opening my stack from scratch.)
Mark
I hope someone more knowledgeable jumps in but...
Perhaps another stack is handling the openStack
message before it arrives to your targeted stack?
Or you might want to try preOpenStack instead.
--
Nicolas Cueto
___
use-revolution mailing list
use
the openStack
message before it arrives to your targeted stack?
Or you might want to try preOpenStack instead.
--
Nicolas Cueto
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
Ok, I'm feeling pretty dumb, but why doesn't my openstack handler
execute when my stack opens? What am I not getting? (I type
openstack into the messagebox after opening and all is well, but
the handler doesn't execute when opening my stack from scratch.)
I had the feeling that the open
Mark,
Here's what I would do:
First, I would put an 'on OpenStack' handler in the first card script of
the stack.
then save it, close Rev, open Rev, choose the browse tool, and open your
stack. See if the debugger gets called. If not, then I would suspect
there's an openStack handler
oops, I accidently deleted the 'first part' ;-)
Chipp Walters wrote:
Mark,
Here's what I would do:
First, I would put an 'on OpenStack' handler in the first card script of
the stack.
on openStack
breakpoint
beep
end openStack
then save it, close Rev, open Rev, choose the browse
Hello List,
(B
(BHere's the story. During the mouseUp of a mainstack button, a substack gets
(Bopened as modal. However, soon as that substack appears onscreen, debugging
(Bshows that the "on openStack" of the mainstack's stack-script has
(B(unexpectedly!) been called.
(B
?Hello List,
Here's the story. During the mouseUp of a mainstack button, a substack gets
opened as modal. However, soon as that substack appears onscreen, debugging
shows that the on openStack of the mainstack's stack-script has
(unexpectedly!) been called.
well, expectedly actually
I guess
On 12/3/04 12:57 PM, Steve Bonham [EMAIL PROTECTED] wrote:
Can anyone tell me what's going on?-- or rather why my handlers are
being ignored?
It's possible that your stack isn't being fully purged when you close it and
reopen it. Check to see is Purge window on close and Purge stack on
close
put line 2 of it into myVariable
etc.
in both on OpenStack and on PreOpenStack handlers (they are
located in the stack script) result in no activity when I exit and
reopen the stack.
Funny thing is;
IF I type Openstack or PreOpenstack into the message box
and hit enter-- after
1 - 100 of 129 matches
Mail list logo
