FWD » Core Development » User Interface

In OE, a FILL-IN widget bound to a date variable with a format containing separators (e.g., "99/99/9999") processes separator character input based on the caret position and character typed. The following rules apply, evaluated in order, stopping after the first matching condition:

1. If the caret is at a separator position:
   • If the typed character matches the separator, move the caret one position right.
   • Otherwise, take no action.
2. If the caret is within the year component and a minus sign (-) is typed, insert the minus sign at the current caret position.
3. If the caret is within the third component, normalize the component without changing the caret position.
4. If the typed character matches the next separator to the right of the caret, normalize the current component and move the caret to the position immediately right of the separator.

In FWD, for condition 3, the condition triggering normalization deviates from OE in both GUI and ChUI modes. When the caret is in the third component, normalization is triggered only if the typed character matches any of the two format’s separators (e.g., / or . for "99.99/9999"). In OE, normalization occurs for any separator character (., /, or -) in both character and GUI modes, regardless of the format’s specific separators.

Example

DEFINE VARIABLE myDate AS DATE.
DEFINE FRAME myFrame
    myDate FORMAT "99/99/9999".
ENABLE myDate WITH FRAME myFrame.
WAIT-FOR WINDOW-CLOSE OF CURRENT-WINDOW.

• OE Behavior: If the user types "12/31/2" and the caret is in the year (third component), typing ., /, or - normalizes "2" to "2002" (caret stays in place) in both character and GUI modes.
• FWD Behavior: In both GUI and ChUI modes, normalization is triggered only if / is typed (matching the format’s separator), not . or -.

9916a rebased to the latest trunk, rev. 16014. Please, review.

There are ChUI regressions.

The specification and the issue description were updated:

Typing One of Date Component Separators (Dot, Minus, or Slash)¶

The following rules are applied sequentially, halting at the first matching condition:

1. For a format without separators, no action is taken.
2. If the caret is located at a separator:
   1. If the typed character matches the separator at the caret position, move the caret one position to the right.
3. If the caret is within the year component and a minus sign (-) is entered, insert or append the minus sign at the current caret position, provided the format length supports it.
4. If the caret is within the third component, attempt to normalize this component (refer to the corner case below) without adjusting the caret position.
5. If the caret is within the first or second component and the typed character matches the next separator to the right of the caret, attempt to normalize the current component (refer to the corner case below) and shift the caret to the position immediately following the next separator.

Corner Case¶

If a component is the year component, contains one or more minus signs, and the caret is not positioned to the right of the rightmost minus sign, no action is taken.

FWD Issue¶

In FWD, the normalization trigger condition differs from OE in both GUI and ChUI modes. When the caret is in the third component, normalization is activated only if the typed character matches one of the format’s defined separators (e.g., / or . for "99.99/9999"). In contrast, OE triggers normalization for any separator character (., /, or -) in both character and GUI modes, regardless of the format’s specific separators.

Example Program¶

DEFINE VARIABLE myDate AS DATE.
DEFINE FRAME myFrame
    myDate FORMAT "99/99/9999".
ENABLE myDate WITH FRAME myFrame.
WAIT-FOR WINDOW-CLOSE OF CURRENT-WINDOW.

1. Execute this program in GUI or ChUI mode, ensuring the last data component is not the year (e.g., set SESSION:DATE-FORMAT='ydm') to prevent literal insertion of the minus (-).
2. Input 12/31/2.
3. Type any of ., -, or /.

• OE Behavior: Typing any date separator character (., -, or /) triggers normalization of the third component.
• FWD Behavior: Normalization is activated only when / is typed (matching the format’s separators), excluding . or -.

Hynek Cihlar wrote:

Code review 9916a. The changes look good. Please go ahead with GUI regression testing, I started ChUI tests.

ChUI tests passed.

Hynek Cihlar wrote:

Hynek Cihlar wrote:

Code review 9916a. The changes look good. Please go ahead with GUI regression testing, I started ChUI tests.

ChUI tests passed.

Works in GUI. Can we merge now?

I rebased the 9916a to trunk rev. 16141. Can we merge now?

Hynek Cihlar wrote:

Are there any related customer test scenarios?

Nothing I can think of.

Should the issue be moved to Test state?

I think yes