Task Savvy Release Notes
October 6, 2002
Description:
List of known problems in prior and current versions of Task Savvy.
Notes:
This file serves both as an example of using Task Savvy for problem reports, and to document the status of specific problems with Task Savvy itself.

Summary:

Task

Who

Status
Double Quote corrupts file Ric Open Issue
Report name after SaveAs Ric Open Issue
Report/Statement Type Ric Open Issue
Report/Statement Format Ric Added in v1.1
Auto Backup Ric Added in v1.1
Formatted Text Reports Ric Added in v1.1
Tasks added out of order Ric Fixed in v1.1
Changes lost or misapplied Ric Fixed in v1.1
Task list update on task apply Ric Closed, NTF
Parenthesis Corrupts File Ric Fixed in v1.0
Lost Docs Ric Fixed in v1.0
Logged time doesn't update Ric Fixed in v1.0

Details:


Double Quote corrupts file, Ric
Open Issue
Using a double quote character in a task description or log entry makes the *.ts file unreadable. There is no sign of trouble until the file is read.

When a file containing a double quote character in a task description or log entry is read, an error is presented in a message box, and the project is truncated. To prevent loss of data, the user must close the file without saving it, and then manually remove the double quote character from the *.ts file.

The work around is to refrain from using double quote character in a task description of log entry.
Date Log Entry
2002.09.14 Problem discovered.

Report name after SaveAs, Ric
Open Issue
After writing a report or statement file, then using File/SaveAs to change the project's file name, the report or statement file name (which is usually based on the project file name) is not changed.

This had been fixed in v1.1, but was reintroduced in v1.2. Work around is to make sure to use the Project menu Report or Statement dialog box to change the report or statement name after File/SaveAs is used to change the project file name.
Date Log Entry
2002.02.03 Changed File/SaveAs to clear the report file name, thereby causing it to be reconstructed next time a report is emitted.
2002.09.14 This had been fixed in v1.1, but was reintroduced in v1.2.

Report/Statement Type, Ric
Open Issue
The [Browse] button in the Report and Statement Profile dialog box should strip off the file extension so the file type (HTML vs. text), which is keyed on the file extension, can be changed more easily. Work around is to delete the file extension manually when changing file types.

This had been fixed in v1.1, but was reintroduced in v1.2.
Date Log Entry
2002.09.14 This had been fixed in v1.1, but was reintroduced in v1.2.

Report/Statement Format, Ric
Added in v1.1
  1. Strip off file extension from [Browse] box of reports and statements so file type (which is keyed on the file extension) switches more smoothly.
  2. Maintain different report and statement properties per project file.
  3. Add a record in the project file for remembering the settings between sessions.
Date Log Entry
2002.02.09 Added code to strip off file extension when browsing for new report or statement file (so Filter string will control file type). Dropped support for .htm and forced .html for all HTML files (because Windows(tm) made it too difficult to support both).

Fixed a bug when writing certain statements if there was a task with no description.
2002.02.23 Moved the report and statement format data structure into the project class, so each project can have its own report properties.

Changed the prefix for report and statement file names from ts-pr_ and ts-ps_, to tsr_ and tss_, respectively.
2002.02.24 More testing and debugging.
2002.04.27 Added code to save report settings in the *.ts file and restore them when reopened.
2002.04.28 Finished ReportFormat field of *.ts file writer and reader. Changed Project/Refresh menu item to show the file name rather than the title.

Auto Backup, Ric
Added in v1.1
Automatically back up periodically to avoid losing work in unlikely event of a crash.
Date Log Entry
2002.02.04 Write Project method for saving the backup file. Split file save method so actual file emitter can use project file stream or backup file stream.
2002.02.06 Call auto backup function right before doing any [Add] or [Apply], in case things go awry.
2002.02.09 Added "Task Savvy Backups" (*.bak) to the file open file types list.
2002.02.23 Added code to remove the auto backup file when the original file is closed, or SavedAs. Found and fixed some [Add] and [Apply] changes that were not setting the modified flag.
2002.02.24 Found and fixed some cases which failed to save the backup file.

Formatted Text Reports, Ric
Added in v1.1
Add support for emitting the various paragraph formats (lists, bullets, prose) when writing report and statement files in text format.
Date Log Entry
2002.02.09 Added a new function to emit paragraphs according to the selected format (list, bullets, prose), and a utility function to create a roman numeral string. Modified the text report file generators to use these instead of just dumping the string into the text file.

Tasks added out of order, Ric
Fixed in v1.1
Adding a task after using the Task pane's [New] button, as opposed to editing an existing task, adds the task in the wrong place. It appears to be in the right position in the task list tree-view display, but is actually prepended ahead of the first task in the underlying data base.
Date Log Entry
2001.02.04 Tried several times to reproduce this, with no success. Then when I tried to enter this problem report in the release notes project, it did occur, so I could track it down to a problem with the [New] button.
2002.02.03 Restored commented out code in TaskSavvyWin::vAddTask() that retrieved the selected task from the task list, instead of simply using the locally remembered task select. Reason is that the local task select was set to NULL to prevent the [Apply] button from being enabled when adding a task; that's why the new task got added to the top of the list.

Changes lost or misapplied, Ric
Fixed in v1.1
If a second project is opened while there are unapplied changes in the current project, Task Savvy will ask whether to apply the changes after switching to the new project. If the new project has a task with the same name and who field, then the changes are applied to the new task instead of the original task. If there is no such task in the new project, then the changes are lost.

While investigating this, it came to light that File/New, File/Open, and File/Close were all similarly afflicted.
Date Log Entry
2002.02.03 Added code to check for this case and warn the user before proceeding in each of File/New, File/Open, and File/Close. User may choose to abandon changes and move on, or stay put with changes intact.

Task list update on task apply, Ric
Closed, NTF
If the task name or who field is changed and applied, the task list tree-view is not updated.

Unable to reproduce.

Parenthesis Corrupts File, Ric
Fixed in v1.0
Using parenthesis in the task name, who, or status causes a file corruption.
Date Log Entry
2000.11.18 Added code to skip through quoted text when parsing object parameter strings from the project file, so delimiters embedded within strings are ignored.

Lost Docs, Ric
Fixed in v1.0
If a project file name (or anything beyond the program name itself) is included on the command line of the Task Savvy shortcut, then the Help menu can't find the help pages.
Date Log Entry
2000.09.28 Changed help file path code to use the Windows _pgmptr variable to obtain the path to the Task Savvy executable (and hence help files).

Logged time doesn't update, Ric
Fixed in v1.0
The "logged time" field of the "task" pane does not update itself when adding new log entries. It will update if you switch to a different task and back.
Date Log Entry
2000.11.10 Now refreshes the Task Tab after adding a log entry, so the logged time is updated.

Task Savvy project file: C:\RIC\TaskSavvy\doc\TaskSavvyRelNotes.ts