Bug #20644 | unable to save relationship label floater custom positions | ||
---|---|---|---|
Submitted: | 23 Jun 2006 1:33 | Modified: | 5 Jul 2006 15:46 |
Reporter: | Geoffrey Hoffman | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Workbench Preview | Severity: | S4 (Feature request) |
Version: | 1.0.6. Beta | OS: | Windows (Windows XP) |
Assigned to: | CPU Architecture: | Any |
[23 Jun 2006 1:33]
Geoffrey Hoffman
[28 Jun 2006 12:15]
Tonci Grgin
Hi Geoffrey and thanks for your problem report. The behavior I see is that when you click "Export" all collapsed nodes of tables you made modifications in appearance get expanded causing labels to "jump around". However I can't verify that file has been saved with new positions: C:\tmp>fc test.mwb CONTROLTEST.MWB Comparing files test.mwb and CONTROLTEST.MWB FC: no differences encountered
[28 Jun 2006 13:04]
Geoffrey Hoffman
On further investigation it appears that while it is possible to reposition the relationship floaters, their positions are not saved, and revert to default positions upon closing and opening the file. Exporting Create SQL merely reverts the mwd to its saved state with default positions for relationship label floaters. Bug should be reclassified as 'unable to save relationship label floater custom positions'.
[5 Jul 2006 6:21]
Tonci Grgin
Geoffrey, I agree with you. Changing synopsis and severity since it's feature request actually.
[5 Jul 2006 15:46]
Geoffrey Hoffman
If you create a relationship, the label floater appears in the "program generated default location". If you reposition the relationship label floaters, the offsets are not saved with the document. Exporting Create Table SQL causes the saved state to reload, which, in turn causes any repositioned relationship label floaters to appear to jump back to their stored/default state.