To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=113976
User aw changed the following:
What |Old value |New value
================================================================================
Assigned to|aw |wg
--------------------------------------------------------------------------------
------- Additional comments from a...@openoffice.org Mon Sep 6 10:08:32 +0000
2010 -------
AW: I do not agree here. I understand what the user intuitively expects, but
when thinking about what happens here, it is no longer intuitive.
A shape filled with a bitmap (bitmap picture) means that the bitmap is scaled so
that it is completely filling the shape. When intersecting with another shape, a
new shape (normally a polygon shape) filled with that bitmap is created. The
dimensions of that shapes of course get changed by intersecting since it is a
geometrical operation. The bitmap again gets scaled to fill the new object.
Intersection of objects is a geometrical operation which change the shape
outline, not a replacement for picture cropping. It is not a replacement for a
pixel-oriented paint program to manipulate the image.
To change this would mean to need a new mechanism to add bitmap filling to
objects with an additional offset and scaling. This would need UI, FileFormat
and API support.
When supporting this, it may happen that the bitmap is completely outside the
shape. There will be no hint that this shape is bitmap-filled. This normally
leads to 'why is my file sooo big'-tasks later.
Another problem: What should be shown in regions which are NOT covered by the
new shape? The group of geometry manipulating functions (including
Intersections, but also merges) may also create regions 'outside' the expected
shape. How to solve that? What would be 'intuitive' there?
Another group of errors would come in after supporting this which would explain
that this is not what they intuitively expect to happen, the group of people who
see this operations as what they are.
In short: It's NOT a bitmap manipulating function set, the expectation is not
correct.
AW->WG: This is in no case a defect, but defined behaviour. As an enhancement it
would lead to problems. I suggest to not accept this task.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@graphics.openoffice.org
For additional commands, e-mail: issues-h...@graphics.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
