[Framers] Weird Framemaker 10 behavior

[Robert Lauriston]

I saw similar behavior with various pods in FM9 and FM10. Haven't used
more recent versions to know whether Adobe ever got around to fixing
it.

On Mon, Aug 22, 2016 at 10:45 AM, Tammy Van Boening
<tammyvb at spectrumwritingllc.com> wrote:
> FM 10, Win7, 64-bit: all patched and current
>
> I have many variables in the book that I am developing for a software
> client. I use the Keyboard shortcut of CTRL + 0 to access the variable list,
> and then keyboard shortcuts to scroll through the long list, for example,
> "PR" to scroll through the list of Product variables (Product 1, Product 2,
> and so on). Nine times outta' ten, this works beautifully and then blam. .
> .for no reason, after using the keyboard shortcut of CTRL + 0, instead of
> getting an opened variable list, I get the message "Not Applicable," which
> means that I have to stop, go to Special > Variables, and then manually
> scroll the list. This is a real pain with such a big manual to create - I
> prefer to keep my hands on the keyboard and this shortcut function helps in
> that endeavor.
>
> I haven't been able to tie this behavior to any action in the file - there
> aren't any issues scrolling/saving the file, the file hasn't crashed. .
> .it's  just like FM loses its little mind and just decides it doesn't want
> to remember keyboard shortcuts.
>
> Has anyone else experienced this behavior?   If so, did you ever figure out
> how to make it stop?