mouseDown cripples menuPick

Anything beyond the basics in using the LiveCode language. Share your handlers, functions and magic here.

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

jacque
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 7216
Joined: Sat Apr 08, 2006 8:31 pm
Location: Minneapolis MN
Contact:

Re: mouseDown cripples menuPick

Post by jacque » Wed May 16, 2018 6:19 am

bogs wrote:
Wed May 16, 2018 6:12 am
@Jacque-
Hm, I think I almost understand that. I'm not sure I agree with it being that way, but it isn't like I'd be changing it either.
Better get used to it, it's been that way since 1987. :)
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com

bogs
Posts: 5435
Joined: Sat Feb 25, 2017 10:45 pm

Re: mouseDown cripples menuPick

Post by bogs » Wed May 16, 2018 6:46 am

Well, I s'pose that being so recent a change, I kin get used to it. 'sides, I'm sure you'll be able to calibrate my perspective if needs be (translation: deliver a wop upside the head) :D
Image

dunbarx
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 9587
Joined: Wed May 06, 2009 2:28 pm
Location: New York, NY

Re: mouseDown cripples menuPick

Post by dunbarx » Wed May 16, 2018 3:03 pm

Jacque.

I understand the difference between exiting to top and exiting a handler. I just did not appreciate that sending a menuPick message from a menu button was dependent on mouseDown, an event which seemed to have occurred in the distant past.

I would have thought that displaying the menuItems was triggered by mouseDown, but that menuPick was triggered by mouseUp. That is what I was struggling with. No problem anymore, now that I know mouseDown rules both.

Craig

Post Reply

Return to “Talking LiveCode”