Issue 106046 - custom property can not be changed
Summary: custom property can not be changed
Status: CLOSED DUPLICATE of issue 100658
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: OOO320m2
Hardware: Unknown Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: writerneedsconfirm
QA Contact: issues@sw
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2009-10-19 16:46 UTC by rolf_schumacher
Modified: 2009-10-25 12:28 UTC (History)
2 users (show)

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

Attachments
one of my test files (9.17 KB, text/plain)
2009-10-19 16:52 UTC, rolf_schumacher 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description rolf_schumacher 2009-10-19 16:46:59 UTC 
What I did:

changed the value of a custom property.

What I expected:

1. the fields in the document referring to that custom property should change.
2. consulting the custom property again it shall show the changed value

What I got:

1. the fields do not change
2. the custom property shows the old value, prior to the change.

Some further comments:

Actually I used Writer 3.2.0 Beta and 3.2.0 M61, instead of 3.2.0m2, but they
can not be chosen in "Found in version" of this issue tracker.

The custom property can be assigned a value one time. They also can not be deleted.
Comment 1 rolf_schumacher 2009-10-19 16:52:06 UTC 
Created attachment 65444 [details]
one of my test files
Comment 2 Regina Henschel 2009-10-19 17:40:13 UTC 
The problem is, that all changes are only possible, if no field uses the
properties. This does not only effect the property name, but also the value. At
least changing the value is possible in OOo3.1.1

Expected behavior: Changing the value is possible any time and the fields are
adapted when update the fields with F9.

I used OOo3.2Beta and DEV300m55 on WinXP.
Comment 3 eric.savary 2009-10-25 12:27:50 UTC 
duplicate

*** This issue has been marked as a duplicate of 100658 ***
Comment 4 eric.savary 2009-10-25 12:28:05 UTC 
Closed