To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=44438
User dvo changed the following:
What |Old value |New value
================================================================================
Status|NEW |STARTED
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Wed Mar 9 10:34:11 -0800
2005 -------
dvo: Ouch! This problem is not nearly as benign as it looks. This is one of our
popular 'concept problems', which means fixing this will require significant
changes to the code. Which means it is risky. Which means I am very hesitant to
fix this for the upcoming release. However, I will investigate some more before
pleading to re-target this issue.
The actual problem is this: <Ctrl-A> select from the first character to the
last. The graphics is anchored to the paragraph. (NOT the characters.) When
deleting paragraphs with flys (images, frames, etc.) anchored to them, the flys
will only be deleted if the COMPLETE paragraph is deleted. If anything of the
paragraph remains, the graphic will remain. In this case, the first and last
paragraph remain and are merged together. Since, essentially, parts of both
paragraphs survive, so will the paragraph-bound flys anchored to them.
This behaviour was explicitly decided upon in the turn of fixing another issue
(that I cannot find currently). The problem THERE was that people were very
surprised by their graphics suddenly vanishing during delete operations, even
though the paragraphs in questions remained at least partially intact. Now,
THERE the current behaviour makes sense. But in THIS issue, in the Ctrl-A case,
it clearly doesn't.
At the time, one argument was that there is a trivial work-around, in that if
people really want the graphics to be deleted as well, it's just another
<click>+<del>. This applies to the <Ctrl-A> case as well. The other solution
would have graphics unexpectedly disappearing, which is a much graver problem.
I will fix this, IF I can find a fix that I am sure will not break stuff
elsewhere. Given what I said above, that is not terribly likely. Also, I am not
terribly inclined to introduce a quick-hack for exactly this situation. If I
can't fix this now, this should be fixed for the next version, which gives us
more time. I would really prefer if we would fix this together with the more
thorough rework that we are planning on the Writer enginge for the upcoming
version. That would allow a much cleaner solution.
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
