View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0011874 | Scribus | Tables | public | 2013-12-06 14:52 | 2014-04-06 18:29 |
Reporter | FirasH | Assigned To | jghali | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.5.0svn | ||||
Target Version | 1.5.0 | Fixed in Version | 1.5.0svn | ||
Summary | 0011874: First Line Offset in Tables is not saved and radio buttons are not selectable | ||||
Description | Properties > Text > First Line Offset does not work as supposed for Table cells. Changes are not saved, even if applied until closing and reopening the document. The black circle of the radio buttons under First Line Offset is always on "Maximum Ascent" | ||||
Steps To Reproduce | 1) Create a new document with a Table (number of Rows/Columns is not important) 2) Write some text in one of the cells (all of them have this issue) 3) Go to Properties > Text > First Line Offset 4) Try selecting "Font Ascent", "Line Spacing" or "Baseline Grid" The Offset is applied to the First Line, but the "Maximum Ascent" radio button is always selected. 5) Save the document an reopen it After reopening the document the First Line Offset returns to "Maximum Ascent" | ||||
Additional Information | Scribus SVN 18624 | ||||
Tags | No tags attached. | ||||
Patch | |||||
|
Now with Scribus 1.5.0 SVN (18828) and Qt 5.2.1 the issue with the radio button seems resolved. The only problem still there is that the entry selected under "First Line Offset" is not saved and consequently not restored as expected after re-opening the document. |
|
Reproducible on OSX 10.8.5 Qt version 5.2.1. Scribus Version 1.5.0.svn 12 February 2014 Build ID: C-C-T-F-C1.12.16-Mac/-64bit Using Ghostscript version 9.07 |
|
Fixed. A warning tho : to fix this issue (+ a few similar ones) a file format change was required. I'll keep the old table reading code as is for 1-2 weeks in order to allow old 1.5.0svn document to be converted. I'll do a cleanup afterwards: as with every development version, we reserve us a right to do breaking changes when required. |
|
FirasH, can you please re-test? |
|
Re-tested, cannot reproduce the issue. |
Date Modified | Username | Field | Change |
---|---|---|---|
2013-12-06 14:52 | FirasH | New Issue | |
2013-12-08 22:46 | jghali | Target Version | => 1.5.0 |
2014-02-21 13:27 | FirasH | Note Added: 0031355 | |
2014-02-21 20:55 | Kunda | Note Added: 0031359 | |
2014-02-25 21:14 | jghali | Note Added: 0031399 | |
2014-02-25 21:14 | jghali | Status | new => resolved |
2014-02-25 21:14 | jghali | Fixed in Version | => 1.5.0svn |
2014-02-25 21:14 | jghali | Resolution | open => fixed |
2014-02-25 21:14 | jghali | Assigned To | => jghali |
2014-04-05 14:39 | christoph_s | Note Added: 0031623 | |
2014-04-06 10:56 | FirasH | Note Added: 0031633 | |
2014-04-06 18:29 | christoph_s | Status | resolved => closed |