Hey there everyone-
I'm using Filemaker Advanced 8.5 for Windows. My question: when a user
has tabbed to a button, and it is selected, s/he can then "click" the
button by pressing the space bar or the Return key, but not,
apparently, the Enter key. Is there any way to change this behavior or
work around it?

My users are very used to using the numeric keypad, and if I tell them
they can't anymore, they won't be very happy with me.

Thanks in advance for any input-
Nate

and part 2 to this question (if I may add to the thread) is if the
user is in a field, can they press enter or the return key to press
the default button? It is very standard windows feature and saves
having to go for the mouse each time.

I know this has been asked in the past but I can't find any
satisfactory answer.

Tim, there is no such thing as a default button.

Not unless you are already in a script, then the default is to continue the
script (With the numeric enterkey)

Keep well, Ursus

"Tim" <tswalton (AT) gmail (DOT) com> schreef in bericht
news:1173171485.016403.14050 (AT) v33g2000cwv (DOT) googlegroups.com...

I'm still sad this is missing.
It was missing when filemaker was only available for macs, because
macs didn't have this feature either.
But this was 10 years ago or more.
I hearby register my grumble.

Tim

On Mar 6, 9:00 am, "Tim" <tswal... (AT) gmail (DOT) com> wrote:
I think I may have discovered a solution (to my problem at least).
Here was my problem exactly: my users enter a field, then use the
numeric keypad to enter a number. Then they want to press the numeric
Enter to tab to a button to execute a script, which is easy to set up.
But then, they want to press Enter again to execute the script, rather
than having to press Return or Space. Impossible? Maybe not.
So, here is my workaround: change the field to a button. When the user
clicks into the field (or uses a Ctrl key combo I set up with custom
menus) the script first sends them to the field, then pauses
indefinitely. Then, when the user presses Enter, the script executes
the relevant button script. Mission accomplished right?
Well actually this brought up a problem. Now if the user enters the
field, types in data, and presses return or spacebar instead of enter
they will tab to the button and execute the script that way, which
leaves the original script still paused indefintely. Solution? Set the
button properties to "Halt current script".
So, now I have a field where users can enter a value, and then by
pressing Enter, Return or Spacebar (possibly twice) execute a script,
which was my goal. Sweet.
Note, all of this only works if the Status Area is hidden.
Look forward to hearing if my solution has massive flaws.
Nate

And it has the innate problem with running scripts other then the script
waiting for a button click

Ursus

"NScheffey" <NScheffey (AT) gmail (DOT) com> schreef in bericht
news:1173190595.223833.149840 (AT) v33g2000cwv (DOT) googlegroups.com...