wiki:TEXT_PARAGRAPH_NEXT_STYLE_R0
Last modified 14 years ago Last modified on 02/06/09 16:23:17

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=TEXT_PARAGRAPH_NEXT_STYLE_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed
current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

When the user define a custom style for a paragraph and then creates second one, the style of the second paragraph should be default. This functionality should present in all cases when the user could edit text(text frame, detached text frame editor etc.). However if they are custom defined character appearance they shouldn't change(same rule is applied for links).

Task requirements

  • Provide functionality that automatically applies default paragraph style to newly created paragraphs.

Task result

  • The result should be code.

Implementation idea

TEXT_PARAGPRAPH_FORMAT_COMMONS_R0
TEXT_PARAGRAPH_ALIGN_R0
TEXT_PARAGRAPH_SPACING_R0
TEXT_PARAGRAPH_CHAR_STYLE_R0
TEXT_PARAGRAPH_NEXT_STYLE_R0

DETACHED_TEXT_FRAME_EDITOR_R0

How to demo

  • Run the application
  • Create a new book and place text frame inside
  • Populate some lorem ipsum text inside with a number of paragraphs(lorem ipsum generator --> http://www.lipsum.com/)
  • Define custom paragraph style including characters appearance in the paragraph(change the color for example).
  • Set focus in the middle of the paragraph. Press enter. This way you'll create separated paragraph.
  • The new paragraph should have default paragraph style applied(color should change).

Design

(Describe your design here.)

Implementation

(Describe and link the implementation results here (from the wiki or the repository).)

Testing

(Place the testing results here.)

Comments

(Write comments for this or later revisions here.)