Executing scripts based on cursor position

[batesman666]

Ok, I'll have to explain this in very basic terms as I am not very versed in FileMaker or Scripting terminology, so please bear with me:

We have been using FM for 6 years now in our Videostore, my colleague created a snazzy little database solution for films, members and ordering which works just fine, there's just one little thing we've ben trying to find a solution for...

The layout for rentals contains 8 fields for entering the number of the film, a seperate button assigned to each of these fields triggers the various scripts needed for statistics, entering today's date, etc. Up until now we've had to press each button by mouse, i.e. enter film number in field number 1, press button number 1, film number 2, button number 2, etc. Doesn't increase workflow...

What I thought is that maybe it's possible to write a script that "notices" which field the cursor is momentarily in and then - maybe through QuickKeys or an Applescript - executes the appropriate script on the press of a Keyboard key (such as F12 or whatever).

Any ideas on how this could maybe be done?

Thanks in advance!

[cjaeger]

try an unstored calc, Status(CurrentFieldName) and a script based on the field. It may work, however, the Status(CurrentFieldName) is not updating in many cases.

But - there is a plugin that does mouse coordinates.

try jazzutils

http://www.jazzmedia.com.au

[batesman666]

well i'll be...

status did the trick, both of us are now kicking ourselves for not coming up with this any sooner. thank you so very much!

[TSilvan]

Better way to do this might be by setting up auto-entry by calculation options for the fields that grab into statistics. It would be an auto-entry bu calc formula like:

Case(not IsEmpty(OneOfYourEightFields), Status(CurrentDate))

So then when you enter anything in one of the eight fields, all the corresponding stats are filled in automatically with nothing to click and no buttons/keys to press.

[Ugo DI LUCA]

Hi,

You may want to use some looping scripts and lookup fields, but this is painful as I agree with Cjaeger about the Status(CurrentFieldName).

Here's an attachment that could help.

exitonfields.zip

[plechton]

Only in unstored calculations is there problem with some status functions that don't always update unless you force it.

Status(CurrentFieldName) is working fine always in scripts. That is what it is designed for.