On 03.03.2015 at 7:31 Uhr -0500 stgoldb...@aol.com apparently wrote:
The issue of a background group being in two places at once is not
quite clarified. Getting back to the script sequence below, when
there is a mouseUp handler in a background group, the message, on
clicking on the grouped
The issue of a background group being in two places at once is not quite
clarified. Getting back to the script sequence below, when there is a mouseUp
handler in a background group, the message, on clicking on the grouped button
goes from:
button -- group -- card -- stack
When clicking on
Stephen Goldberg wrote:
I think the bottom line is to be cautious about putting mouseUp
scripts in background groups, or to put a disclaimer in the group
at the beginning of the group handler the line (as mentioned in
the User Manual (pg 131, 5.3.9):
if the owner of the target is not me
Thanks for that explanation Richard. I finally get the difference between
sharedBehavior and backgroundBehavior. Seems like sharedBehavior is the one
to use for everything except old HC stacks.
On Tue, Mar 3, 2015, 7:14 AM Richard Gaskin ambassa...@fourthworld.com
wrote:
Stephen Goldberg wrote:
On 3/3/2015 9:13 AM, Richard Gaskin wrote:
The backgroundBehavior property is a tricky thing,
I think of it like this: A message to an object will always go to the
object's owner group(s) first, if any. After that it hits the card and
follows the normal hierarchy.
--
Jacqueline Landman Gay
While on the subject of out-of-the-normal message paths, I came across
another one a couple of months ago.
openControl messages are sent to the highest level group and then DOWN to
any of it's child groups which seems the opposite of the normal message
direction.
It gets more interesting though.
Richard, Very nice explanation of this. I always wondered about the
relationship between this properties.
Thanks,
Mike
On 3/3/15 10:13 AM, Richard Gaskin wrote:
Stephen Goldberg wrote:
I think the bottom line is to be cautious about putting mouseUp
scripts in background groups, or to
