I suppose if it worked the other way around, the command would be append the
script of object in front
Bob
On Jul 18, 2012, at 5:34 PM, Dar Scott wrote:
On Jul 18, 2012, at 4:53 PM, Peter Haworth wrote:
This is all back to front to me….
OR
The first one now will later be last….
Hi,
That's very simple. One front script comes after the other. If the first front
script doesn't pass the message, then the second front script won't run. If
you're making a plugin, you need to pass the message and good developers do
this.
--
Best regards,
Mark Schonewille
Economy-x-Talk
Thank you Mark, I'm glad to hear that's how it works. I am, of course,
planning on passing the message.
I checked out Richard Gaskin's excellent write up on extending the message
path before asking this question, but it it doesn't really deal with this
situation - Richard, might be worth a note
Peter Haworth wrote:
I'm wondering what happens if two front scripts each contain a
handler for the same message.
...
I checked out Richard Gaskin's excellent write up on extending
the message path before asking this question, but it it doesn't
really deal with this situation - Richard,
On Jul 18, 2012, at 2:50 PM, Richard Gaskin wrote:
It may just need to be more prominent - in the section on Backscripts it
includes:
In LiveCode all libraries and backScripts can freely call
each others' handlers by name, with the order of insertion
only coming into play in the
Interesting, I would have thought the last inserted script would take
precedence, as in the old Military standing order, obey the last order first.
There is a lot of good wisdom to that.
Bob
On Jul 18, 2012, at 1:50 PM, Richard Gaskin wrote:
in such cases libraries take
precedence over
Thanks Richard, yes I was just reading the front script section.
Pete
lcSQL Software http://www.lcsql.com
On Wed, Jul 18, 2012 at 1:50 PM, Richard Gaskin
ambassa...@fourthworld.comwrote:
It may just need to be more prominent - in the section on Backscripts it
includes:
In LiveCode all
I read the dictionary entry as meaning that the last script inserted into
the front scripts will be executed before the first one, so the message
path starts at the last script inserted then prgresses through any others
until the first one inserted.
I don;t think any of this will be a problem for
Yes you have it right there Peter. I just read it myself, and the key is that
the order the scripts appear in the list is the reverse of the order they were
entered, which means the last insert goes at the top and then they scripts
follow the order of the list, meaning, much like the Military,
On 7/18/12 5:01 PM, Bob Sneidar wrote:
Yes you have it right there Peter. I just read it myself, and the key
is that the order the scripts appear in the list is the reverse of
the order they were entered, which means the last insert goes at the
top and then they scripts follow the order of the
Hi Jacque,
OK, well that contradicts the dictionary entry where it describes the exact
same mechanism for both front and back scripts, i.e. messages go the first
inserted script last and the last inserted script first for bot front
scripts and back scripts. Course, it wouldn't be the first time
On 7/18/12 5:53 PM, Peter Haworth wrote:
Hi Jacque,
OK, well that contradicts the dictionary entry where it describes the exact
same mechanism for both front and back scripts, i.e. messages go the first
inserted script last and the last inserted script first for bot front
scripts and back
Hi, Jacque!
I made the time.
Inserting a script into the back puts it at the front of the back.
That is consistent with the order in the backscripts.
I have not confirmed stack libraries, but if they are the same then adding
scripts in all methods put them at the front of the applicable
On Jul 18, 2012, at 4:53 PM, Peter Haworth wrote:
This is all back to front to me….
OR
The first one now will later be last….
OR
What goes up the chimney down but not down the chimney up?
You might be comforted by these words from The Reluctant Dragon (1941) to be
read with poetic
Thanks for taking the time to confirm that Dar.
Pete
lcSQL Software http://www.lcsql.com
On Wed, Jul 18, 2012 at 5:12 PM, Dar Scott d...@swcp.com wrote:
Hi, Jacque!
I made the time.
Inserting a script into the back puts it at the front of the back.
That is consistent with the order in
Peter Haworth wrote:
I just realized that the stacks that I insert as front scripts are
included in the Contents of a standalone application on a Mac.
I may decide to package some of those scripts and try to sell them
in the future but this makes them available to anyone who takes the
time
Thanks Richard, I knew it would be something simple!
Pete Haworth
On Jan 7, 2011, at 10:26 AM, Richard Gaskin wrote:
Peter Haworth wrote:
I just realized that the stacks that I insert as front scripts are
included in the Contents of a standalone application on a Mac.
I may decide to
17 matches
Mail list logo
