Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | WW8: Word wraps its "local variables" around to the top of the page on the next update | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Writer | Reporter: | osavill <osavill> | ||||||
Component: | code | Assignee: | AOO issues mailing list <issues> | ||||||
Status: | ACCEPTED --- | QA Contact: | |||||||
Severity: | Trivial | ||||||||
Priority: | P4 | CC: | issues | ||||||
Version: | OOo 1.1 RC4 | Keywords: | ms_interoperability, oooqa | ||||||
Target Milestone: | --- | ||||||||
Hardware: | PC | ||||||||
OS: | All | ||||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||||
Developer Difficulty: | --- | ||||||||
Attachments: |
|
Description
osavill
2003-09-15 17:53:51 UTC
Created attachment 9337 [details]
Incorrect handling of user defined `fields'
reassigned to mru please take a look at this issue 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 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. add oooqa, ms_interoperability change OS: all 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. Created attachment 11867 [details]
An example to show why we import as variables and not user fields.
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 :-( Oliver, you like fields issues, don't you? ;-) . Reset assigne to the default "issues@openoffice.apache.org". Reset assigne to the default "issues@openoffice.apache.org". |