User Guide: I tell myself periodically to read the whole thing (be never
do…tinyDictionary has me hooked) … here it is, as you says, clearly stated on
page 105
If background behavior is false, the group is in the message path for all
controls it owns, but is not in the
message path of any
On 12/10/19 9:20 PM, Richard Gaskin via use-livecode wrote:
The Message Path discussion starts on p 101, with a pretty good diagram
on p 102, including a distinction between Groups and Backgrounds.
OMG - there's documentation? Admittedly I haven't looked at the User
Guide in quite a while.
The PDF files are generated from .md files. The guides are split between
two locations:
https://github.com/livecode/livecode/tree/develop/docs/guides
https://github.com/livecode/livecode-ide/tree/develop/Documentation/guides
Thanks,
Brian
On Wed, Dec 11, 2019 at 12:21 AM Richard Gaskin via
Richard, I'm not sure you were posting this to the right forum. You see, this
is the Livecode forum. We don't need no stinking User Guides! :-)
Bob S
> On Dec 10, 2019, at 21:20 , Richard Gaskin via use-livecode
> wrote:
>
> Paul Dupuis wrote:
> > Richard Gaskin, at one point, had a really
Paul Dupuis wrote:
> Richard Gaskin, at one point, had a really excellent diagram of the
> LiveCode message hierarchy. If he sees this post and still has it
> perhaps he could post a link to it.
Still there:
https://www.fourthworld.com/embassy/articles/revolution_message_path.html
Since I made
Just for reference, Dar Scott wrote a Primer in Message Mechanics:
http://pages.swcp.com/dsc/revstacks.html
Al
on Tue, 10 Dec 2019, Paul Dupuis wrote:
[snip]
Richard Gaskin, at one point, had a really excellent diagram of the
LiveCode message hierarchy. If he sees this post and still has it
Mark Waddington gave the answer if need.
I really want "shared groups" and not "backgroundGroups"
Then the scripts are encapsulated. I turned off backgroundBehavior on all
groups.
A click on top layer button (no script) now registers in the stack script with
its target.
I tried it, Yay!
On 12/10/19 11:39 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
So then to trap "the target" in the stack script, require putting
pass mousedown (or mouseWhatever)
in all the background groups (all of which contain their our MouseDown)
Correct?
Only if you want to handle
So if I have a button X with a mouseDown handler in a Group Y also with
a mouseDown handler and in my card script (or stack script) also have a
mouseDown handler
If I click on button X and I only want button X to handle the mouseDown,
I do not 'pass mouseDown' in the button X mouseDown
@ Mark Waddington
That's it! Thank you!
If you turn 'background behavior' off, then your shared group should no
longer receive messages after the card does.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe,
So then to trap "the target" in the stack script, require putting
pass mousedown (or mouseWhatever)
in all the background groups (all of which contain their our MouseDown)
Correct?
remember the use case:
we do not want and script in *any* button or top object that receives a click
or
Mark Wieder wrote:
> The syntax for describing the message path gets
> pretty gnarly.
It gets somewhat simpler when we consider the origins of the object
model, though admittedly this is help more for us ol' timers than
newcomers.
For newcomers I just don't mention backgrounds at all unless
On 12/9/19 11:13 AM, Alex Tweedly via use-livecode wrote:
I think the correct (and nit-picky) statement is ...
Mark Weider says "A background group will definitely get the message
before the stack
script does. Also any script being used as a behavior **for the
background group**."
**and
On 12/9/19 6:30 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
In this use case,
- the button "starWidget" is a "standalone" button on an independent
layer on the card and not a part of any group
-- @Jacque... the groups that are trapping the mouseup I are
background groups using on
On 2019-12-09 14:30, Sannyasin Brahmanathaswami via use-livecode wrote:
-- background groups: "encapsulated" only receive mouse/touch events
from objects that are contain in "itself" -- group
-- behaviors: "encapsulated": only receive mouse events for the object
or group the behavior is
On 12/9/19 6:30 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
In this use case,
- the button "starWidget" is a "standalone" button on an independent layer on
the card and not a part of any group
-- @Jacque... the groups that are trapping the mouseup I are background groups
using on
I use groups in use cases where I want a on mouseDown script in the
group to respond to any mouse click anywhere in the rect of the group,
so, no, groups should not ONLY respond to mouse messages passed though
object contained in the group
If you have groups where you need to pass a
In this use case,
- the button "starWidget" is a "standalone" button on an independent layer on
the card and not a part of any group
-- @Jacque... the groups that are trapping the mouseup I are background groups
using on various card.
Mark Weider says "A background group will definitely
On 12/8/19 4:04 PM, J. Landman Gay via use-livecode wrote:
I take that back, the card group shouldn't get the message. Sounds like
something else is wrong.
A background group will definitely get the message before the stack
script does. Also any script being used as a behavior.
--
Mark
I take that back, the card group shouldn't get the message. Sounds like
something else is wrong.
On 12/8/19 5:24 PM, J. Landman Gay via use-livecode wrote:
Is the group that receives the mouseUp a card group or a background
group? If I remember right, messages go from the button, to all card
Is the group that receives the mouseUp a card group or a background
group? If I remember right, messages go from the button, to all card
groups, then to the card, then all background groups, then to the stack.
So if it's a card group, it will get the message before the stack does.
On 12/8/19
ire?
Craig
-Original Message-
From: Sannyasin Brahmanathaswami via use-livecode
To: How LiveCode
Cc: Sannyasin Brahmanathaswami
Sent: Sun, Dec 8, 2019 2:56 pm
Subject: Groups in the message path: Trapping Mouseup
I think this a old problem that is re-surfacing. Or else it is known….
9.6 dp1, in t
I think this a old problem that is re-surfacing. Or else it is known….
9.6 dp1, in the message path different independent groups are not encapsulated.
button "starWidget"
-- has no script
-- is not a part of any group
Stack script:
on mouseup
put the short name of the target
23 matches
Mail list logo
