Ooo Draw: changes applied to all objects

Asked by manolo

Hi to all.

I am new to Draw from OpenOffice.org suite. I created a rectangle and then I copied it several times since I need to draw various rectangles. Then I select JUST ONE OF THEM, right click on it and cliccked on

Edit Style -> Line

and selected the "fine dashed" line instead of the previous "Continous". I expected only the selected item to be dashed, not all the objects in the page. It happens the same when I create new objects: they are created with dashed lines and when I try to change the line of the new object, again it changes the lines to all the objects and not only to the new one.

is it a bug?

Thanks.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu openoffice.org Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

I'd say so. What version are you on?

Revision history for this message
manolo (mac-man2005) said :
#2

Sorry, my version is OpenOffice.org 3.2.0 Build 9483

(Please see the screenshot)

http://img248.imageshack.us/img248/1203/screenshotaboutopenoffi.png

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

Can you give the output of:

lsb_release -a

Thanks

Revision history for this message
manolo (mac-man2005) said :
#4

lsb_release -a
LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:qt4-3.1-amd64:qt4-3.1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 10.04 LTS
Release: 10.04
Codename: lucid

uname -a
Linux mano-laptop 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 19:31:57 UTC 2010 x86_64 GNU/Linux

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#5

I'd log a bug. Maybe the copying links them somehow. I don't use the app personally.

Revision history for this message
manolo (mac-man2005) said :
#6

ok, how shoud I follow the bug?

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#7

ubuntu-bug oodraw

Should do it, if you run alacarte, you can see the exact command and you can log a bug against that app.

Revision history for this message
manolo (mac-man2005) said :
#8

running ubuntu-bug oodraw produces this error message "Package oodraw does not exist"

running alacarte I can see that Draw is launced by the ooffice -draw %F command, so running ubuntu-bug ooffice -draw %F produces this message in terminal:

Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash file]

On the other hang, running the command using quotes ubuntu-bug "ooffice -draw %F" I get "Package oodraw -draw %F does not exist".

Similar error launching ubuntu-bug with ooffice -draw
- without %F
- with or without quotes
- without %F and without -draw

Of course, running ooffice from terminal it opens the quick start page of openoffice, while running "ooffice -draw" directly opens the Draw application.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#9

then use:

ubuntu-bug openoffice.org

Revision history for this message
manolo (mac-man2005) said :
#10

This is the bug report:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/604482

Just for curiosity, are the infos collected by Apport stored somewhere? I cannot see them in that bug report.

Revision history for this message
Tony Pursell (ajpursell) said :
#11

If you right click and do Edit Style... you are editing the Style of the graphic object. Probably this is the Default Style. Copied objects all have the same Style as the object they are copied from, so when you change the Line properties of the Style, the border of all the objects is changed because they all have the same Style.

To change the Line properties of just a single object, either

1) Go Format > Line and make your change

2) Create a whole new Style with the different Line properties and assign this to the object. Do this by selecting Format > Styles & Formatting. Right click an existing Style (Default, perhaps) and select New. Give the new Style a Name. Change its Line properties and click OK. Now highlight the object and double click this new Style to assign it to the highlighted object.

It's up to you which method you use. Using styles can be very useful. If you have 50 objects with the same Line properties that you want to all change, then you can do it once with Edit Style... rather that 50 times with Format > Line.

Hope this helps.

Tony

PS If this answers your question, please mark it as Solved (and mark you Bug as Invalid)

Revision history for this message
manolo (mac-man2005) said :
#12

Tony, thanks for your reply.

Unfortunately, I am not sure it is not a bug. As I said, the misleading behavior happens also when adding a brand new object from the Drawing Bar (that is not copying/pasting it). In fact, even in this case, changing the stile to the brand new object changes the stile to all of the objects.

However, I have been trying to change the line as you said in 1) and it works.

So, I think there are two possibilities:
1) the EDIT STYLE changes the default style to all of the objects in the current page. To change the properties to just one object, right click on it and chose Line, Area, Text, Position & Size. In this case, it could be useful to change the "Edit Style" option in "Edit default style"
2) There is a bug.

Can you help with this problem?

Provide an answer of your own, or ask manolo for more information if necessary.

To post a message you must log in.