MySQL Bugs: #53042: No indication of unsaved changes

Bug #53042	No indication of unsaved changes
Submitted:	21 Apr 2010 23:21	Modified:	11 May 2010 14:49
Reporter:	Chris Nanney	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2.17, 5.2.19	OS:	Windows (XP SP3)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	regression

Description:
When working in the data modeler, there is no indication that there are unsaved changes to the file. In previous versions (5.1) the filename had an asterisk in the title bar when there were changes to save.

Current versions (5.2) don't have any indication that the open model has unsaved changes.

How to repeat:
Open a model, make some changes to the schema.

Suggested fix:
Add some visual indication to the "EER Diagram" and maybe parent "MySQL Model (filename.mwb)" tab that lets you know there are unsaved changes. Maybe add an asterisk, or make the tab text bold?

Thank you for the problem report. Verified just as described with 5.2.19.

Fixed in repository.

Fixed in repository (only the model file itself is marked dirty, not the diagram pages anymore).

fix confirmed in repository

A 'change' entry has been added to the 5.2.22 changelog:

MySQL Workbench has been changed so that only the Model Overview tab indicates that changes need to be saved, using an asterisk, rather than this being reflected on individual EER Diagrams.