Re: use-livecode Digest, Vol 168, Issue 50

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: use-livecode Digest, Vol 168, Issue 50

Tom Glod via use-livecode
sez “J. Landman Gay" <[hidden email]>:
> The original issue that influenced this one was how to provide a larger hit
> zone on an SVG widget. How would this property work for that?
I’m thinking that a single line of code would suffice:

set the clickableRegion of widget “Fred” to ListOfPoints

As i’ve noted previously, the engine *already* handles clickable regions for *every* control, and my proposal ‘merely’ (he says, optimistically…) opens up the engine’s mechanisms to the extent of granting developers the opportunity to override the engine’s default “define the clickable region” behavior. If a dev is happy with the default clickable regions provided by the engine, that dev can just ignore the clickableRegion property and everything should work the same as it always did… but if a dev *isn’t* happy with the default clickable regions provided by the engine, *then* that dev can mess around with the clickableRegion property.



   
"Bewitched" + "Charlie's Angels" - Charlie = "At Arm's Length"
   
Read the webcomic at [ http://www.atarmslength.net ]!
   
If you like "At Arm's Length", support it at [ http://www.patreon.com/DarkwingDude ].

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: use-livecode Digest, Vol 168, Issue 50

Tom Glod via use-livecode
> > JLG wrote:
> > The original issue that influenced this one was how to provide a
> > larger hit zone on an SVG widget.
> > How would this property work for that?

> Quentin L. wrote:
> I’m thinking that a single line of code would suffice:
>
> set the clickableRegion of widget “Fred” to ListOfPoints
>
> As i’ve noted previously, the engine *already* handles clickable
> regions for *every* control ...

No. Sadly (or luckily, depending on one's point of view) a widget is
not an ordinary control. This has to be implemented in the widget.

To see this write one that handles only the mouse events, not to
speak of a clickable region.
Even this is hard to control: who gets first which mouseEvent, the
widget's script or the widget.
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode