Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=DOCUMENT_FILE_MANAGEMENT_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

file menu entries... recent books. new, open, save, save as, close - these should be handled by appropriate extension points Create structure of the file menu. Define document behavior. File menu should contain:

• New
• Open
• Recent Documents
• Save
• Save As
• Close

Task requirements

The behavior is the following:

• File -> New Toggles a hud that gives the opportunity to enter size of the new book and/or to choose a template to use for creating the new book.
  • When a template is selected, the size controls become inactive
  • Default values are chosen when the dialog is opened.
  • This dialog should also be accessible by keyboard shortcut. (Not part of this task)
• File -> Open toggles File Dialog to choose a book file to be opened.
• File -> Recent Documents opens a submenu with list of recently opened books.
  • The list should be with maximum 10 items.
  • The list should be with most recent book documents at the top of the menu. (Sorting)
• File -> Save - saves the book.
  • If the book hasn't been saved yet, works like File -> Save as.
• File -> Save As - Toggles Save as File Dialog to choose a location to save the book.
• File -> Close Toggles the "Save changes" and/or "Quit Sophie 2" message boxes.
  • If there are no opened and modified books File -> Close toggles the "Quit Sophie2?" message box.
  • If there are opened and modified books File -> Close toggles the "Save changes?" message box starting from last modified book.
• In later revisions File -> Import/Export should be present with similar behavior.(with submenus, should toggle file dialogs.)

Task result

Source code. Diagrams.

Implementation idea

Related

^{(Here you can add related tasks that could be useful or helpful.)}

How to demo

^{(In this section you must add instructions for the demo of the task.)}

Design

Implementation

^{(Implementation results should be described and linked here (from the wiki or the repository))}

Testing

Comments

Underlining letters for keyboard shortcuts should be present, but as part of which task?