Yes, many times previously and just now again, thinking I had missed something. According to this graphic from that article -

I would think my reasoning is sound. I am getting
'the target' from an
input event (mouseDown) inside of a
group.
If I click on a control outside of that group, I'm not sure why the message should be picked up by the group. It would seem bizarre if you are saying that because there is a group anywhere in a program, it's scripts will fire on any event when you haven't interacted with it.
I think I did finally see the reason because of that graphic, though, and my reasoning was perhaps too narrow. Since the group is also set to be a background, I guess that might be the reason (although it still strikes me bizarre).
Anyway, I finally added a work around to make sure I was getting the target only from the group -
Code: Select all
if the loc of the target is within the rect of group "grpNavigation" then
put the short name of the target into lclClicked
--answer lclClicked
end if
Although sufficient and working, I'd still like to know how to not get this result the correct way.