Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323860 - [Form Editor] In some cases Tigerstripe files cannot be saved
Summary: [Form Editor] In some cases Tigerstripe files cannot be saved
Status: RESOLVED FIXED
Alias: None
Product: Tigerstripe
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 major (vote)
Target Milestone: 0.5M0   Edit
Assignee: Navid Mehregani CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-27 14:20 EDT by Navid Mehregani CLA
Modified: 2010-10-07 13:07 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Navid Mehregani CLA 2010-08-27 14:20:12 EDT 
Build Identifier: 

I finally managed to consistently reproduce this defect :-) 

In some cases Tigerstripe files cannot be saved.  I debugged this down to the algorithm that marks a file as dirty.  There seems to be flaws in the algorithm, which fails to mark a file as dirty when it really should be marked as such.  Note that there are different ways of reproducing this defect.  The steps below is only one scenario.

Reproducible: Always

Steps to Reproduce:
1. Open a project descriptor file
2. Specify a description in the file
3. Save the file
4. Click on Edit > Undo
5. Notice that you can't save the file even though an asterisk in the title bar indicates that the file is dirty.
Comment 1 Navid Mehregani CLA 2010-08-27 14:22:01 EDT 
File to look at: AbstractTigerstripeProject.isDirty() and BaseContainerOBject.isContainedDirty()
Comment 2 Navid Mehregani CLA 2010-10-07 13:07:00 EDT 
This issue should now be fixed.

Files modified:
GeneratorDescriptorEditor
DescriptorEditor