finding "global" procedures
Jon
jbondy at sover.net
Wed Jun 1 20:36:18 EDT 2005
I'm not sure I want to insert a message handler in the normal message
passing hierarchy. I don't want it to ever be called automatically. I
want to be able to call a handler manually, from another handler. At
the moment, unless the two handlers are in the same "file", I can't call
it because I can't "see" it. I just want to be able to declare a
handler that can be invoked manually from anywhere in the program. This
is a visibility issue.
I hope I'm making this clear[er].
:)
Jon
Dan Shafer wrote:
> You raise an important issue. To program effectively in Revolution,
> you really need to understand the message-passing hierarchy. Nobody
> has explained it better than Richard Gaskin at:
>
> http://www.fourthworld.com/embassy/articles/revolution_message_path.html
>
> There is no concept of global handlers. If you want a handler to be
> accessible to all the message handlers in a given stack file, just
> put it in the mainstack. If you want it available across multiple
> stack files, you'll need to create it as its own mainstack and then
> include it by making it a library with "start using."
>
> HTH
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Dan Shafer, Co-Chair
> RevConWest '05
> June 17-18, 2005, Monterey, California
> http://www.altuit.com/webs/altuit/RevConWest
>
> On Jun 1, 2005, at 3:31 PM, Jon wrote:
>
>> I want to write some utility routines that can be used by lots of
>> message handlers. Where do I put those utility routines so that the
>> event handlers can "see" the utility routines? Do I have to declare
>> them as Global, or just put them in a particular place?
>>
>> Thanks!
>>
>> Jon
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>
>>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>
More information about the use-livecode
mailing list