Bug 234540 - embed an oo.o-draw (v2.0) object in an impress (v1.0) presentation = chaos
embed an oo.o-draw (v2.0) object in an impress (v1.0) presentation = chaos
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Caolan McNamara
Depends On:
  Show dependency treegraph
Reported: 2007-03-29 17:27 EDT by Ben Levenson
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-30 04:49:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
OpenOffice.org 75905 None None None Never

  None (edit)
Description Ben Levenson 2007-03-29 17:27:55 EDT
Description of problem:
oo.o v2.0 doesn't behave as expected when editing a v1.0 document.

Steps to Reproduce:
1. open an oo.o 1.0 presentation with oo.o 2.0
2. create a new slide with an object
3. double click to add the object and create an openoffice.org 2.0 drawing
4. use the flowchart images, connectors to create a diagram
5. label the flowchart shapes with some text
6. save the presentation and close it
7. reopen the presentation

Actual results:
flowchart images appear to be OK, but all of the connectors and text are

Expected results:
no chaos

Additional info:
Everything works as expected if you open the v1.0 presentation and
save it as an odp document *before* you add the drawings.

I think this is a problem with embedding a v2.0 drawing in a v1.0 presentation.
When you "double click to add an object" you are only presented with 2.0
options, even though you are editing an v1.0 presentation.
Comment 1 Caolan McNamara 2007-03-30 04:49:57 EDT
reproducable, still affects the current 2.2.0 release of OOo as well. Moving
upstream to get input from the draw/impress developers.

Note You need to log in before you can comment on or make changes to this bug.