Seems like the "focus" is lost on mouseup, and so I can't grab the button's object name. Hopefully, I'm missing something obvious...

I think you will just have to be happy with passing a value thru the script parameter for the button in order to identify what button was activated.

Focus is not lost. Focus is NOT passed to a button by clicking on it - only by tabbing into it.

Sorry about the loose use of the word "focus," comment. I'm building a technique and was hoping not to edit the button's script parameter. If you both don't see anyway of doing this, then it's just not possible. Rats.

Somehow using the tab order might be a cludge?...Go to next object, go to previous? Nah...

If you both don't see anyway of doing this

You haven't told us what "this" is. I am guessing you need to know which button was clicked. Can't see why you would want to avoid using the script parameter for this.

Don't mean to be obtuse, just not wanting to bother you all with the details. We're trying to build what we think is the ultimate list view sort script.

We have a button whose scriptparameter is a field object name. The script then goes to that object (field) and gets its field name. Once we have the field name, we set some globals which are read by a calc. The sort step always sorts the list on the calc field.

But, we're left with going into each button scriptparameter and changing the value for the object that we want the script to go to. We thought that if we named the button something like "Field1 btn" and use leftwords, we could avoid going into the button scriptparameter. We'd have matched pairs of buttons and field objects.

Yes, all this to avoid changing a button scriptparameter.

You will have to use script parameter for this. I guess I don't see what's the big deal with that.

Regarding "the ultimate list view sort script", see this thread:

http://www.fmforums.com/forum/showtopic.php?tid/188673/