Skip to main content
Known Participant
January 23, 2015
Question

"Next" Para. Tag Affects Previous Paragraphs

  • January 23, 2015
  • 3 replies
  • 453 views

Inserting new paragraph by placing the cursor at the beginning of a paragraph is reading the Next Pgf Tag setting and changing the existing paragraph's style. For example, consider that you have a Heading 1 and want to insert another Heading 1 above it. You used to be able to simply place the cursor at the beginning of the existing H1 and press Enter. Voila - two H1 paragraphs.

Now when you do this, the existing H1 becomes Body style, because Body is the Next Pgf Style setting for H1. The same is true for any paragraph tag with a different Next Pgf setting. 

This is a change since FM8 (we just upgraded to FM12 last year), and I suppose Adobe thinks they made the setting smarter, but we find this behavior not at all useful.

If there is a workaround to this (other than the obvious), we'd sure like to hear it. It's a small thing, but irritating. (And if no solutions, yes we will report this in the Bugs/Features area.)

Thanks!

This topic has been closed for replies.

3 replies

Gloria_McAuthor
Known Participant
February 11, 2015

Glad that my post helped you, A-Bel. I did enter a bug report on this issue. If you would like to see the behavior changed, vote on the bug:

Bug#3912641 - "Next Pgf Tag" behavior when entering new line at the beginning of a paragraph

Inspiring
February 11, 2015

Hi Gloria,

Thank you for your problem analysis. I had this problem, but did not understand the correlation.

Knowing this we are discussing to change the templates: delete the Next-paragraph-options and

working more with well prepared text modules (-> Autotext).

Legend
January 26, 2015

Glad to see someone else posting about this! it's decidedly irritating.

Inspiring
January 26, 2015

I don't like the change, either, but learned to work around it by

hitting the left arrow to move to the end of the previous paragraph

before hitting return to enter a new paragraph.

We probably should report this as a bug.