Issue 6358 - objects should be inserted as anchored on page standardly
Summary: objects should be inserted as anchored on page standardly
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 1.1 RC3
Hardware: All All
: P4 Trivial with 6 votes (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
: 6740 (view as issue list)
Depends on:
Blocks:
 
Reported: 2002-07-08 19:36 UTC by lars
Modified: 2013-02-07 22:13 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description lars 2002-07-08 19:36:07 UTC
I have thought about this:

Until now, I always changed from anchored on cell to anchored on page, because 
column & row size changes, change the size of the object (or more specifically 
an inserted bitmpap) too.

That's sth. I don't want. It should be inserted at the current cell position 
though.

Or if there is more to being anchored on cell than what I wrote, only consider 
to have r&c size changes not influence object sizes.
Comment 1 frank 2002-07-09 09:18:58 UTC
Hi Falko

1 4 u

Frank
Comment 2 lars 2002-08-17 18:27:24 UTC
this can be very annoying if it there are only small size changes one 
doesn't see when working with the doc but one sees them after 
printing for example.


or how about an OOo option?!?
Comment 3 lars 2003-09-05 00:55:53 UTC
*** Issue 6740 has been marked as a duplicate of this issue. ***
Comment 4 lars 2003-09-05 01:00:20 UTC
this one is valid for any OOo app and until issue 7085 isn't 
resolved, this one is P2

There should at least be an option to change the default behaviour; 
and when the user first changes the anchor type, inform him about the 
possibility to choose the default using the method described in issue 
7185 or perhaps just remember the last/most often used anchor type?
Comment 5 lars 2003-09-05 01:01:58 UTC
oh, there's no harsh, angry, sarcastic undertone in these comments; 
they just occurred to me. [now, how can i make you believe me?]
Comment 6 rblackeagle 2003-09-05 06:16:51 UTC
I've got the same problem.  It seems developers are not interested in
solving the "jumping graphics" problem that has been reported for two
years now.  I've still got the problem.  It's far less common with
page anchors than other kinds of anchors.  I also note that "anchor as
character" does nothing of the sort as the images sometimes jump pages
ontop of one another even though they're supposed to retain their
position as solidly as a character does.

I understand the the positioning issue is not easy to resolve, but I
would have thought someone might be at least interested in looking at
it.  I have a list of problems developers don't want to look at
(despite their having been reported for years):

3317
3962
9845
10049
10357
10634

The first two deal with wrapping issues.  3317 and the remainder deal
with graphics not holding position.  I guess I'll just keep filing new
issues every time a graphic jumps.  Maybe the sheer number of filed
issues will get someone's attention.
Comment 8 falko.tesch 2003-09-11 14:37:08 UTC
First of all:
This not a P2.
Second:
Currently we evaluating the default anchoring to match MS word's way
of anchoring. since this is part of our interoperability issues we
address in 2.0 I will 
Comment 9 falko.tesch 2003-09-11 14:37:47 UTC
First of all:
This not a P2.
Second:
Currently we evaluating the default anchoring to match MS word's way
of anchoring. since this is part of our interoperability issues we
will address this in 2.0.
Comment 10 falko.tesch 2003-09-11 14:38:19 UTC
Started
Comment 11 bettina.haberer 2004-04-08 22:08:22 UTC
Hello Andreas, is changing the default anchoring in progress or done or declined
for Q? I have not found any PCD for it. Please give approval for this evaluated
OO.o 2.0 flagged issue. 
If you confirm with the target OO.o 2.0, then please keep it on your owner (or
the owner of the concerning developer) for implementation. In case you want this
issue for 'OOo Later', then please reset the target milestone. If you decline
the issue finally, please set the resolution to 'Wontfix' (but do not close). In
case of 'OOo Later' or 'Wontfix' please reset it on Bettina's owner. Thank you.
Comment 12 michael.ruess 2004-05-06 14:22:40 UTC
re-targeted to OO later
Comment 13 guraknugen 2010-12-01 16:30:50 UTC
The size of an object (at least if the object is an image) can be protected:
Right click an image → Position and size… ⇨

Protect
☐ Position
☒ Size