Issue 76864 - Enable human readable value typing in custom fields
Summary: Enable human readable value typing in custom fields
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 2.2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-02 15:31 UTC by nmailhot
Modified: 2014-09-18 07:38 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description nmailhot 2007-05-02 15:31:54 UTC
When I insert a custom field formated as a date in a document modifying it later
is a pain.

Double-clicking on it raises a popup where the field content is not displayed as
a date but as some weird internal integer/string format. I can't select the
month part for example and change it, I have to clear the field and type the new
date from scratch
Comment 1 eric.savary 2007-05-03 13:45:23 UTC
Please add a step by step description of what you do, get and expect.
Comment 2 nmailhot 2007-05-03 15:02:13 UTC
1. add a custom field/variable to a writer doc
2. format it as a date
3. enter date that uses the chosen format
4. save
5. double-click on the field to change it (opens a popup)

Expected result :
Value field in the popup formatted as a date and containing the previously
entered date

Actual result
Value field in the popup containing a humanly-unparseable integer
Comment 3 eric.savary 2007-05-04 13:54:38 UTC
If I understand your description, you entered for instance:
Field name: var1
Field value: 04.05.2007
Format: 31 Dec. 1999
and you get, when editing the field, something like var1 = 39177?

If yes:  the *value* of a date variable must be understood as a raw
(unfromatted) number value = an internal number. Entering something like
"04.05.2007" in the value field will be interpreted as 4.05 (number).

One could think about an "intelligent" value edit field which would recognize
"04.05.2007" as an already formatted date and work with it as is. I don't know
if it's really possible but it's a feature anyway.

Reassigned
Comment 4 nmailhot 2007-05-04 14:02:16 UTC
More like
- Format 31-12-1999
- Value 04-05-2007

but you got the basic idea.

I somehow disagree with the qualification as "enhancement": the integer is some
form of internal OO.o representation, explosing this raw representation as-is in
the UI is a bug as it can not be interpreted by the human user
Comment 5 Edwin Sharp 2014-04-06 13:18:54 UTC
Confirmed with
AOO410m15(Build:9761)  -  Rev. 1583666
2014-04-01 13:50 - Linux x86_64
Debian
Comment 6 mroe 2014-04-07 11:44:10 UTC
I understand the wish.

But try the following:
User field: "MyDate" - Value: 07.04.2014 → [Insert]
User field: "Mydate14" - Value: MyDate + 14 → [Insert]

So there are only special cases where the issue is useful.
Comment 7 aoo 2014-09-18 07:38:49 UTC
I have a similar issue:

I added the definition of a <text:user-field-decl> with office:value-type attribute set to date and the office:date-value attribute set to the date/time string directly in the content.xml like it is specified in http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#element-text_user-field-decl

When I save the document, then the <text:user-field-decl> is changed to float with the office:value attribute value set to the corresponding floating point value.

I wanted to use this feature to generate an ODT-file with the <text:user-field-decl> of type date and the corresponding <text:user-field-get> to show the value to user. Later I want to replace the value in the <text:user-field-decl> with new values.