Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Unexpected behaviour with Shapes → Intersect | ||||||
---|---|---|---|---|---|---|---|
Product: | Draw | Reporter: | rgb <rgb.mldc> | ||||
Component: | editing | Assignee: | AOO issues mailing list <issues> | ||||
Status: | CONFIRMED --- | QA Contact: | |||||
Severity: | Major | ||||||
Priority: | P4 | CC: | Armin.Le.Grand, hrustall, issues, oooforum | ||||
Version: | OOo 3.3 | ||||||
Target Milestone: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Issue Type: | FEATURE | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
rgb
2011-11-25 22:18:05 UTC
ALG: Intersection is a geometrical operation on two polygon shapes, so the bitmap you try to work with gets converted to a polygon object (context menu, convert to contour). These two polygon shapes then get intersected, leading to the ellipse result. The intersection always uses the fill/line style of the deepest object, in this case the converted polygon with fill style bitmap. Thus, the result gets the line/fill style copied from that, so the result ellipse will just get the fill style of the deepest object. This is designed to work with any fill style, e.g. color and/or others. This function is not intended to cut portions out of a bitmap, though. It works as intended, but you make a nice suggestion how this feature could be extended. It would be necessary to cut bitmap contents to the result geometry. A big caveat is that the result geometry could not only be smaller and inside the source image (which will make clipping simple and logic), but also be much bigger and empty (shapes merge). How should the bitmap meeded as a result be extended? I suggest to make this task a feature request. *** Issue 128061 has been marked as a duplicate of this issue. *** (In reply to Armin Le Grand from comment #1) > I suggest to make this task a feature request. Done |