a new problem

[chipsm]

All of a sudden, my "on MouseUp" doesn't work on my scrolling table field. My "on MouseDOwn" does work on this field.
Has anyone seen this happen?
all other field in my app work with the "on mouseUp"
Update: this problem seems to be specific to my application.
Now, what to look for?

[jacque]

It happens on mobile if the field has a native scroller. MouseUp isn't sent at all in that case. Is your stack running on a mobile device?

If desktop then the most likely reason is that there's a mouseUp handler earlier in the message path that's trapping the message.

[chipsm]

thanks Jacque.
I it is om the desktop and I have been looking for another "on mouseUp" , so I guess I need to search again.
I know that I was calling an "on mouseUp" elsewhere but I will look again.

[dunbarx]

Is it possible that there is a mouseUp handler farther along the message path?

When you do your search (I assume with the "Find and Replace..." tool in the "Edit" menu) try searching ALL open stacks. Hey, you never know.

Craig Newman

[chipsm]

Hey Craig, Thanks for the tip.
I actually looked everywhere that I could find. I know it's there but where?
I finally started remarking out sections of my scripts to search for the affected script.
I can't find it anywhere.
I beginning to think that it is somewhere that is hidden and am actually backing up to several versions where this does not happen.
I actually have a version where this anomaly doesn't happen and will be changing other scripts to get back to where I want to be.
This seems to be one of those things that may be a "forever mystery" at least for me.

Thanks to all for the help.

[dunbarx]

Chip.

I finally started remarking out sections of my scripts to search for the affected script.

Huh?

Um, what about the "Find and Replace..." tool? You do use that, right?

Craig

[chipsm]

Yes, I tried that too.
I tried everything.
I have taken the time to rewrite my code and I seem to have gotten rid of the hidden culprit, wherever it is.

[dunbarx]

Sometimes the default "phantom" button mouseUp handler can be made "real" without your realizing it. This has happened to me, though it is invariably at the button level, and affected group or card handlers ostensibly above the scripts in a particular button.

Sorry, Jacque.

But as long as you are up and running...

Craig

[chipsm]

That's something to keep in mind.
Thanks.