LiveCode Forums

Michael. I doubt it, given that, as I mentioned, rawKeysDown doesn't fire either when the menu is dropped. Hmmm. Just to be clear, in an open optionMenu, "mouseRelease" is sent. You're welcome. It is sent for the reasons discussed above, and possibly those reasons are even true. And since a message ...

Correct. The escapeKey message is not sent. But the keysDown function knows when the escapeKey is pressed, and that can be used to the same effect.

Craig

I see what you are all talking about. But one does not have to add additional stacks. I have used a single stack as a repository of one or more behaviors. You might say, "why not just place handlers normally in the stack script, and use the hierarchy"? Well, I could, and of course do. I guess it jus...

I think of this differently. I always extract the entirety of the DG with the dgText, do stuff in "ordinary" LC. and re-install. Thus I rarely distinguish between tasks involving one or more "cells", one or more rows or columns, or the whole shebang. This is just laziness on my part. But my comfort ...

Michael.

I told you this would be fun.

Craig

Jacque. Rereading, I now see what you are on about. This applies only to the escapeKey. None of the other control keys do this. Apparently, the "mouseRelease" message fires even if the cursor is within the rect, as long as the menu is open. It does not fire if closed. Does opening a menu essentially...

Jacque. The optionMenu is invoked externally, with "click at the loc of btn..." So when that happens, and the user clicks anywhere BUT within the rect of that optionMenu, mouseRelease fires. This was the intent of the OP, that the user would invoke the option, and then decide not to go there at all....

If I remember right there was last year a post by Mark Waddingham who said it was never intended to use "set the behaviour" to anything else than to a button. And that this may be restricted to buttons in future versions. I always thought that having a button as the only repository of a behavior wa...

Bogs. Hmmm. I have a mainStack "xxx" and its subStack "yyyy". I have a stack script in "yyyy", and set the behavior of "xxx" to the long id of stack "yyyy". I have to start using "yyyy" in order for something in "xxx" to work. If I stop using "yyyy", that functionality goes away. Back and forth... T...

I think the dictionary is misleading in this. It simply states that the pathname to the behavior stack must be of a certain form, to allow portability. This would lead one to think that if both stacks were open, LC would know to look for and use the behavior stack. After all (again, assuming both st...

Klaus.

Of course. I was sloppy, simply checking only the stack script.

Craig

Confirm this was never an issue on Mac. First I have heard of it anywhere. Anyway, the script of the "answer dialog" stack is" on resizeStack end resizeStack on openStack end openStack on preOpenCard end preOpenCard on openCard end openCard on closeCard end closeCard So where might any sort of timin...

In the meantime, I've made some fields that work like option menus, so that's my solution... Yes rolling your own, as we like to say (after all, most of us are old, old...) allows one to make tools that have functionality far beyond the native set. If that were not possible, much of the beauty of L...

Michael. You will have a much easier time when you learn just a little more vocabulary. Like learning any new language, this takes time and practice. To a point you made earlier, it is hard to know, unless you have a bunch of hours under your belt, where to look in the dictionary. So now every time ...

Michael. You are learning there is a slippery slope between being clever and making kluges. You tell me: In the script of the optionMenu button: on mouseRelease if the mouseLoc is within the rect of me and the keysDown = 65307 then answer "escapeKey pressed!" end mouseRelease So, kluge or cleverness...