The only keyboard shortcut I can find to insert a variable is CTRL-0. This colors the left side
of the status bar and gives you the entire list of user variables with -- with "Not Applicable" as the
highlighted choice. It appears that you have to traverse the list with the mouse pointer and
click on the desired variable.
This is just as cumbersome as calling up the variables pod and double clicking on the
variable you want.
Is there a way to define a keyboard shortcut to insert a particular variable?
No need to use the mouse. After you press the ctrl-0 to trigger the shortcut, just start typing the variable name that you want. The list of variables in the status bar will jump to the matched string as you continue typing. Depending upon your naming convention used, you should be able to home in on a desired variable in a few keystrokes.
This method is used for a number of other catalog lists as well.
Yes, that is what I've tried but it doesn't seem to work.
When I type CTRL-0, the list appears as described above, with "Not Applicable" in the
dropdown list selection box. The variable name I want is SM2, and when I start typing SM2,
the box displays "Section Number" as soon as I hit S, and stays that way even if I type
all three characters.
However, if I display the drop-down list and click on SM2, the variable is inserted as expected.
Which version of FM (including point release info) are you using? FWIW, it works just fine for me - I tried your specific instance and the first "s" shows the "Section Number" and the "m" then jumped to the "SM2" variable.
I just updated to 10.0.2 and the behavior is the same.
I can't tell you the version number I had been running because I couldn't find an "About" button.
I thought that FM checked for updates when I installed it from a 10.0 CD. Applications typically check
for available updates when you install and register and let you choose whether to update.
So Adobe doesn't inform you of new FM updates either?
I really appreciate the help I get from this forum. Even though the update installation didn't
say I had to reboot, I'll try that and let you know whether that changes the behavior.
I'd reboot and check right now except that I have a gazillion things open while I work on
the client's document.
But it's not a life-or-death situation. I may even retain my sanity while trying to figure this out...