Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Tab positions in Header/Footer are not recalculated when changing margins size | ||
---|---|---|---|
Product: | Writer | Reporter: | issues@www <issues> |
Component: | code | Assignee: | jp <juergen_pingel> |
Status: | CLOSED NOT_AN_OOO_ISSUE | QA Contact: | issues@www <issues> |
Severity: | Trivial | ||
Priority: | P2 | CC: | issues |
Version: | 613 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
issues@www
2001-01-02 10:06:33 UTC
I think here you are wrong. TabStops have a position measure from the left margin. Then each TabStop has an alignment which describe how the text of this TabStop has to format. This aligment don't mean that the TabStop themself is formatted inside the margins! Hm, have you tried to reproduce what I've described? Don't you see a bug or very horrible flaw in how it works? After margins are decreased, the right edge of the text in the rightmost TabStop is not aligned with the text right margin no more! Same for center TabStop - it becomes not in the center! May be that's the way it should programmed for (I don't think so), but it's very counterintuitive and broken! Imagine a situation - I want page numbers in the header, in the rightmost position. I place a field there (and it looks OK - page number aligns right with right edge of the text). Then I suddenly decide to reduce margins, I do this and get page number not aligned at the right edge of the text, but somewhere to the left of it! Yes I've reproduce your problem and I unstand it. What you want to have is a new Type of TabStop. A TabStop that is not positioned from the left side of the text. You will have a "stable" position right or centered. This we can add in the feature (not in the near). But you misunderstood me: our current implemtation works how I describe it before. So you haven't currently the functionality you wish for. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. |