Skip to main content
W
waltk2
Participant
May 3, 2010
Question

FM9 Marker bug work-around

  • May 3, 2010
  • 1 reply
  • 407 views

If any of you have documents with large numbers (thousands) of markers, you may have noticed a performance problem in FM9.  When you open such a document, FM appears to "freeze" for up to several minutes while loading/opening the document.

One possible work-around would be to save as a setting whether Framemaker starts with the marker pod open or not.  I haven't been able to find a persistent setting that does this.  (if you know how to do this, please let me know).

Another possible work-around would be to close the "Marker" pod before opening the document.  This is not possible if Framemaker is being started by double-clicking on an associated document, or programmatically.

A third possibility would be to code a Framemaker add-in with the FDK that closes the Marker pod.  I haven't looked into this option yet (but have developed other add-ins with FDK).  If you what functions might be used to accomplish this, or where to find an example, please let me know.

a non-possibility is to permanently remove the markers from the document.  This doesn't work for me because the markers are an integral part of another application that uses them to know where insert/replace updated data from a database.

The best solution would be to fix the problem at its source - presumably some really poor programming in the product itself.

Any other ideas or suggestions?

    This topic has been closed for replies.

    1 reply

    Arnis Gubins
    Arnis Gubins
    Inspiring
    May 3, 2010

    Create your own custom Workspace that doesn't have any of the pods and use this. FM remembers the last workspace used and always opens with that.

    W
    waltk2Author
    Participant
    May 3, 2010

    Hi Arnis,

    Thanks for the quick response.  I tried this - successfully saved a custom workspace - but it doesn't load when I restart Framemaker.

    It sounds like a good suggestion, and I'm wondering if Framemaker starts with the default ("None") workspace because I get this message every time Framemaker starts:

    Cannot import ......fmreg.reg.  Error accessing the registry

    So this is probably a different problem that is preventing your solution from working.

    -Walt

    Michael_Müller-Hillebrand
    Michael_Müller-Hillebrand
    Legend
    May 4, 2010

    Walt,

    I think you found the source of the problem. It seems to me you have to start the product at least once with Administrator privileges. Or make sure that the Registry entries are set.

    The workspace settings as well as all other user settings are stored in the %appdata%\Adobe\FrameMaker\9\ folder.

    - Michael

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices