Issue 16803 - Frame positioning option: "exclude other frames"
Summary: Frame positioning option: "exclude other frames"
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC Linux, all
: P3 Minor with 3 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2003-07-14 10:14 UTC by bryancole
Modified: 2014-03-23 11:27 UTC (History)
3 users (show)

See Also:
Latest Confirmation in: 4.1.0-beta
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description bryancole 2003-07-14 10:14:41 UTC
Hi, this is a feature request:

Following an extensive discussion under Issue #16292 of various issues with the
frame positioning algorithm/anchoring, I feel the usability of OOo-writer would
be substantially enhanced if Frames had an additional toggleable option "exclude
other frames". This option would forbid any other frames from overlapping this
frame. The option should be turned on by default, since under normal condition
it is never desirably for frames to overlap (of course, there will always be
rare cases where the user want's to switch it off).

This option would remove the "problem" of the tendancy of frames to "jump" onto
one-another when they are positioned automatically (e.g. when anchored to a
paragraph). This problem is *extremely* annoying when working with a document
that uses many graphics or other frames.
Comment 1 reinouts 2003-07-16 14:55:16 UTC
This problem is driving me up the wall, too. I work with a master
document which contains subdocuments with lots of text frames. In the
subdocuments themselves there is no problem, but of course in the
master document there is some layout reflow causing text frames to be
placed on top of each other. But since subdocuments are not supposed
to be edited from within the master document this problem is nearly

However I don't agree with the suggestion to add another option. The
behaviour is broken, so fix it, and don't add an option to work around
it. When frames are explicitly placed on top of each other that should
be fine but automatic reflow should never ever do that.
Comment 2 rblackeagle 2003-07-16 17:25:48 UTC
This is indeed a duplicate of the problem I have faced and still face.
 The incredible jumping graphics should be considered a bug.  I have
never seen a word processor that allowed graphics to move by
themselves simply because a file is closed or the user moves to
another page and then returns.  This "jumping" behavior is intolerable
in those files that are affected.  I find myself forced to use Kword
to make certain graphics do not jump.  And I cannot call Kword a "full
featured word processor."  But, actually, if the developers ARE able
to get it fixed, I don't care if it's called an enhancement or a bug fix.
Comment 3 stefan.baltzer 2003-09-08 17:30:17 UTC
SBA: Reassigned to Bettina from the User Experience team for consideration.
Comment 4 ace_dent 2008-05-16 02:09:48 UTC Issue Tracker - Feedback Request.

The Issue you raised is currently 'Unconfirmed' pending review, but has not been
updated within the last 3 years. Please consider re-testing with one of the
latest versions of OOo, as the problem(s) may have already been addressed.
Either use the recent stable version:
or consider trying the new OOo 3 BETA (still in testing):
Please report back the outcome so this Issue may be Closed or Progressed as
necessary - otherwise it may be Resolved as Invalid in the future. You may also
wish to search for (and note) any duplicates of this Issue that may have
advanced further by checking the Issue Tracker:
Many thanks,
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~
Comment 5 bryancole 2008-05-16 09:53:55 UTC
This is still a significant problem in Writer, in all version up to and
including 3.0beta.

The user-experience team should try working with more documents with densely
spaced figures or frames. Then the problem is obvious.
Comment 6 bettina.haberer 2010-05-21 14:43:09 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements". 
Comment 7 enapannes 2010-11-11 01:48:09 UTC
Created attachment 74012
Comment 8 Edwin Sharp 2014-03-23 11:27:53 UTC
Confirmed with
AOO410m14(Build:9760)  -  Rev. 1573062
2014-03-01_04:11:01 - Rev. 1573123