Was: openstack or preopenstack confusing... Now "User Contributed Notes" for RunRev Dictionary

7 messages Options
Embed this post
Permalink
william humphrey-2

Was: openstack or preopenstack confusing... Now "User Contributed Notes" for RunRev Dictionary

Reply Threaded More More options
Print post
Permalink
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. But
now the information is in this great searchable resource.

Speaking of information for users that come later.  I just registered for
"User contributed notes" and I will put the information there about putting
these messages in the first card. I will also suggest a referral to the
"onstartup" message but that looks a little specialized. The Revolution
Dictionary could become greatly more usable as we add these kind of notes.
_______________________________________________
use-revolution mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
Sivakatirswami

Re: Was: openstack or preopenstack confusing... Now "User Contributed Notes" for RunRev Dictionary

Reply Threaded More More options
Print post
Permalink
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 and I think it is  something I used to know along with a
> myriad of other knowledge my gradually dying brain cells once contained. But
> now the information is in this great searchable resource.
>
> Speaking of information for users that come later.  I just registered for
> "User contributed notes" and I will put the information there about putting
> these messages in the first card. I will also suggest a referral to the
> "onstartup" message but that looks a little specialized. The Revolution
> Dictionary could become greatly more usable as we add these kind of notes.
> _______________________________________________
> use-revolution mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>  
_______________________________________________
use-revolution mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
Stephen Barncard-4

Re: Was: openstack or preopenstack confusing... Now "User Contributed Notes" for RunRev Dictionary

Reply Threaded More More options
Print post
Permalink
I didn't think *private* worked with any system messages....??


-------------------------
Stephen Barncard
San Francisco
http://houseofcubes.com/disco.irev


2009/11/9 Sivakatirswami <[hidden email]>

> 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 and I think it is  something I used to know along with a
>> myriad of other knowledge my gradually dying brain cells once contained.
>> But
>> now the information is in this great searchable resource.
>>
>> Speaking of information for users that come later.  I just registered for
>> "User contributed notes" and I will put the information there about
>> putting
>> these messages in the first card. I will also suggest a referral to the
>> "onstartup" message but that looks a little specialized. The Revolution
>> Dictionary could become greatly more usable as we add these kind of notes.
>> _______________________________________________
>> use-revolution mailing list
>> [hidden email]
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>
>>
>>
> _______________________________________________
> use-revolution mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
_______________________________________________
use-revolution mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
Richard Gaskin

Re: Was: openstack or preopenstack confusing... Now "User Contributed Notes" for RunRev Dictionary

Reply Threaded More More options
Print post
Permalink
In reply to this post by william humphrey-2
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
  Fourth World
  Rev training and consulting: http://www.fourthworld.com
  Webzine for Rev developers: http://www.revjournal.com
  revJournal blog: http://revjournal.com/blog.irv
_______________________________________________
use-revolution mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
Robert Brenstein

Re: Was: openstack or preopenstack confusing... Now "User Contributed Notes" for RunRev Dictionary

Reply Threaded More More options
Print post
Permalink
In reply to this post by william humphrey-2
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 of other knowledge my gradually dying brain cells once contained. But
>now the information is in this great searchable resource.

Warning: putting closestack on the first card may not always work as
expected -- that handler won't get called if the stack is closed
while user displays a non-first card. In other words, a multi-card
stack should have closestack on the stack level unless its
functionality pertains only to the first card.

Robert
_______________________________________________
use-revolution mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
william humphrey-2

Re: Was: openstack or preopenstack confusing... Now "User Contributed Notes" for RunRev Dictionary

Reply Threaded More More options
Print post
Permalink
In reply to this post by william humphrey-2
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 (it's the central part 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 <[hidden email]> wrote:

> 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 of other knowledge my gradually dying brain cells once contained.
>> But
>> now the information is in this great searchable resource.
>>
>
> Warning: putting closestack on the first card may not always work as
> expected -- that handler won't get called if the stack is closed while user
> displays a non-first card. In other words, a multi-card stack should have
> closestack on the stack level unless its functionality pertains only to the
> first card.
>
> Robert
>
> _______________________________________________
> use-revolution mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>



--
http://www.bluewatermaritime.com
_______________________________________________
use-revolution mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
J. Landman Gay

Re: Was: openstack or preopenstack confusing... Now "User Contributed Notes" for RunRev Dictionary

Reply Threaded More More options
Print post
Permalink
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 (it's the central part of the interface) but
> your comment makes me worry about the functionality of closeStack for other
> users.

It just depends on what the stack needs to do. In this case, since only
the mainstack uses a closestack handler, and the mainstack is open at
card 1 all the time, putting closestack into the card script is fine.
The handler will always be called. If your mainstack needed to see a
closestack handler from any card, then it would have to go into the
stack script (alternately, if all cards shared a background group, it
could go there.)

If you want the mainstack and all substacks to get the closestack
handler, put it into the mainstack's stack script.

If you want only some stacks to get a closestack handler, or if your
mainstack may close from a card other than card 1, put the handler into
the stack script and do a test inside the handler to see if the right
stack is frontmost before acting on it.

--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution