Ticket #2115 (closed bug)
When rotated text frame is autochained it preserves its rotation angle but not its position.
Reported by: | todor | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | M12_RELEASE |
Component: | uncategorized | Version: | 2.0 |
Keywords: | Cc: | ||
Category: | unknown | Effort: | |
Importance: | Ticket_group: | ||
Estimated Number of Hours: | 0 | Add Hours to Ticket: | 0 |
Billable?: | yes | Total Hours: | 0 |
Analysis_owners: | todor | Design_owners: | boyan |
Imp._owners: | boyan | Test_owners: | |
Analysis_reviewers: | Changelog: | ||
Design_reviewers: | pap | Imp._reviewers: | pap |
Test_reviewers: | Analysis_score: | 0 | |
Design_score: | 3 | Imp._score: | 3.5 |
Test_score: | 0 |
Description
- Insert text frame.
- Fill it with text.
- Rotate the frame and move it.
- Choose autochain option.
As a result the new created frame is with default size and position (75, 75), but the rotation is preserved.
Attachments
Change History
comment:2 Changed 16 years ago by boyan
- Design_owners set to boyan
- Status changed from s1b_analysis_finished to s2a_design_started
- Imp._owners set to boyan
starting design
comment:3 Changed 16 years ago by boyan
- Status changed from s2a_design_started to s3b_implementation_finished
Actually, the issue is the following: size and location are not templated with auto-chaining.
However, they are templated when applying a frame template from the library.
The solution of this bug is to reuse the code from the LibraryTabLogic in order to apply frame templates. This exposes a static method in the Logic as public but code duplication is avoided. The attached patch contains the solution.
comment:4 Changed 16 years ago by pap
- Status changed from s3b_implementation_finished to s3c_implementation_ok
- Design_score changed from 0 to 3
- Design_reviewers set to pap
- Imp._score changed from 0 to 3.5
- Imp._reviewers set to pap
- The fix is OK although the template applying logic should be put at some more centralized place
- Commited to trunk in [7645].
Note: See
TracTickets for help on using
tickets.