[elm_datetime] Fix to consider second field while comparing datetime values.

Summary:
Some app like calendar, they heavily depend on the value of datetime,so to ensure accuracy
second field is considered while comparing datetime values.

@fix

Test Plan: NA

Reviewers: shilpasingh, raster

Reviewed By: shilpasingh, raster

Subscribers: poornima.srinivasan, govi, rajeshps

Differential Revision: https://phab.enlightenment.org/D2204
This commit is contained in:
Subodh Kumar 2015-03-25 07:09:23 +09:00 committed by Carsten Haitzler (Rasterman)
parent 79e7d5bcad
commit 7bf866f8bf
1 changed files with 3 additions and 2 deletions

View File

@ -46,7 +46,8 @@
&(tmptr)->tm_mon, \
&(tmptr)->tm_mday, \
&(tmptr)->tm_hour, \
&(tmptr)->tm_min}
&(tmptr)->tm_min, \
&(tmptr)->tm_sec}
// default limits for individual fields
static Format_Map mapping[ELM_DATETIME_TYPE_COUNT] = {
@ -589,7 +590,7 @@ _date_cmp(struct tm *time1,
DATETIME_TM_ARRAY(timearr1, time1);
DATETIME_TM_ARRAY(timearr2, time2);
for (idx = 0; idx < ELM_DATETIME_TYPE_COUNT - 1; idx++)
for (idx = 0; idx < ELM_DATETIME_TYPE_COUNT; idx++)
{
if (*timearr1[idx] != *timearr2[idx])
return EINA_FALSE;