Passing mouse clicks up the object heirarchy

[jacque]

God-like or sewer. Take your pick.

More like sky worshipers or earth children. But I gave up the metaphor long ago. Messages travel toward the engine, which allows any visual representation the user likes. Scripts are "closer" or "farther away" from the engine.

Unless they're turtles.

[FourthWorld]

I belong to no political party, hold the same respect for all churches, and even treat left-handed people as I would right-handed.

But on this most important matter I take my stand: messages fall downward.

Yes, this is the hill I'm prepared to die on.

[richmond62]

But is beside the point of my OP

Richmond.

Your problem is solved, no? Just choose the way you want to do it. I like Jacque's idea, since images do not change their look when disabled.

Craig

Nope: I am putting this in each "floating" image:

Code: Select all

on mouseUp
send "mouseUp" to img "underLying"
end mouseUp

mainly because:

1. 'Tworx.

2. Cannot work out how to disable an image.

[Klaus]

...
2. Cannot work out how to disable an image.

Use the message box, the inspector does not provide this setting!

[richmond62]

...
2. Cannot work out how to disable an image.

Use the message box, the inspector does not provide this setting!

My emphasis added.

Well, that is something that needs "rectification":

https://quality.livecode.com/show_bug.cgi?id=22824

[jacque]

I belong to no political party, hold the same respect for all churches, and even treat left-handed people as I would right-handed.

But on this most important matter I take my stand: messages fall downward.

Yes, this is the hill I'm prepared to die on.

You can come down now, I have logical proof that you are correct. Consider the layering order of objects. Messages flow from the highest layer through to the lowest layer; backscripts and groups for example. Controls within a group have higher layer numbers than the group that contains them, and messages flow from the inner controls to the group. The highest-numbered control is on top of lower-numbered controls. Therefore, messages flow from top to bottom.

Quod erat demonstrandum.

[richmond62]

Quod erat demonstrandum.

Hmm . . .

"In rivers and bad government, the lightest things float to the surface." Johnny Cash

[dunbarx]

You cannot use layers of controls on a card to make your point. Those are all have the same "rank"; even in the upside down world Richard has dug his heels into, all diagrams show those sorts of objects grouped together at the same "level", that is, the same rank.

Not the same at all as "controls/cards/backGrounds/stacks/backScripts/engines" just to name the usual suspects.

I am over the hill, so cannot see Richard. But I know where he lives now.

Quod erat faciendum

Craig

[jacque]

Ah yes, but the map is not the territory. A diagram is not the behavior.

Quod whatever.

[SparkOut]

Quod whatever.

If it was a raven, then "Nevermore".

Or regarding the turtle messengers, they go downstream, which is determined by gravity. Yeah, Aeschylus, if it had been an apple, Newton might well have been superceded by millennia.

[richmond62]

https://quality.livecode.com/show_bug.cgi?id=22824

"Hello Richmond,

Thank you for the report.

Disabling an image does not change the visual representation of the image - it
just blocks the mouse clicks on the image.

I guess this was the reason that such functionality is not present in the
Property Inspector, since it might confuse new users.

We will update you when the status of this enhancement request changes.

Kind regards,
Panos"

Emphasis added by me.

Your thoughts on this?

[dunbarx]

Perhaps Panos slightly misused "blocks" when he meant "ignores"?

Craig

[FourthWorld]

...even in the upside down world Richard has dug his heels into...

Ah, but being upside-down I'm diving into it head first.

[richmond62]

Perhaps Panos slightly misused "blocks" when he meant "ignores"?

Craig

I hope so.

[richmond62]

Of course ignores can also be a pain in the bum . . .

We might want an object to ignore mouseUp commands but NOT mouseEnter commands.

NOT having 'disable' in the Properties palette is, I believe, an oversight,
as there are no visual cues to whether an object is disabled or not.
-

-
The left-hand image of a cat is disabled, the one on the right is not.