Option menu strangeness
howard.bornstein at gmail.com
Fri Mar 18 22:38:36 CST 2005
Very strange. I also just ran into a very weird (and different) oddity
using combo buttons. Suddenly a combo button I've been using on a
stack stopped working. I was operating with a mouseup handler in it.
When it stopped working I checked the message watcher and sure enough,
no mouseup message was being sent. Everything else looked fine
(mousedown was sent, for example).
Here's where it gets really weird. If I copied the button to another
stack, mouseup was sent. Since the button's handler gets first crack,
I can't figure out how its mouseup message was getting hijacked. I'm
not using any frontscripts.
I resolved it by using the more traditional menupick message handler,
but I have no idea why a) a previously working button would change its
operation and b) why the mouseup message in particular suddenly
stopped being sent.
On Fri, 18 Mar 2005 23:28:28 +0000, Graham Samuel
<graham.samuel at blueyonder.co.uk> wrote:
> I'm developing an app under the RR IDE and one of the stacks shows a
> card with a lot of option buttons (menus) on it, allowing the user to
> pick stuff from a set of little lists and to see what has been picked.
> This has been working for ages: I read it by looking at the menuHistory
> of the buttons, and I can set them by setting the menuHistory also.
> Suddenly today for about half an hour the thing stopped working. When I
> clicked on (any) of the buttons, I saw the list of options, but they
> wouldn't "stick", I mean if the options were
> and B was showing, then picking A or C did nothing: the button reverted
> to B as soon as I let go of the mouse. After a bit the problem went
> away, leaving me totally mystified. I realise it must be something I've
> done, but I can't guess what it could be. Has anyone got any
> suggestions? BTW the IDE seemed to remain stable while all this was
> happening - no trouble with its menus or buttons. Strange.
More information about the use-livecode