Better get used to it, it's been that way since 1987.
mouseDown cripples menuPick
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- VIP Livecode Opensource Backer
- Posts: 7216
- Joined: Sat Apr 08, 2006 8:31 pm
- Location: Minneapolis MN
- Contact:
Re: mouseDown cripples menuPick
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
Re: mouseDown cripples menuPick
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)
-
- VIP Livecode Opensource Backer
- Posts: 9587
- Joined: Wed May 06, 2009 2:28 pm
- Location: New York, NY
Re: mouseDown cripples menuPick
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
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