details: https://code.openbravo.com/erp/devel/pi/rev/b82519cbc5e9
changeset: 35789:b82519cbc5e9
user: Carlos Aristu <carlos.aristu <at> openbravo.com>
date: Thu May 16 16:10:20 2019 +0200
summary: related to issue 40829: fix comments
diffstat:
modules/org.openbravo.client.application/web/org.openbravo.client.application/js/form/formitem/ob-formitem-datetime.js
| 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diffs (19 lines):
diff -r 59d8a1189664 -r b82519cbc5e9
modules/org.openbravo.client.application/web/org.openbravo.client.application/js/form/formitem/ob-formitem-datetime.js
---
a/modules/org.openbravo.client.application/web/org.openbravo.client.application/js/form/formitem/ob-formitem-datetime.js
Thu May 16 14:01:42 2019 +0200
+++
b/modules/org.openbravo.client.application/web/org.openbravo.client.application/js/form/formitem/ob-formitem-datetime.js
Thu May 16 16:10:20 2019 +0200
@@ -296,13 +296,13 @@
});
// == OBDateTimeToDateItem ==
-// OBDateTimeToDateItem inherits from OBDateTimeItem
+// OBDateTimeToDateItem inherits from OBDateTimeFromDateItem
// It has the value of the next day of the selected date at 00:00:00
// Note that the logic to calculate the next day is not implemented here
// For the moment, that logic should be implemented where needed
isc.ClassFactory.defineClass('OBDateTimeToDateItem',
isc.OBDateTimeFromDateItem);
-// == OBDateTimeToDateItem ==
+// == OBAbsoluteDateTimeItem ==
// OBAbsoluteDateTimeItem inherits from OBDateTimeItem
// It displays the received date and send to the backend the modified one "as
it is". So there is no any kind of UTC conversion.
isc.ClassFactory.defineClass('OBAbsoluteDateTimeItem', isc.OBDateTimeItem);
_______________________________________________
Openbravo-commits mailing list
Openbravo-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbravo-commits
