Issue 19608 - WW8: Word wraps its "local variables" around to the top of the page on the next update
Summary: WW8: Word wraps its "local variables" around to the top of the page on the ne...
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC4
Hardware: PC All
: P4 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: ms_interoperability, oooqa
Depends on:
Reported: 2003-09-15 17:53 UTC by osavill
Modified: 2017-05-20 11:25 UTC (History)
1 user (show)

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

Incorrect handling of user defined `fields' (177.50 KB, application/octet-stream)
2003-09-15 17:55 UTC, osavill
no flags Details
An example to show why we import as variables and not user fields. (26.00 KB, application/msword)
2003-12-10 14:50 UTC, caolanm
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description osavill 2003-09-15 17:53:51 UTC
The original OR seems to have been removed from my list. Appologies if it was
due to duplication.

I am going to attach a document that, on its front page, has some text entry
fields that were created in Word. In Word these are highlighted gray and contain
text. In OOo they appear as small, empty gray boxes. Double clicking one brings
up the `Edit Field' dialog but does not display any content not allows any
editing to take place !!

Unlike Word there are now 4 further small, empty gray boxes below the table
containing the original small, empty gray boxes. Double clicking one of these
brings up the `Input Field' dialog which does allow, seemingly, entry of new
text. However this makes no difference to the original small, empty gray boxes.

I raise this as a high priority as it appears to be a very common exercise to
hold details such as Author, Date Published etc. in such user created fields. 

A releated issue is the `Page n of x'. Where `n' is exported to word as a valid
field but the `x' isn't. In word therefore it appears as `Page n of 1' !!
Comment 1 osavill 2003-09-15 17:55:16 UTC
Created attachment 9337 [details]
Incorrect handling of user defined `fields'
Comment 2 jack.warchold 2003-09-15 18:59:02 UTC
reassigned to mru

please take a look at this issue
Comment 3 utomo99 2003-09-16 06:50:07 UTC
I can Reproduce the problem on OOo 1.1 RC4, Win XP Pro Sp1
It is real problem

It is Form problem. so all instruction on the form is gone in OOo
Comment 4 michael.ruess 2003-09-17 12:49:25 UTC
MRU->CMC: May be we can catch the problem, when the Ref fields are not
imported as a varible but as a User Field. these have the same
functionality, but they can only have one value throughout the
document, so that they also have content when they appear above the
"set variable" or an input field.
Comment 5 utomo99 2003-09-19 06:52:30 UTC
add oooqa, ms_interoperability
change OS: all
Comment 6 caolanm 2003-10-10 15:02:05 UTC
If you turn on view fields in word you will see the 4 (actually 5) ask
fields which are turned into the writer input fields. They are invis
in word and so are 0 len in writer. That explains the 5 fields in writer.

I cannot the ref fields as user fields because user fields are changed
globally, they are imported as show variables which is correct. It
just so happens that word "wrap" such variables back to the top of a
page the next time the page is updated. If you would move your 5 ask
fields above their first use your document will work much better. 

But I will try and think of a solution given the document at hand.
Comment 7 caolanm 2003-12-10 14:50:58 UTC
Created attachment 11867 [details]
An example to show why we import as variables and not user fields.
Comment 8 caolanm 2003-12-10 14:58:36 UTC
cmc->ama: I think I've done all I can with the bookmarks used as variables in
this word document. I think I must import them as variables and not as user
fields because they have the same sort of behaviour as our variables in that
changes to them in general only affect the portion document that follows the
set, and not globally like user fields. 

*But* there seems to be the quirk that if you reference a variable before it is
set, you get the value that word last saw this variable take. i.e. the last set
value for a variable in a document wraps around to the top when the fields are
next update.

e.g. load the attached .doc in word and "show fields" and change the last set
variable to a new value and "hide fields" again. Ctrl-A, F9. Now the last
showing of the variable changes, but not the first. Ctrl-A, F9 again and now the
first showing of the variable matches the last one :-(
Comment 9 andreas.martens 2003-12-15 08:57:03 UTC
Oliver, you like fields issues, don't you? ;-)
Comment 10 Oliver Specht 2003-12-15 09:09:38 UTC
Comment 11 Marcus 2017-05-20 11:24:37 UTC
Reset assigne to the default "".
Comment 12 Marcus 2017-05-20 11:25:52 UTC
Reset assigne to the default "".