Bonsoir Richard and Graham,
If Richard has not been so timely with his reply :-)
I fully agree but I did not want to not make things too complicated.
Actually, the architecture I often use has three parts:
. A component, all calls of which refer mainly to one or more
libraries (of course, the
Graham Samuel wrote:
I had just worked out for myself that a set of re-usable substacks was
the solution to my "component" issue. The only downside is that since
the material is in a substack, usually I will have to use "send" to
invoke the handlers in the component, but that's OK really.
Thanks Eric
I had just worked out for myself that a set of re-usable substacks was
the solution to my "component" issue. The only downside is that since
the material is in a substack, usually I will have to use "send" to
invoke the handlers in the component, but that's OK really. I will
s
Bonjour Graham,
A library is a collection of handlers put in a stack's script only.
The purpose of a library is to make some particular code routines
available (text, menu, etc.).
Usually, a library is a 'blank' stack with a single card and no control.
Just the script of the stack is used an
Thanks Richard for your reply. As you can see, I am stumbling a bit
over this, feeling my way. I would like to cut down on the experiments
which is why I'm asking questions on this list.
Thanks very much for the reference to your article. I think I do
understand the Rev message path, and I
Graham Samuel wrote:
> I am trying to construct a library by writing stacks and
> inserting their scripts into the message path with 'start
> using'. So far, so good. Then I wanted to set a custom prop
> in a library stack, and RunRev silently rejected this, presumably
> because the stack although
This is a bit of a newbie question, even though I've been using RunRev
for a very long time. Embarrassing, but there you are.
I am trying to construct a library by writing stacks and inserting
their scripts into the message path with 'start using'. So far, so
good. Then I wanted to set a cu