Bug 67741 - EDITING: Date entry with numeric keypad
Summary: EDITING: Date entry with numeric keypad
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
(earliest affected)
Hardware: All All
: medium enhancement
Assignee: Not Assigned
Keywords: difficultyInteresting, easyHack, needsDevEval, skillCpp
Depends on:
Blocks: Database-Forms
  Show dependency treegraph
Reported: 2013-08-04 11:21 UTC by Simon Richter
Modified: 2019-08-15 12:09 UTC (History)
8 users (show)

See Also:
Crash report or crash signature:
Regression By:

Testcase (9.38 KB, application/vnd.oasis.opendocument.database)
2013-08-04 18:52 UTC, Simon Richter
Screenshot editing the column properties. (151.66 KB, image/png)
2013-08-04 20:17 UTC, m.a.riosv

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Richter 2013-08-04 11:21:33 UTC
I have a form that is designed so that data can be entered with the numeric keypad -- however this does not work for date fields (locale is de_DE, and there is no dot on the numeric pad, only a comma).

It would be nice to have a defined method for quickly entering dates on the numeric pad, ideally without separators as it is easier to type zeros than dashes or slashes.
Comment 1 m.a.riosv 2013-08-04 14:47:50 UTC
Hi Simon, thanks for reporting.

Have you taken a look in?
Menu/Tools/Options/Language settings/Languages - Date acceptance patterns.
Comment 2 Simon Richter 2013-08-04 16:35:11 UTC

I have now. :) Unfortunately, that doesn't work for me.

I've tried adding the formats "D,M" and "D,M,Y" as these would be easy to type, but "1,3,13" gives 1800-01-01. The help mentions ISO dates being acceptable, however neither "13-3-1" nor "2013-3-1" give the desired result (these behave as if nothing was entered, and copy the date from the previous entry).
Comment 3 m.a.riosv 2013-08-04 17:26:56 UTC
Sorry Simon, I have just seen your report is about database, if a find some information about it I'll let you know.
Comment 4 m.a.riosv 2013-08-04 17:41:01 UTC
In a first try, ISO "2013-3-1" date works for me in a date field directly in the table. Maybe in your language minus "-" it is not a separator for dates.
Comment 5 Simon Richter 2013-08-04 18:26:16 UTC
It isn't, however the help text explicitly states that ISO dates are always accepted regardless of locale.

This is a date entry field in a table in a Form.
Comment 6 m.a.riosv 2013-08-04 18:28:55 UTC
Please Simon, take a look to this link, maybe can help.
Comment 7 m.a.riosv 2013-08-04 18:31:27 UTC
Can you attach a sample file?
Please reduce data at minimum needed and delete all private information.
Comment 8 Simon Richter 2013-08-04 18:52:56 UTC
Created attachment 83622 [details]

This is a minimal example, containing a table and a form to edit the table data.

In the form, the date column does not accept ISO dates or dates following the configured acceptance pattern -- only dates from the current locale appear to be allowed.
Comment 9 m.a.riosv 2013-08-04 20:17:00 UTC
Created attachment 83627 [details]
Screenshot editing the column properties.

I think you need to define properly the date format for the column.
While you edit the form, right-click the date column head, and select Column to edit the their properties.
Comment 10 Simon Richter 2013-08-04 20:49:44 UTC
That does affect display as well, which I'd rather avoid.

There are two issues I can see here:

 - the date entry in the form code does not go through the same code path that the normal date entry does, thus ignoring date entry preferences

This I'd think of as a (minor) bug.

 - there is no easy format for date entry using the numeric keypad.

This is definitely an enhancement. It would be awesome if I could use "DMY" as a date format so I can use zero-padded dates without separator.

I'm not sure whether this could/should be split.
Comment 11 m.a.riosv 2013-08-04 21:39:23 UTC
Well Simon, as I have write in you other bug report, why no trying to get help in Ask or in Mailing List.
Comment 12 Joel Madero 2013-12-22 15:58:08 UTC
Lionel - is there some reason why we couldn't add this functionality? I'm thinking if open standards wouldn't allow it for some strange reason. Don't want to mark as NEW until I have confirmation that it's a valid enhancement request.
Comment 13 Alex Thurgood 2015-01-03 17:39:50 UTC Comment hidden (no-value)
Comment 14 Robinson Tryon (qubit) 2015-12-14 05:02:03 UTC Comment hidden (obsolete)
Comment 15 Robinson Tryon (qubit) 2016-02-18 14:51:20 UTC Comment hidden (obsolete)
Comment 16 Chuck Davis 2016-03-20 16:11:43 UTC
One of the major reasons I have been unwilling to migrate to LO is it's lack of date handling for those of us who are heavy 10-key users.  With OO entering a period in a date field always produced an ISO date.  This jewel should not be so deeply hidden: Menu/Tools/Options/Language settings/Languages - Date acceptance patterns!!

A date entered with periods should be a default input pattern!

I also just found the "legacy" selection which gets rid of the stupid marching ants around a selection!!  Bravo!  The "legacy" selection should be the standard....
Comment 17 Aron Budea 2017-11-24 10:10:20 UTC
Needs code pointer.