- Status Closed
- Percent Complete
- Task Type Bug Report
- Category QCAD (main)
-
Assigned To
andrew - Operating System Ubuntu Linux
- Severity Low
- Priority Very Low
- Reported Version 3.4.2
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Opened by sverholen - 17.11.2013
Last edited by andrew - 03.12.2013
FS#971 - Dimension properties: text position not saved
When reopening a dxf that had the dimension text aligned differently than the default, the text position has the same X position for vertical dimensions and the same Y position for horizontal dimensions as the dimension line. In other words, changes to the text position are not saved or loaded when reopening a file.
For example:
1) Create the drawing and take a dimension measurement
Dimension Line on (X, Y): (110, 1680)
Text Position changed to (X, Y): (100, 1255)
2) Save file, close it and reopen it
Dimension Line on (X, Y): (110, 1680)
Text Position on (X, Y): (110, 1255)
The text height (in drawing preferences) is set to 15 and page printing scale is 1:5 (if it matters).
QCAD Professional 3.4.2.0 on Ubuntu 13.04. See the attached file for the program specs.
Not really a major bug, but quite irritating none the less. :)
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
Hi,
could this be a workaround for you? Yes - it isn't a solution but a workaround ....
http://www.qcad.org/rsforum/viewtopic.php?f=33&t=2529&p=8362&hilit=Dimension#p8362
Hello Husky,
Well I can certainly live with that workaround :)
Thank you very much.
For the audience: the gist of the workaround is:
1) select all dimensions
2) enter the command: dimregen
Thanks again, Husky !
To the developers: this problem doesn't occur straight away. My dimensions are in a separate layer. Instinctively, I think the problem started after I added another layer after the dimensions layer.
I'll test it out in the next couple of days and report here.