Issue 1560 - graphics/objects can be anchored to a table row in such a way as to be displayed outside the table
Summary: graphics/objects can be anchored to a table row in such a way as to be displa...
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 638
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords: ms_interoperability
: 3567 (view as issue list)
Depends on: 18732
Blocks:
  Show dependency tree
 
Reported: 2001-08-28 16:16 UTC by caolanm
Modified: 2013-08-07 14:41 UTC (History)
1 user (show)

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


Attachments
example (31.00 KB, application/octet-stream)
2001-08-28 16:17 UTC, caolanm
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description caolanm 2001-08-28 16:16:42 UTC
graphics/objects can be anchored to a table row in such a way as to be displayed
outside the table. There appears to be a compatibility structure in word 97/2000
which matches the positions of table cells.

So if a graphic is anchored in a table cell, this structure tells word whether
to position the graphic inside the cell (as is the default in word currently) or
outside, relative to the table row (as appears to be the case in word 6). The
first is no problem to us, but the second is :-(. This is the reason behind the
"missing" ole2 object in issue 1291/1532/1533
Comment 1 caolanm 2001-08-28 16:17:04 UTC
Created attachment 479 [details]
example
Comment 2 caolanm 2001-10-11 13:54:35 UTC
This is a really obscure word *feature* which seems only available
through importing an older word document into a newer version of word.
It is not possible to create it from scratch in new varients of word.

Most of the required behaviour would occur for free if our table
layout was close enough to word's to be able to lock the height of our
table rows when explicitly set by word, so that our autogrow to
swallow the object didn't happen. So it only makes sense to tackle
this odd varient after the main cases get solved by better support of
layout inside tables. So set this to resolve later to stop issuezilla
nagging me about it weekly.
Comment 3 michael.ruess 2002-04-17 15:31:24 UTC
*** Issue 3567 has been marked as a duplicate of this issue. ***
Comment 4 caolanm 2002-12-13 09:35:51 UTC
Change target to reflect reality
Comment 5 caolanm 2003-08-08 12:03:46 UTC
I'll reassign this
Comment 6 caolanm 2003-08-08 12:04:31 UTC
cmc->ama: This is an old bug, I still see no solution for it in the
filter, unless you have any ideas.
Comment 7 andreas.martens 2003-08-08 14:43:34 UTC
AMA->CMC:
A. We stop our autogrowing cells and allow objects which are anchored
inside cells to be positioned outside the cells.
B. We do A., but with a compatibility flag.
C. We do A., but with object property.
Which solution is sufficient for you?
Or do you have problems even with C because you cannot detect if the
object has to be inside the cell or not?
Comment 8 caolanm 2003-08-08 14:57:32 UTC
C: An object property would do the trick. There is a UI option now in
2003 to enable/disable this of format->object->advanced->picture
position->layout in table cell (it didn't exist before). I'm not 100%
where this information is kept in word but I have a good idea.
Comment 9 andreas.martens 2003-08-18 07:58:20 UTC
So we need an object property.
Comment 10 Oliver-Rainer Wittmann 2003-08-18 08:58:03 UTC
OD (18.08.2003): accepted.
Caoláns investigation is correct, there is a new option in the current
beta version. Thus, we need an object property. I would propose to
introduce a more general property. Our current implementation
restricts the position of objects to the given environment (e.g. page
header/footer, table cell, document body). Thus, I propose an property
like 'layout in given environment' (the name of the property has to be
adjusted).
Comment 11 Oliver-Rainer Wittmann 2003-09-24 12:49:10 UTC
.
Comment 12 Oliver-Rainer Wittmann 2003-10-31 12:38:00 UTC
Changed issue type to enhancement, because we have to introduce a new
option at Writer fly frames to control, if they can leave their given
layout environment (in this case the table cell) or not.
Comment 13 Oliver-Rainer Wittmann 2003-11-20 14:04:17 UTC
OD->CMC:
assigned to you as discussed. Some enhancement in the MS Word import
filter is needed to completely fulfill this enhancement issue.
Comment 14 Oliver-Rainer Wittmann 2003-11-20 14:16:09 UTC
add dependence on issue #18732
Comment 15 caolanm 2003-11-21 14:50:17 UTC
I've checked in the missing piece of glue from word to this new
feature for import to swobjpos03. Lets see if it works...
Comment 16 Oliver-Rainer Wittmann 2004-02-23 10:52:23 UTC
OD->MRU: checked in internal installation set of cws swobjpos03 - please verify.
Comment 17 michael.ruess 2004-03-01 16:09:54 UTC
Yeah, looks good with CWS swobjectpos03.
Comment 18 michael.ruess 2004-03-01 16:10:46 UTC
Verified.
Comment 19 michael.ruess 2004-03-02 11:22:26 UTC
Verified.
Comment 20 michael.ruess 2004-03-25 14:33:53 UTC
Checked integration in src680m30.
Comment 21 amoroder2 2005-10-24 09:41:32 UTC
Hello,

I continue to have the same formatting problem with 2.0
Maybe there is a configuration option for this behaviour, isn't it ?

Bye
Andreas