Skip to main content
T
TTVB544
Participating Frequently
December 10, 2012
Question

Has anyone experienced an unintended "find/replace all" in a document (using FM11) ?

  • December 10, 2012
  • 1 reply
  • 641 views

Hi All,

Using FM11 with Windows7.

We have a problem with the following:

If I have completed a Find/Change All in Document A (then close the Find window), then I open Document B and press Control-F to perform a new search, once I start typing the previous word search/change all is applied to Document B when it's not the intention.

The problem is when Control-F is pressed the last function is highlighted (in this case "Change All") - rather than the word field, so nothing is actually being typed in this field - rather it performs the last function.  The basic work-around is just to make sure we click or tab to the desired field before typing...  OR make sure to delete the previous find/change text fields before closing the window.  When doing things quickly though we may forget - so it gets annoying when we have to fix this or revert to last saved document.

Users with XP don't experience this. Each time control-F is pressed, the Find term field is the highlight so the new term is typed in as expected.

Any tips would be welcome. 

Thank you,

Tina

    This topic has been closed for replies.

    1 reply

    Arnis Gubins
    Arnis Gubins
    Inspiring
    December 11, 2012

    Tina,

    There's been a change in behaviour with FM11's Find/Change (as you've noticed). The dialog now retains focus after a search has been performed and is modal. However, the focus of the field for ctrl-F should place it in the Text area, regardless of platform, not execute the last operation. This is buggy behaviour and I just confirmed this on my platform (regardless of whether your in Doc A or B).

    Please file a bug report at the FrameMaker Bugs & Wish List  (https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&product=63)

    T
    TTVB544Author
    Participating Frequently
    December 12, 2012

    Thank you Arnis !

    That's right, once we all tried to reproduce the problem - we realized we could be in the same document when this 'bug' happened.

    We are aware of it now, so we'll take the necessary actions to prevent it.

    Tina

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