Optimize the interaction of calendar

[Keith-CY]

As mentioned at nervosnetwork/neuron#2592 (comment)

The selected year, month will not be effective if it's saved before day is selected, which is weird and prone to select tomorrow.

Say the pre-picked time is 2023/05/17, and 2024/07 are selected, however, 2023/05/17 will be saved if save is clicked without selecting day

neuron_calendar_behavior.mov

[WhiteMinds]

I feel that not automatically changing the value when switching between years and months is a common behavior and quite reasonable. It seems more like an interaction design rather than a logical bug.
If we want to optimize this, perhaps we should have the "Save" button initially disabled until the user manually makes a change.
In this way, providing a default value for tomorrow might not be necessary, and we can omit the default value but offer a shortcut button like "Tomorrow" to assist in quickly selecting a value.

@Danie0918 @Keith-CY What do you think about this?

[Keith-CY]

I feel that not automatically changing the value when switching between years and months is a common behavior and quite reasonable. It seems more like an interaction design rather than a logical bug. If we want to optimize this, perhaps we should have the "Save" button initially disabled until the user manually makes a change. In this way, providing a default value for tomorrow might not be necessary, and we can omit the default value but offer a shortcut button like "Tomorrow" to assist in quickly selecting a value.

@Danie0918 @Keith-CY What do you think about this?

Indeed, it could be optimized from UX.
Enabling the save button after an interaction is good for me.

[WhiteMinds]

iShot_2023-05-18_10.52.38.mp4

The overall effect would be like this. I think if the goal is to prevent saving unintended values, it might be better to provide a time preview near the save button. That way, users can have a better understanding of the value they are about to save.
The follow was just an example, and the actual style needs to be determined by the designer:

[yanguoyu]

I think it's better to disable save when the user does not select any date. Otherwise, the user may confuse with the new date.

[Keith-CY]

Any idea from @Danie0918 @Sven-TBD

[Danie0918]

Calendar selection is indeed a common function that needs to be protected against accidental touches, especially when it affects transactions.

There are 2 situations here:

1. When no date is selected, the "Save" button is not displayed, and the "Cancel" button is changed to "Close"
2. After selecting the date, the user needs to be prompted to select the date. Here, the style 2 mentioned in the WhiteMinds's comment is used. It is recommended to change "save" to "lock to"

[WhiteMinds]

PR: nervosnetwork/neuron#2674

Please have @Danie0918 review the effect presentation in the PR to ensure it meets the expectations.