Widgets "eating" mouseevents?

Klaus major-k klaus at major-k.de
Thu Jun 15 09:14:11 EDT 2017


> Am 15.06.2017 um 15:10 schrieb Mark Waddingham via use-livecode <use-livecode at lists.runrev.com>:
> 
> On 2017-06-15 14:37, Klaus major-k via use-livecode wrote:
>> Hi friends,
>> I know that widget ignore "mouseevents" (up/down/move etc.) if not
>> explicitley scripted in them.
>> OK, but is it neccessary that they also "eat" mouseevents? I hope not!
>> Example: card script:
>> on mousemove x,y
>>  put x && y into fld 1
>> end mousemove
>> Works until you e.g. place a "browser widget" onto the card.
>> No info in field 1 while the cursor is over the widget.
> 
> Widgets do need to post events they want script to receive (including mouseMove) so they have to be coded to allow this - we're still figuring out the best way for this to work to make things more uniform and to cut down on code in the widgets people write.
> 
> In regards to the browser widget, then that's a separate issue. It is a native control, so the engine doesn't get a look in at the events it gets at present (I have a vague idea how we might get this to work - but it is still a little vague at present!).
> 
> Warmest Regards,
> 
> Mark.
> 
> -- 
> Mark Waddingham ~ mark at livecode.com ~ http://www.livecode.com/
> LiveCode: Everyone can create apps

OK, thanks, so the answer to my question is: I have to live with it right now. :-/


Best

Klaus

--
Klaus Major
http://www.major-k.de
klaus at major-k.de





More information about the use-livecode mailing list